Selecting Database Tables as Destinations

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

1. Choose DB 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.
2. With an extraction to a database table, you can either retain the history of the data or just store the new data in the table. If you want to overwrite the fields, choose Delete Data from Table when defining your destination. The table is then completely deleted and regenerated before every extraction. We recommend this if you do not want to store the history of the data in the table. If you do not select this option, the system generates the table just one time, before the first extraction. This allows you to obtain the history of the extracted data.
   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).
3. You can choose whether to use a technical key or a semantic key.
4. 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.
   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.
5. If you set the Semantic Key flag, the system selects all 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.
6. If you specify a previously created connection to a SAP HANA database for DB Connection Name, the data (together with the generated table) is written to the SAP HANA database. You can create or edit the connection to the SAP HANA database in the DBA cockpit. Further information: Add a Database Connection
   Note Other databases are not supported here. Only the SAP HANA database is supported.

   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.