Introduction

In the BII, multiple tables can be mapped to a single component. A component will always have one ‘root table’. Non-root tables must always be related to another (root or non-root) table. The relations are defined in the BII (there need not be any reference defined in the data model). Cycles or self-references are not allowed. In the end, all non-root tables must be connected to the root table, either directly or indirectly.

Note: Referential integrity tables are a different category. A referential integrity table must by definition have a one-to-one relationship with the root table through their primary keys. Referential integrity tables are not discussed in this section.

Multiple ways exist to link a non-root table to a component’s root table or to another non-root table. For the impact on the List and Show methods, refer to the former section “Complex Mappings”. The Create, Change and Delete methods are discussed in the following section. A number of examples are given.

Note that in all cases the implementation will behave as if the data in the non-root table is aggregated in the component. If this is not the desired behavior, do not use a non-root table, but use an association relationship to another business interface instead, or use hooks to implement the complex mappings.