What is Data Extraction?
Data extraction in BW is extracting data from various tables in the R/3 systems or BW systems. There are standard delta extraction methods available for master data and transaction data. You can also build them with the help of transaction codes provided by SAP. The standard delta extraction for master data is using change pointer tables in R/3. For transaction data, delta extraction can be using LIS structures or LO cockpit etc.
Types of Extraction:
- Application Specific:
- BW Content Extractors
- Customer Generated Extractors
- Cross Application Extractors
- Generic Extractors.
BW Content Extractors
SAP provided the predefined Extractors like FI, CO, LO Cockpit etc, in OLTP system (R/3) . The thing that you have to do is, Install business Content.
Lets take an example of FI extractor. Below are the steps you need to follow:
- Go to RSA6 >> select the desired datasource >> In the top there is a tab Enhance Extract Structure >> Click on it
- It will take you to DataSource: Customer Version Display. Double click on the ExtractStruct.
- Click on Append Structure button as shown:
- Add the field Document Header Text (eg: ZZBKTXT) in the Append Structure with ComponentType: BKTXT. Before you exit, make sure that you activate the structure by clicking on the activate button.
- Required field has been successfully added in the structure of the data source.
Populate the Extract Structure with Data
SAP provides enhancement RSAP0001 that you use to populate the extract structure. This enhancement has four components that are specific to each of the four types of R/3 DataSources :
- Transaction data EXIT_SAPLRSAP_001
- Master data attributes EXIT_SAPLRSAP_002
- Master data texts EXIT_SAPLRSAP_003
- Master data hierarchies EXIT_SAPLRSAP_004
With these four components (they're actually four different function modules), any R/3 DataSource can be enhanced. In this case, you are enhancing a transaction data DataSource, so you only need one of the four function modules. Since this step requires ABAP development, it is best handled by someone on your technical team. You might need to provide your ABAP colleague with this information:
- The name of the DataSource (0FI_GL_4)
- The name of the extract structure (DTFIGL_4)
- The name of the field that was added to the structure (ZZBKTXT)
- The name of the BW InfoSource (0FI_GL_4)
- The name of the R/3 table and field that contains the data you need (BKPFBKTXT)
With this information, an experienced ABAP developer should be able to properly code
the enhancement so that the extract structure is populated correctly. The ABAP code itself
would look similar to the one shown below:
- Now check the data via tcode RSA3.
(You can open the four Function Modules given above (Tcode SE37), you will get include statement in all the FMs. Double click on theinclude program you will get the ABAP code as above for all standard data sources which can be modified.)
Note: Similarly you can enhance all other SAP delivered extractors. ( For LO Cockpit use tcode LBWE)
Customer Generated Extractors
For some application which vary from company to company like LIS , CO-PA ,FI-SL because of its dependency on organization structure , SAP was not able to provide a standard data source for these application. So customer have to generate their own data source. So this is called Customer generated Extractors.
Lets take an example of CO-PA extraction
- Go to Tcode KEB0 which you find in the SAP BW Customizing for CO-PA in the OLTP system.
- Define the DataSource for the current client of your SAP R/3 System on the basis of one of the operating concerns available there.
- In the case of costing-based profitability analysis, you can include the following in the DataSource: Characteristics from the segment level, characteristics from the segment table, fields for units of measure, characteristics from the line item, value fields, and calculated key figures from the key figure scheme.
- In the case of account-based profitability analysis, on the other case, you can only include the following in the DataSource: Characteristics from the segment level, characteristics from the segment table, one unit of measure, the record currency from the line item, and the key figures.
- You can then specify which fields are to be applied as the selection for the CO-PA extraction.
Generic Extractors
When the requirement of your company could not be achieved by SAP delivered business content data source , Then you have to create your own data source that is purely based on your company's requirement , That is called generic extractors .
Based on the complexity you can create Data source in 3 ways .
1. Based on Tables/Views ( Simple Applications )
2. Based on Infoset
3. Based on Function Module ( Used in complex extraction)
Steps to create generic extractor:
1. Based on Tables/Views ( Simple Applications )
- Go to Tcode RSO2 and choose the type of data you want to extract (transaction, Masterdata Attribute or Masterdata Text)
- Give the name to the data source to be created and click on create.
- On the Create data source screen, enter the parameters as required:
Application Component: Component name where you wish to place the data source in the App. Component hierarchy.
Text: Descriptions (Short, Medium and Long) for the data source.
View/Table: Name of the Table/View on which you wish to create the Generic data source. In our case it is ZMMPUR_INFOREC.
- The Generic datasource is now displayed allowing you to Select as well as Hide field. The fields ‘hidden’ will not be available for extraction. Fields in the ‘Selection’ tab will be available for Selection in the Infopackage during data extraction from the source system to the PSA.
- Select the relevant fields and Save the data source.
- Now save the DataSource.
2. Based on Infoset
3. Based on Function Module
Note: Data for all types of extractors can be viewed via Tcode RSA3, where you have to give the DataSource name, Data Records/call, No. of Extr calls and the selections:
The detailed information on LO-Cockpit, Update modules, generic extractor using FM and Infoset, delta pointer, safety interval will be shared in upcoming blogs.
Thanks,
Suraj Yadav
- SAP Managed Tags:
3 Comments
