This document specifies technically, How to Extract Transform and Load the SAP R/3 Data to Oracle Using Business Objects Data Services.
Data Services has four SAP interfaces:
• SAP ERP and R/3 ABAP
• SAP ERP and R/3 BAPI
• SAP ERP and R/3 IDoc
• SAP BI/BW
Each interface is a license-controlled feature that can be purchased separately and installed with Data Services. When you purchase the SAP ERP and R/3 ABAP interface, you can use an additional type of data flow called an ERP and R/3 data flow.
An SAP ERP or R/3 data store includes the following information for working in an SAP ERP or R/3 environment:
• Connection information, including the ERP or R/3 application server name, the language used by the ERP or R/3 client application, and the client and system numbers. You supply these values based on your installation of SAP ERP or R/3.
• Data transport method used to exchange information between Data Services and SAP ERP or R/3.
You select the method and supply the appropriate information based on decisions you make about running Data Services jobs. This section describes a data transport method that is ideal for a development environment.
To define an SAP ERP or R/3 datastore
As a development option, you can connect to an application server from your GUI using a routing string using the specified syntax in the ERP or R/3 application server field to ensure connection.
The syntax for using an SAP routing string is:
/H/IP Address of local SAP router/H/IP Address of target SAP
router/H/IP Address of target application server
For example:
Your SAP routing string (local and target) is /H/10.10.1.7/H/204.79.199.5 Your application server IP address is 147.204.76.41 Therefore, your routing string would look like this: /H/10.10.1.7/H/204.79.199.5/H/147.204.76.41
To add more information click Advanced button
To add more configurations for QA/Production, click Edit and Create New Configuration
Click Apply and Ok to Save the datastore.
Either double click on the Datastore, and select External metadata to see the list of object from the specified server as shown below or Right click on the Tables from Object library window and ‘Import by name’
5. Goto General Tab and specify the name of the R/3 Dataflow
6. Now, double click on the R/3 Dataflow from local object library window. Drag and Drop the Source table from the datastore window.
7. Place Query Transform and apply the conditions wherever necesssary. (Eg : Where clause VBAK.PERNR=’00001516’)
8. Select Data Transport Transform and connect with Query Transform as shown below.
9. Double click on the Data Transport Transform and specify the File name for ABAP Code generation.
Eg : VBAK.dat
2. Create a Template table or select the Target table from Datastore tab in local object library window and connect with R/3 Component.
Save the Job and Execute it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 |