Configuring Siebel eBusiness Applications > Configuring Links >

How Links Are Constructed

The relationships between object definitions used to implement a link appear in Figure 40.

Figure 40.  Link Property Relationships

The object definitions in Figure 40 are as follows:

• Link. The Link object definition specifies a master-detail relationship between two business components. It identifies the master and detail business components, the key field in the master business component, and the foreign key field in the detail business component.
• Master business component. The master business component is the "one" in the one-to-many relationship. The name of this object definition is specified in the Parent Business Component property in the Link object definition.
• Detail business component. The detail business component is the "many" in the one-to-many relationship. The name of this object definition is specified in the Child Business Component property in the Link object definition.

  NOTE:  The Calendar business component should not be used as the master or detail business component in a link.

• Source (primary key) field. The source field, also known as the primary key field, is a field in the master business component that uniquely identifies records in the business component. It represents the ROW_ID column from the business component's base table. The name of this field is specified in the Source Field property in the Link object definition. Source field typically, but not necessarily, represents the row id column from the business component's base table.
• Destination (foreign key) field. The destination field, also known as the foreign key field, is a field in the detail business component that points back to the master record in the business component. Account Id and Opportunity Id are typical foreign key fields. A foreign key field represents a foreign key column from the detail business component's base table, such as PR_DEPT_OU_ID (the base table for the Account business component). The name of this field is specified in the Destination Field property in the Link object definition.

  In a link based on an intersection table, that is, one in which the Inter Table, Inter Parent Column, and Inter Child Column properties are non-blank, you do not specify the Source Field or Destination Field properties. Otherwise, the Destination Field property needs to contain the name of a field in the base table of the business component (not based on a join), and the field has to be updated.

  NOTE:  For a M:M link, you could specify a source field. Destination will always default to Id, even if another value is specified.

A link in a master-detail view is implemented using the object types illustrated in Figure 41.

Figure 41.  Link Architecture

In a master-detail view, a Link object definition is incorporated into a business object (by means of a Business Object Component object definition) to establish the master-detail relationship. This relationship applies to any use of the two business components together within the context of the business object. Each view specifies the business object it uses in its Business Object property. This forces the view to operate as a master-detail view, as specified in the link, without any additional configuration of the view. For more information about master-detail views, see About Views.