Skip to Content
Author's profile photo Johnpaul Joseph

How to Extract SAP R/3 Data to Oracle using Business Objects Data Services

1.   Introduction


This document specifies technically, How to Extract Transform and Load the SAP R/3 Data to Oracle Using Business Objects Data Services.


2.   Data Services Supplement for SAP Connect:


Data Services has four SAP interfaces:


• SAP ERP and R/3 ABAP

• SAP ERP and R/3 BAPI

• SAP ERP and R/3 IDoc



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.

3.   How to Create SAP R/3 Data Store :


 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 


  1. In the object library, go to the Datastores tab.
  2. Right-click inside the object library window and choose New.
  3. The datastore editor opens.
  4. Enter a new, unique name for the datastore in the Name box. The name can contain alpha-numeric characters and underscores (_). It cannot contain spaces.
  5. Choose R/3 in the Application type box.
  6. Enter the appropriate Username and Password information.

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/ Your application server IP address is Therefore, your routing string would look like this: /H/
























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. 


4.   To Retrieve metadata for source schéma   

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.   To Create R/3 Data flow

  1. Create a New Batch Job.
  2. Click on the Dataflow tab on the local object library window.
  3. Right click on the R/3 Data flows and select New
  4. Goto the Options tab and give the appropriate informations like Datastore, Generated ABAP file name etc., as  shown below.




























     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































6.   To Create Data flow  

  1. Right click on the Data flows tab on the local object library window. Create a new data flow. Drag and drop the corresponding R/3 Data flow (VBAK_DATA_EXTRACTION) on the working pane.





























    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.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kishore Madireddy
      Kishore Madireddy
      Hy johan Really good one given a clarity about BODs..
      Author's profile photo Rodrigo Silveira
      Rodrigo Silveira
      How Can I control the delta load in this case ?

      Rodrigo Silveira

      Author's profile photo Johnpaul Joseph
      Johnpaul Joseph
      Blog Post Author
      If it is a Incremental Load, you can control with scripts and variables or If you are doing Target based CDC, you can dump the data to Staging table first, then move to Warehouse table. For Staging table, populate data using flush and load.
      From Staging to Warehouse, use Table comparison transform. Hope this would help you.
      Author's profile photo Former Member
      Former Member
      I have some doubts about delta management using BO data services. Once a LO extractor, for instance 2lis_12_vcitm has been initializated using BODS 4.0, working properly with daily delta loads, could you clarify if it is possible to do (and how) any 'full repair' data load without broken this delta management (something like full repair in terms of BW)?
      Author's profile photo Former Member
      Former Member
      nice weblog, but can u tell the version of BODS which u have used here?
      is it 4.0?
      Author's profile photo Johnpaul Joseph
      Johnpaul Joseph
      Blog Post Author
      Thanks, Its BODS 3.1


      Author's profile photo Former Member
      Former Member
      ohh thanks for quick update. we are working over BODS 4.0. i want to know, can we connect R/3 as a target in BODS 4.0 or not. because there is SAP application coming over there in 4.0 while creating a Data store.
      Author's profile photo Johnpaul Joseph
      Johnpaul Joseph
      Blog Post Author
      Hi pandey, i m not sure about 4.0, but normally we dont treat R/3 as target. Most of the time we treat R/3 as source and SAP BW as Target.


      Author's profile photo Vijayakumar Mukunthan
      Vijayakumar Mukunthan

      Hi Pandey


        Yes its possible to treat R/3 as target using BODS 4.0. I am using both BODS 4.0 and 4.1 and source as non SAP and target has SAP. I can able to create materials, Customer and Vendor Master using IDOC's and BAPI through BODS.



      Vijay Mukunthan

      Author's profile photo Ashok Babu Kumili
      Ashok Babu Kumili

      Hello John Paul Joseph,



      Perfect document to understand the concepts of  "Data Extraction from Non SAP". Very nicely written articles. Thanks for the examples used.. I learnt the key views. It has been summarized very nicely...

      Author's profile photo mario Sepulveda
      mario Sepulveda

      Hi. I've the next question.


      I'm trying to extract data from SAP BW to a SQL_Server table.



      In my instalation, i have Datastore types SAP BW Source and SAP BW Target, but not R/3. Nevertheless, exists on Datastore tab the ABAP_Dataflows.



      I followed the instructions to create the dataflows without use the 'R/3' Datastore type and when i execute the job appear the next error :



      R3C-150301: |Dataflow DF_BW_EXTRACT1 Error opening file <//myserver/Z_EXTRACT1.dat>.



      Is strictly neccesary the R/3 Datastore type?, why exists ABAP_Datflows item in the Datastore tab?


      In your instructions, when is generated the ABAP code for extraction?, and where is used the JOB created in the first Dataflow properties.


      can you send me your comments directly my email? (


      Thanks a lot.