Components of the Open Hub Service in BW BI

The open hub service is made up of the following objects:

InfoSpoke

The central object for the data export is the InfoSpoke.

The InfoSpoke defines the following:

● The open hub data source from which the data is extracted

● The extraction mode

● The open hub destination into which the data is delivered.

In addition, you can select which selection of data is extracted from which InfoProvider. The selection ensures that a destination can be provided with data from the same InfoProvider at different times using a delta. As long as extraction has not yet taken place in delta mode, the selection set is freely configurable. Once it has, this no longer applies.

Open Hub Data Source

BI objects such as InfoCubes, DataStore objects, MultiProviders or InfoObjects (attributes or texts) can function as open hub data sources. If you use an InfoCube with non-cumulative key figures as a data source, refer to the note regarding the settings on the Selection tab page in Creating InfoSpokes.

Extraction Mode

An InfoSpoke can extract data in two ways: in full mode (F) and in delta mode (D). See InfoSpoke Extraction Mode.

Open Hub Destination

Database tables (from the database in the BI system) and flat files (CSV) can act as open hub destinations. See Database Tables As Destinations and Files As Destinations. You can extract the data from a database to a non-SAP system using APIs with a third-party tool. See Third-Party Tools As Destinations.

The open hub destination contains all the information about the target system for the InfoProvider data: type of destination, name of the flat file or database table. It also contains a logical target system. The logical target system is used to structure the individual open hub destinations in the open hub monitor. The open hub monitor groups the requests according to logical target system, open hub destination and InfoSpoke. By specifying a logical target system, you get a better overview of the individual open hub requests.