Start of Content Area

Function documentation Database Tables As Destinations  Locate the document in its SAP Library structure

Use

You can select a database table as an open hub destination.

Features

Generating Database Tables

When you activate the open hub destination, the system generates a database table. The generated database table has the prefix /BIC/OHxxx (xxx is the technical name of the destination).

Deleting Data from the Table

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. Choose Delete Data from Table when defining your destination if you want to overwrite the fields. In this case, the table is completely deleted and regenerated before each extraction takes place. We recommend that you use this mode if you do not want to store the history of the data in the table. If you do not select this option, the system only generates the table once before the first extraction. We recommend that you use this mode if you want to retain the history of the extracted data.

Note that if changes are made to the properties of the database table (for example, fields are added), the table is always deleted and regenerated.

Table Key Fields

You can choose whether you want to use a technical key or a semantic key.

Technical Key:

If you set the Technical Key indicator, a unique key is added that 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 within 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 into a table that is not deleted before extraction. If an extracted record has the same key as a record that already exists, the duplicate records cause a short dump.

Semantic Key:

If you set the Semantic Key indicator, the system selects all the fields in the field list as semantic keys, if they are suitable. You can change this selection in the field list. However, note that duplicate records may result from using a semantic key.

The records are not aggregated. Every extracted record is stored in the table instead.

 

End of Content Area