Non-Hierarchy and Hierarchy DataSource Processing Mappings
Non-Hierarchy and Hierarchy DataSource Processing Mappings
When you create a processing mapping, the Designer creates a different mapping for non-hierarchy DataSources than for hierarchy DataSources. Hierarchy DataSources have parent-child segments. To maintain the hierarchical relationship in the target, the processing mapping for hierarchies contains additional target definitions that share a primary key.
There can only be one processing mapping for all hierarchy DataSources. This mapping is named Mapping_For_Hierarchy and cannot be changed. If you create an additional processing mapping for a hierarchy, you overwrite the existing Mapping_For_Hierarchy mapping.
Processing mappings include the following target definitions:
Control record.
Contains the control record data for the DataSource document, including status and type.
Document number.
Contains the DataSource document number as a unique key. The cleanup mapping uses this as a source definition.
Parameter file.
Contains the folder name and the largest document number processed. The Source Qualifier transformation uses the largest document number processed to ensure that only higher document numbers are extracted from the Source_For_BCI source.
DataSource data targets.
Non-hierarchy processing mappings contain one target definition for all of the business content data extracted from the DataSource. The hierarchy processing mapping contains one target definition for the hierarchy parent IDoc segment and four target definitions for the hierarchy child IDoc segments.
The following figure shows a processing mapping for a non-hierarchy DataSource:
The following figure shows a processing mapping for a hierarchy DataSource:
The name of the source definition in processing mappings is based on the name of the DataSource. However, the source for all processing mappings is the Source_For_BCI relational table.