Open Hub Destination

Source From:

The open hub destination is the object that allows you to distribute data from a BI system to non-SAP data marts, analytical applications, and other applications. It ensures controlled distribution across multiple systems.

The open hub destination defines the target to which the data is transferred.
See the following figure outlines how the open hub destination is integrated into the data flow:

open hub destination








Use of Open Hub:
Database tables (in the database for the BI system) and flat files can act as open hub destinations. You can
extract the data from a database to non-SAP systems using APIs and a third-party tool.
The open hub destination contains all the information about a data target: the type of destination, the name
of the flat file or database table and its properties, and the field list and its properties.
BI objects such as InfoCubes, DataStore Objects, InfoObjects (attributes or texts), and InfoSets can function
as open hub data sources. Note that DataSources may not be used as the source.
You can use the data transfer process to update data to the open hub destination. This involves transforming
the data. Not all rule types are available in the transformation for an open hub destination: Reading master
data, time conversion, currency translation, and unit conversion are not available.

Creating Open Hub Destinations:

Follow the steps to create and execute the Open Hub Destination.
Step 1
1. In the Modeling area of the Data Warehousing Workbench, choose the open hub destination tree

data warehosuing workbench










2. In the context menu of your InfoArea, choose Create Open Hub Destination:

data warehosuing workbench2










3. Enter a technical name and a description. We recommend that you use the object from which you want to
update data to the open hub destination as the template.








4. On the Destination tab page, select the required destination. Here I’m selecting the File as Destination.

Press F4 and then select the destination path

Note: Here Separator is “;” (Semicolon), we can also give “,” (Comma), at the end of this article we can see with Comma
Here I selected Desktop as path. So the Flat File will save directly on Desktop with the technical name of
Open Hub Destination

5. On the Field Definition tab page, you can see the fields list (from InfoCube).

Save and Activate.
Step 2:
Creating the Transformations.
Right click on our Open Hub Destination and then create Transformation between Open Hub Destination and

Give the Source and Target details like below. i.e. Our InfoCube Technical name and Open Hub Destination
Technical name.

After giving the details then Press Enter.
In the following screen you can see the Transformations and mappings; the system will propose the
mappings automatically.
Save and Activate.

After Activation see the Flow of our Open Hub Destination

Step 3:
Creating Data Transfer Processes between InfoCube and Open Hub Destination.
Right click on our Open Hub Destination and Create DTP.

The system will take the default values, see the following screen

Check the parameters in the above screen and then press Enter.
Save and Activate the DTP, you can see the different options in the Extraction Tab, we can select either
Delta or Full. Here I selected Delta.
With delta we will get any new records i.e. from InfoCube to Flat File.

See the options in Update Tab

Finally see the Extraction Tab. Once every thing is fine then execute it.

Once it is Success, you can see the below screen with Green lights.

In Desktop i.e. I given the destination path is Desktop, it will create Two Files one is Structure file and other
is Actual Data File.

Step 4:
Actually Step 3 it self the Scenario is over, but here I’m explaining with different Separator “,”. The data in
actual data file is very clear if you select “,”.
For this we need to change the Separator in Open Hub Destination.

Active the DTP and then execute it, you can see the below screen.


Leave a Reply

Your email address will not be published. Required fields are marked *