Third-Party Tools as Destinations
Use
You can use the open hub destination to extract data to non-SAP systems. Various APIs allow you to connect a third-party tool to the BI system and to use this third-party tool to distribute data to other non-SAP systems.
Features
First you extract the data from BI InfoProviders or DataSources into a database table in the BI system. The third-party tool is notified as soon as the extraction process has finished. You can define parameters for the third-party tool. You can also use the monitor to monitor the process.
You can connect one or more data transfer processes to an open hub destination of type Third-Party Tool.
You can use a process chain to start the extraction process either in the BI system itself or using the third-party tool.
You can choose from the following APIs:
RSB_API_OHS_DEST_SETPARAMS: You use this API to transfer the parameters from the third-party tool that are required for extraction to the BI system. These parameters are saved in a parameter table in BI 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. You can also add another parameter table containing 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 overwritten by a subsequent request as long as the status is not changed or the request was not yet deleted in the DTP monitor when it was loaded with DTP. If the status is green, the next request can be processed. The user can normally change the status manually in the monitor or in the maintenance screen for the data transfer process. These manual functions are deactivated with open hub destinations of type Third-Party Tool however.
RSB_API_OHS_DEST_GETLIST: This API delivers a list of all open hub destinations.
RSB_API_OHS_DEST_GETDETAIL: This API gets the details of an open hub destination.
RSB_API_OHS_DEST_READ_DATA_RAW: This API reads data from the database table in the BI system. The data is transferred in raw format, and you can select the target code page.
RSB_API_OHS_DEST_READ_DATA: This API reads data from the database table in the BI system. Note that the code pages must be identical.
For information on the parameters of the APIs, 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_DEST_READ_DATA_RAW
Process Flow:
Extraction to the third-party tool can be performed as follows:
...
1. You define an open hub destination with Third-Party Tool as the destination type.
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 required for the extraction.
4. You either start extraction immediately 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 BI system.
5. When the extraction process has finished, the system sends a notification to the third-party tool using API RSB_API_OHS_3RDPARTY_NOTIFY.
6. The extracted data is read by API RSB_API_OHS_DEST_READ_DATA_RAW or RSB_API_OHS_DEST_READ_DATA.
7. The status of the extraction is passed on to the monitor by API RSB_API_OHS_REQUEST_SETSTATUS.
See also:
For detailed information about certification and the scenario, see the SDN at www.sdn.sap.com → Partnership and Certification → Integration and Certification → Integration Scenarios → Business Intelligence → Interface: BW-OHS.