Explicit Key Mapping

Automatic key mapping function is used if:

• The back-end key fields of the nodes higher in the data object hierarchy are contained as back-end fields in the child nodes.

• The back-end key fields have the same names and data types as the child nodes of a data object.

But if the back-end key fields do not have the same names and data types, you need to define the mapping yourself using explicit key mapping in the Data Orchestration Workbench.

If automatic key mapping is not enabled or the system cannot find any matching fields, and you activate the data object, then the system:

• Creates additional fields for holding the back-end keys of the nodes higher in the hierarchy

• Maps the back-end keys implicitly

  You can change this mapping in the Explicit Key Mapping screen after activation and the additional fields are deleted from the table generated in the CDS, but this can cause inconsistencies.

  If you activate a data object with automatic key mapping enabled, you can use the Explicit Key Mapping screen to check and correct the automatic mapping if necessary.

  Note

  If you use explicit key mapping to change the system's mapping after activating the data object, you must regenerate the tables. There is no need to reactivate the data object.

• Performs consistency check to ensure that the parent key fields are mapped