Configuring Siebel eBusiness Applications > Configuring Tables and Columns > About Extension Tables >

About One-to-Many Extension Tables

The names of 1:M extension tables are appended with the suffix _XM. In a 1:M extension table, there can be multiple rows for a single row in the base table. Like 1:1 extension tables, 1:M extension tables have a set of generic columns (ATTRIB_xx) that you can use to store custom attributes. However, unlike 1:1 extension tables, 1:M extension tables have a Type property value of Data (Public) rather than Extension.

You can use 1:M extension tables to track additional entities that have a 1:M relationship with a parent business component but are not represented by existing Siebel business components. You can store data for multiple business components in an _XM table. The Type column is used to group records in the _XM table. You configure each business component to retrieve only the rows of a given type.

One-to-many extension tables require the following configuration at the business object layer:

• A new business component and fields that map to columns in 1:M extension table that you want to use to store data.
• Three additional business component fields that provide the user key and map to the following columns:
  • PAR_ROW_ID. This column maps to the foreign key field using in the 1:M link.
  • NAME. The value stored in this column needs to make the record unique for each parent record.
  • TYPE. This column is used to group records in the extension table. Set a default value for the Type field and then configure the business component search specification to automatically search for those records in the extension table that contain the default value.

    NOTE:  The combination of NAME, TYPE, and PAR_ROW_ID will be unique in order to satisfy the U1 index of the _XM table.

• A link and business object component to establish the master-detail relationship between the new (detail) business component and its master business component.

CAUTION:  Avoid an _XM table as an extension to an existing _XM table. It will cause problems with EIM and docking processes.

Related Topics

Using Static 1:M Extension Tables

Creating Business Components

Creating Links to Define a 1:M Relationship

Creating Business Objects and Business Object Components