Selecting Database Tables as Destinations

You can write data from the BW system to a database table via the open hub destination.

Context

You can also connect a further database. The data is then also written both to the generated table and to this database. This allows you to publish data directly from the BW system to other systems. The data does not have to be replicated, and no third-party tools are required. If you are using SAP HANA, you can also process the data subsequently using SAP HANA functions.

For DB-specific information, see SAP Note 2300276 Information published on SAP site .

Procedure

Choose Database Table as the type of destination. When you activate the open hub destination, the system generates a database table. The generated database table has the prefix /BIC/OHxxx, xxx being the technical name of the destination.
If you specify a previously created connection to a database for Database Connection, the data (together with the generated table) is written to this database. You can create or edit the connection to the database in the DBA cockpit. For more information about the DBA cockpit, go to http://help.sap.com/netweaver SAP NetWeaver Platform Application Help Function-Oriented View Database Administration <Your Database>.

In the target system (in the database), a table is created with prefix /BIC/.

If the DB instance also has an SAP instance, like an SAP ERP system on a SAP HANA database for example, the DDIC object also has to be generated manually. The namespace is also registered when this is done. The DB table name in the remote system is identical to the DDIC name in the local system, or corresponds to the name that would have been created locally on the database.

Note You have to make sure here that there is no table with the same name in the target system. Otherwise an error will occur during creation. The SAP_BASIS version of both SAP systems must also be either identical or compatible, and the codepage (ASCII, Unicode) should match.
You can choose from the following types of extraction:
- Delete data and insert data records: The fields are overwritten. The table is completely deleted before every extraction and regenerated. We recommend this if you do not want to store the history of the data in the table.
- Retain data and insert data records: The data records are inserted. The table is generated just once prior to the first extraction. This allows you to obtain the history of the extracted data.
- Retain data and change data records: You can only do this if you have selected Semantic Key.
Note Note that the table is always deleted and regenerated if changes are made to the properties of the database table (by adding fields for example).
You can choose whether to use a technical key or a semantic key.
- If you set the Technical Key flag, a unique key is added. This consists of the technical fields OHREQUID (open hub request SID), DATAPAKID (data package ID), and RECORD (sequential number of a data record to be added to the table in a data package). These fields display the individual key fields for the table.
  Note Using a technical key with a target table is particularly useful if you want to extract data to a table that is not deleted before extraction. If an extracted record has the same key as an existing record, this duplication causes a short dump.
- If you set the Semantic Key flag, the system selects all suitable fields in the field list as semantic keys. You can change this selection in the field list. Note however that using a semantic key can result in duplicate records. The records are not aggregated. Instead each extracted record is saved in the table.