Skip to Content
RSA3 is a simple extractor checker program that allows you to recognize the problems at source system i.e SAP R/3.  It tells you if the extractor works. Since records that get updated into InfoCubes and ODS structures are controlled by Update Rules, you will not be able to determine what is in the InfoCube compared to what is in the R/3 environment.  You are not modifying anything, so what you do in RSA3 has no effect on data quality afterwards. The extract checker can test extracted data at the source, allowing you to find data errors/inconsistencies at an early stage, before uploading into BW . If there is something wrong with data in enhanced fields we can check it in RSA3 and correct the User Exit logic there itself, also we can debug the User Exit in RSA3 .   Extract Checker can be utilized in the following ways, i.e  I.     Checking the Records II.     Checking the data in R/3 III.     Changing the Layout IV.     Setting Filter V.     Selecting the Fields VI.     Selection of Range VII.     Exporting the data from Spreadsheet  VIII.   Exporting the Data through Mail IX.      Debugging the extractor function module  I. Checking the records  1. Goto Transaction RSA3.  2. Enter the technical name of the extractor i.e give the Datasource Name and click on Execute(F8) imageDataSource: A DataSource is an object for retrieving data. The DataSource is localized in the OLTP (R/3).  It has  • an extract structure, • an extraction type, and • an extraction method.  The extract structure describes the fields of the internal table that contain the extracted data. The extraction type describes which type of extractor the DataSource uses. The extraction method extracts the data and transfers it into an internal table with the same type as the extract structure.  The DataSource also contains information on the type of data that it stages, for example, attributes, transactional data, hierachies, or texts. It can also support different types of data update. Request ID: Request number for the data transfer Key number for a quantity of data and control information, that belongs together and has been requested in BW at the same time. A request consists of data (sometimes split up into several data packets) and additional information about this data. Data Records / Calls: Maximum number of table entries in extraction API interface Update Mode: Mode of data update (Full, Delta, etc.) This data element describes the mode, in which an extractor is called from a BW. Depending on the mode, the BW expects the data request to be processed in the extractor in various ways:  Update Mode Types Mode     ->               Description F     ->               Transfer all requested data                            D     ->               Transfer delta since last request         I       ->                  Transfer initial status for non-cumulative values     R     ->               Repeat the last delta transfer       C       ->                     Initialize the delta transfer                          S     ->               Simulate the initialization of the delta transfer     Mode ‘R’ This mode must no longer be supported by the extractor under the following conditions: 1. The system has an R/3 Release >= 4.0B 2. The extractor is completely roll back-capable within an extraction process, meaning that no database-commit takes place in the extractor.  Mode ‘S’ If an extractor is called in this mode, it is not permitted to deliver any data. Its only job is to make sure that for this request, the delta mode (‘D’) is possible for any following requests. Example The extractor uses a time stamp stored in an administration table to determine the delta. In the delta mode, only those records that have been changed or generated since the last extraction are actually transferred. In mode ‘S’, the current time stamp is included in the administration table, but no data is transferred into BW.  Target System: Source system of the receiver System, in which applications run, integrated on a joint databasis. In the SAP sense, a client corresponds to a logical system. In the definition of a client, you can enter which logical system is a client. The logical system is relevant for the following SAP areas: •     ALE, in general: Communication takes place between one or more logical systems. •     ALE, distribution scenarios (e.g. cost center accounting): Definition of the system in which a certain application is running. Master data changes, for example, can only be carried out in this system. •     Workflow objects: The logical system is always contained in the key of an object When maintaining the logical system, please note: •     The logical system must be unique across the group. It may not be used by any other system in the ALE system group. •     The logical system may no longer be changed in the productive system if a non-initial has been entered once. If a non-initial logical system is changed retrospectively then the system’s own documents may no longer be found. If the logical system of a document reference does not agree with it’s own then the system assumes that the document is in another system.    3. Enter the technical name and execute(F8) image 4. Click on Display List  Once you click on Display list, it will show you how many records are there in each data packet image    5. Double Click on the DataPacket / Records  Once you double click on any particular record, it will show the data it contains. image  6. Data is displayed ima ge    II. Checking the data in R/3   7. Goto Transaction SE11  8. Give the name of the base table and then click on Display  To check the data in RSA3 with data of base table to see whether extraction is happening correctly or not image 9. Click  on Contents image  10. Check for the Number of entries that are extracted depending on the selection criteria eg. Sales document, Document date etc and Execute, the selected entries will be displayed  III. Changing the layout   11. Goto Settings -> Display Variant -> Current image  12. You can change the layout by transferring Hidden fields which you require to Column content  Here you can modify your column content and select which fields which you want to be displayed, the fields which are required can be selected from hidden fields and moved to column content image  IV. Setting Filter    13. Goto Edit -> Set Filter image  V. Selecting the Fields    14. Move the fields you want to filter, from field list to filter list  The required fields are selected and moved from field list to filter criteria, so that you can see the fields which you are want to be displayed image    VI. Selection of Range   15. Select the range you want to display and execute(F8) image VII. Exporting the Data to Spreadsheet   16. Goto List  -> Export -> Spreadsheet           image  17. Select Table  You will get three radiobuttons, out of which you select Table image   18. Select the Microsoft Excel Radiobutton image  19. The Data is displayed in Excel Sheet  image  VIII. Exporting the Data through Mail   20. Goto List -> Mail recipient      image  21. We can load a file in the Document content, click on Load local file  Here we load the file which we want to transport  and send the required data to the recipient image  22. We can send attachments depending on the recipient type and click on send  Once the file is been loaded we can send the file as an attachment to the recipient intended image  IX. Debugging the extractor function module  23. Click the Debug Mode check box  This will take you to ABAP Debugger screen image 24. When we select the debug mode check box, we can check the execution of function module on which the datasource is based  Here we can make the changes required on the exit written and check whether the data is correctly populated or not image
To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    Hey Man,

    Congrats for first blog.

    This weblog is good only for BW Freshers and who are not familiar with basic R/3 Transaction codes.

    Hope to see some real-time BW Sceanrio from you soon.

    Cheers!!!!!!!!!

    (0) 
  2. Dear,
    I understand that you want to give your contribute by posting a weblog, but I think that everyone here has to consider a kind of minimun in an ideal standard quality of own contributions…
    Here you want to blog about RSA3, ok, this topic could be useful.
    But you cannot upload only screenshot without giving any (REAL) comment that can add some value to your analysis…
    Just to mention something evident:
    * the first screenshot is about HOW TO DIGIT A TRANSACTION CODE ??? and why don’t you directly start from the logon ?
    * the second and the third screenshots seem to have some problem (the second one is not shown and, anyway, it seems to contain the same thing of the third one…)
    * “I. checking the records” and “II. Checking the data in the list”: where is the difference from a logical point of view ?
    * III point is the worst: “give the name of extract structure and setup”…this have no sense ! You are talking about a LC datasource; RSA3, for this type of datasource, takes data from setup table in F mode (and don’t you want to spend some word about this peculiarity ?!). But setup table is a cluster table and there is no help to check its content ! And why do we need to go in SE11 to look at number of entries function, available directly in SE16?
    * From IV to IX I see only screenshots about gui functions available for every table/list in SAP !
    * No comment about other very important feautures in RSA3: update methodS, number of calls, record number per call, target system, authorization trace flag…
    Onestly, sometimes it would be better to take own courage in both hands and decide to wait some moment before posting such a weblog…
    Bye,
    Roberto
    (0) 
    1. Former Member
      Roberto, It doesn’t mean everybody can write blogs like you in detailed/explanatory. And you know what I have learned a lot from his blog reg RSA3 which I dint know earlier since I am new to this BW tech, and a BW aspirant. So you don’t have to be soo harsh on him, he tried his best and not every one be smart & perfect like you. Infact there would have been many guys who are new to this BW and would have learned from his web blog. I am sorry if u are offended but ur comments were very harsh/disappointing. There are hundred’s & thousand’s of blogs and everybody can’t be so smart as you and you can’t compare the detailed level of any blog since you can do it very well. Its just his way of doing it, you should appreciate or be calm. I have read all of your blogs, I really liked them. I know you are too gud, but everybody is not the same rite. Good luk.
      (0) 
  3. Dear,
    I understand that you want to give your contribute by posting a weblog, but I think that everyone here has to consider a kind of minimun in an ideal standard quality of own contributions…
    Here you want to blog about RSA3, ok, this topic could be useful.
    But you cannot upload only screenshot without giving any (REAL) comment that can add some value to your analysis…
    Just to mention something evident:
    * the first screenshot is about HOW TO DIGIT A TRANSACTION CODE ??? and why don’t you directly start from the logon ?
    * the second and the third screenshots seem to have some problem (the second one is not shown and, anyway, it seems to contain the same thing of the third one…)
    * “I. checking the records” and “II. Checking the data in the list”: where is the difference from a logical point of view ?
    * III point is the worst: “give the name of extract structure and setup”…this have no sense ! You are talking about a LC datasource; RSA3, for this type of datasource, takes data from setup table in F mode (and don’t you want to spend some word about this peculiarity ?!). But setup table is a cluster table and there is no help to check its content ! And why do we need to go in SE11 to look at number of entries function, available directly in SE16?
    * From IV to IX I see only screenshots about gui functions available for every table/list in SAP !
    * No comment about other very important feautures in RSA3: update methodS, number of calls, record number per call, target system, authorization trace flag…
    Onestly, sometimes it would be better to take own courage in both hands and decide to wait some moment before posting such a weblog…
    Bye,
    Roberto
    (0) 
  4. Former Member
    Hi,

    I could not agree more with Roberto and BIProject. I think there should a minimal standard for any content to be qualified as a blog. If such “basic” things were to be qualified as blog then we would see many more blogs ranging from “creating info-objects” to “creating cubes”, etc… I hope the Weblog moderators take some action on this trend.

    Let me make it clear I intend no harm to Sajeed’s contribution. I am just worried at the quality and the trend of such weblogs.

    Regards
    Dinesh

    (0) 
    1. Former Member
      ->I could not agree more with Roberto and BIProject.

      Hey Dinesh, we are also saying the same…whatever you said. We also worried for weblogs content.

      Cheers!!!

      (0) 
      1. Wojciech Nowicki
        As I saw this WEB-Blog in the list, I was interested “What interesting can one write about such trivial thing as rsa3 ???”. With this question I looked into this WEB-Blog, and I was appeased – nothing.
        (0) 
  5. Former Member
    Thanks Roberto!

    The weblog is very useful.I request those who have commented not to contradict.If you don’t know to appreciate,Please don’t critisize…

    Thanks,
    DD

    (0) 

Leave a Reply