About Joins

This topic describes joins. It includes the following information:

• How Siebel CRM Creates a Join

• Guidelines for Creating a Join

A join creates a relationship between a business component and a table that is not the base table of the business component. For more information, see Join.

To observe how a join works, in the Siebel client, you can navigate to the Service Request screen, and then examine the Service Request List Applet. This applet includes the Account field. A join brings the Account field to the Service Request business component, and then the Service Request List Applet displays the data in the Siebel client.

The following figure describes how a foreign key column that resides in the detail table defines the parent-child relationship. Multiple rows in the detail table include the same foreign key value that references back to the same row in the parent table. After you create a join, you can define more fields in the business component that reference columns in the joined table.

You can use a joined field as the Source Field on the join specification. For example, if you must join grandparent data through the parent ID field on the parent business component.

For more information about implicit joins, see How an Extension Table Stores Custom Data.