Skip to Content
Author's profile photo Former Member

Step by step data loading from BODS to BW target

Configurations at BW system:

1) Log on to the SAP BW system.
2) Enter T code ‘SALE’ to create new logical system:


3) To create a logical system, choose Define Logical System.

  • Enter a name for the logical system that you want to create.
  • Enter a description of the logical system.
  • Save your entries.

4) Go to Transaction RSA1 to create RFC connection.

5) Select Source Systems in the Modeling navigation pane on the left.

6) Navigate to BO DataServices right click and select create.


7) Enter Logical System Name and Source System Name as shown above and hit Continue.


8) Data Services will start an RFC Server program and indicates to SAP BI that it is ready to receive RFC calls. To identify itself as the RFC Server representing this SAP BI Source System a keyword is exchanged, in the screen shot above it is “BODREP”. This is the Registered Server Program, the Data Services RFC Server will register itself with at SAP. Therefore, provide the same Program ID that you want to use for the call of the RFC Server on Data Services side. All other settings for the Source System can remain on the default settings.
To complete the definition of the Source System, save it.


NOTE: We have to use the same Program ID while creating RFC connection in Management Console(BODS).

BO Data Service – Configure a RFC connection

  1. Log on to the SAP data services management console system.


2     Expand to the new “SAP Connections” node and open the “RFC Server Interface” item. In the Configuration tab a new RFC Server is added so that it can register itself inside the SAP System with the given PROGRAM_ID.


3     Start the RFC server from tab ‘RFC server interface status” :


4     Go to BW and check the connection :


  It will show message like below:


Creating BW source:

  1. Double click on BODS connection :


   2    Right click on header and create new application component(Here it’s ZZ_EMPDS) :



   3    Right click on application component and create a new datasource:


   4    Fill the information for datasource as shown below :

         General Info. Tab


   Extraction Tab


   Fields Tab: Here we’ll define the structure of the BW target and save it.


   5   Now, BW will automatically create a new InfoPackage as shown below :


Creating BODS Datastore and Job:

1     Right click and create a new data store for BW target and fill the  required BW system detail as shown below :


2     Right click on transfer structure and import the datasource( here its transaction datasource ‘ZBODSTGT’ :



3     Right click on File format and create a new file format as shown below :


4     Create a BODS job where Source is flat file and target is BW data source(Transfer structure) as shown below :


Where query mappings are as shown below:


Execute the job:

BODS job to load data in BW can be executed from both the systems, BODS designer and BW system.

Before Executing the job, We have to do following cofigurations in BW InfoPackage :

Goto BW, Double click on the InfoPackage for respective datasource(ZBODSTGT) and fill the “3rd party selection” details as below and save it.

Repository    : BODS repository name

JobServer     : BODS running jobserver name

JobName     : BODS job name


Job Execution from BW system: Right click and execute infopackage. It will trigger BODS job which will load the data into BW datasource.



Double click on InfoPackag, go to ‘Schedule’ tab and click on start:


Job Execution from BODS designer: Go to BODS designer, Right click on the BODS job and Execute.



Verifying Data in BW :

  1. Go to Datasource and right click go to Manage :


When we execute the job, it will generate a request for data extraction from BODS :


2     Select latest request and click on PSA maintenance which will show the data in target datasource.

After loading data to BW datasource, it can be mapped and loaded to any BW target like DSO or Cube using process chain in “Schedule” tab of InfoPackage:

Go to ‘Schedule Option-> Enter Process Chain name in ‘AfterEvent’

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo shiva sahu
      shiva sahu

      Hi Tanvi,

      Thanks for posting this document.

      could you please show some example with data cubes , extractors, hierarchies and other objects as well.

      Thanks & Regards,

      Shiva Sahu

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Siva,

      Once data is loaded to BW PSA as described in this document, It can be mapped to any of the BW object from PSA.

      Here is the document which describes how to fetch data from ECC extractors using BODS:

      Data loading from SAP ECC Extractor to SAP HANA using BODS



      Author's profile photo Former Member
      Former Member

      Hi Tanvi,

      Thanks for the doc. I was looking for it.



      Author's profile photo Sunil Kumar
      Sunil Kumar

      This is the other way round...You have to first do the BODS RFC setup and then start on the source system.

      Author's profile photo Christian Kinne
      Christian Kinne

      I tried to follow you description because it's very interesting for us but still there are some problems.

      First - could be that it is new, I must select a source object for the data source. If I tried to select this I get this error :

      Browse has system error: org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog## at [row,col {unknown-source}]: [1,0]

      Further the adapter selection third party isn't available anymore for BODS - looks like they support it directly, Adapter : Load using RFC from Data Service - it's the only entry in the list to select.

      It would be great if someone have newer information or set it up in the last time.

      best, Christian


      Author's profile photo Shubha Nand
      Shubha Nand

      Hi Christian,

      We are facing the same above error. able to resolve the issue?

      We are unable to create a datasource due to the error.

      In RFC logs in dsmc,  attached error screenshot.

      Dataservices local repo is sql anywhere.