Situation 1: direct mapping through identifiers.

Relationship between root and non-root tables - situation 1:

Identifying attributes/columns are shown in italics.

This is the situation that was supported already in Integration Studio 6.1. In this case, the non-root table is really aggregated in the root table. A row in the root table will always exist for a component instance. A row in the non-root table need not exist; it will exist if a price is set or if the table is marked as ‘mandatory’ in the BII. If a component instance is deleted, then the non-root row is deleted first and then the root row is deleted.