Skip to Content

Transfer Data From BI to Third Party Tool Using OHD.

Applies to:

This article applies to SAP Business Intelligence (BI 7.0). For more information, visit the Business Intelligence homepage.


These documents describe step by step procedure of loading the recently missed delta using reconstruction method. Hopefully it will be useful to anyone else who’s about to load missed delta (especially for beginners).

Author(s):    Rajesh Kumar Sinha

Company:   Accenture Services Pvt. Ltd.

Created on: 15 April 2013



Author Bio :

Rajesh Kumar Sinha, is working as a SAP BI Consultant in Accenture has an experience of more than 1.5 years. Skill set includes SAP Business Intelligence and Business Objects.

Business Scenario

This article explains how to transfer the data from BW system to third party Tools.

Here we are considering the data has to be transferred from BW system to Application server in BW system itself.

OHD Concept:

The Open Hub Destination Object enables us to distribute data from an SAP BW system into external Data Marts, analytical applications, and other applications. We can ensure controlled distribution using several systems. The central object for exporting data is the OHD. We can define the source and the target object for the data. BW becomes a hub of an enterprise data warehouse. The distribution of data becomes clear through central monitoring from the distribution status in the BW system.


BW 7.0 and afterwards supports OHD.

Using BADI we can transform Open Hub Data according to the destination requirement.

OHD sources:

Open hub data sources are the BI objects from which data can be extracted and sent to required destination.

Info Cubes

Data Store objects

Characteristic Info Objects (attributes/texts)

Step By Step Solution:

Here we are taking the scenario for Example: Source is Cube and Target is BI application Server.

We are sending the data from BI Cube to Application server through ODH. So we need to create the Logical Path and Logical File name.

Creation of Logical Path and Logical File Name.

1.    Definition of the logical path name

Here logical file path name is a path where we want to create the file on application server.

  1. Go To Transaction FILE.
  2. Click on Logical File Path Definition and then click on New Entries. (Please find the below screenshot for details).


      Enter the Logical File Path and Name of the same (In Below screenshot) and click on Save.


Now Select the saved Logical File Path and double click on option “Assignment of Physical Paths to Logical Path” from left side Menu of Dialog Structure.

(Find the details in below screenshot)


After clicking on new entries below screen will appear.

Enter the Syntax Group and Physical Path(Path where the file will be stored physically on Application server).



Click on Save(below screen will appear).


Logical File Path Definition is completed.

2. Definition of the logical file name.

Here Logical file name is the name of the file (File with the same name will be stored in Application server)

Select the option “Logical File Name definition, Cross Client” from left side Menu of Dialog Structure and click on New Entries (Find the details in below screenshot).


After clicking on new entries below screen will appear.


Enter the New Logical File and Name.

Enter the Physical file Name (the file will be stored at application server with the same name and format), here we have used Format File Name (Export_File_Country_Year Month Day) ending with Year, Month, and Day and also format is Text Type.

Similarly we can put File Name.CSV for CSV format.

Data Format: Several Options like Binary, ASCII etc (mentioned in the below screenshot).

We have used Binary Type.


Select Application Area: Here also we have different – different Application Areas, we are selecting BW because we are sending data to BW application server only.(Mentioned in the below screenshot)


Click on Save.

Definition of Logical File Name is completed.

Steps to create OHD.

Go To Transaction RSA1.

Click on OHD.

Select the Info Area, right click and click on Create “Open Hub Destination”.


Provide the Technical Name and Description of the OHD.


Template can be provided if you want to use same number of fields in the Transformation of OHD extraction also.

Here we are taking example without Template.

After clicking on OK, We will get the below window.


The Destination Type:

For Destination Database Table- Automatically BW Table Database Table will be created.

Please find the below Screenshot for the same.


For Destination Third Party Tool.

We need to maintain RFCs destination Parameters.


Here we are selecting Destination File Type and select Application Server.

We have already created Logical File Name, so same will be provided here.


Give the Application Server File Name and use the Separator, Here we have used “;” as the separator.


In the Field Definition fill the Field, Description, Data Type, and Length.

Mention in the below screenshot.


Create the Transformation by Right Clicking on OHD and select Create Transformation.

Provide the Source Object Type and Name of the same.


Map the Target field with any source fields.


Right Click on Target filed assignment and select the Rule Group.

Put the Description and Rule Type ABAP Routine.


Edit the routine and put ‘ ‘ in Result. Check and save the same.


Create a Start Routine and select the required field which you want to extract from BW system.

Store all the data in Internal table and transfer the data to result in End Routine.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.