Extraction to Non-SAP Systems 
Use
You can use the open hub service to extract data to non-SAP systems. Various APIs allow you to connect a third-party tool (such as Ascential) to the BW system and then to distribute the data to other non-SAP systems.
Features
You first extract the data from data targets in BW to a database table in the BW system. The third-party tool receives a message when the extraction process is complete. You can define parameters for the third-party tool. You can also use the monitor to oversee the process.
Using a process chain, you can start the extraction process either in the BW system itself or from the third-party tool.
The Following APIs Are Available:
RSB_API_OHS_DEST_SETPARAMS: With this API, the parameters from the third-party tool that are required for the extraction are transferred to the BW system. These parameters are saved in a parameter table within the BW system in the metadata for the open hub destination.
RSB_API_OHS_3RDPARTY_NOTIFY: This API sends a message to the third-party tool after extraction. It transfers the open hub destination, the request ID, the name of the database table, the number of extracted data records and the time stamp. In addition, you can add another parameter table that contains the parameters that are only relevant for the third-party tool.
RSB_API_OHS_REQUEST_SETSTATUS: This API sets the status of extraction to the third-party tool in the open hub monitor. Red means that the existing table is not being overwritten. If the status is green, the request is processed further.
RSB_API_OHS_DEST_GETLIST: This API delivers a list of all open hub destinations.
RSB_API_OHS_DEST_GETDETAIL: This API determines the details of an open hub destination.
RSB_API_OHS_DEST_READ_DATA: This API reads data from the database table in the BW system.
Optional:
RSB_API_OHS_SPOKE_GETLIST: This API supplies a list of all InfoSpokes.
RSB_API_OHS_SPOKE_GETDETAIL: This API determines the details of an InfoSpoke.
In the next BW Release the InfoSpoke will no longer be used. The open hub destination will remain.
For more information about the parameters, see:
API: RSB_API_OHS_DEST_SETPARAMS
API: RSB_API_OHS_3RDPARTY_NOTIFY
API: RSB_API_OHS_REQUEST_SETSTATUS
API: RSB_API_OHS_DEST_GETDETAIL
API: RSB_API_OHS_DEST_READ_DATA
API: RSB_API_OHS_SPOKE_GETLIST
API: RSB_API_OHS_SPOKE_GETDETAIL
Process Flow:
Extraction to the third-party tool can be executed as follows:
...
1. You define an InfoSpoke with destination type DB Table and Notification to Third-Party Tools.
2. You create an RFC destination for your third-party tool and enter it in the definition of the open hub destination.
3. You use API RSB_API_OHS_DEST_SETPARAMS to define the parameters for the third-party tool that are required for the extraction.
4. You can use the InfoSpoke either to start the extraction directly or include it in a process chain. You can also start this process chain from the third-party tool using process chain API RSPC_API_CHAIN_START. The extraction process then writes the data to a database table in the BW system.
5. When the extraction process is finished, the system sends a notification to the third-party tool via API RSB_API_OHS_3RDPARTY_NOTIFY.
6. The third-party tool reads the data from the database table. Afterwards it transfers the status of the extraction to the monitor using API RSB_API_OHS_DEST_SETSTATUS.