Guidelines for Creating a Join

If you create a join, then use the following guidelines:

• Use a join only if it gets no records or only one record. For example, use a join to get the primary account for an opportunity.

• Create a join only if the business component does not already include a join to a table that includes the data that your configuration requires, and only if a foreign key value exists between the base table of the business component and the joined table.

• Create a join only if Siebel CRM stores the foreign key value in a field that it does not already define as a source in a predefined join.

• If you use the Alias property to create an alias for each join, then a business component can include more than one join that references the same destination table. For example, the Action business component includes two joins that reference the S_CONTACT table:

  • The Owner join gets the person who created the activity.

  • The Primary Contact join gets the contact that is associated with the activity.

• Make sure the Alias property of the join is unique even though the destination table is the same. Do not use the table name as the Alias name, even though this is common in the predefined Siebel repository. An implicit join uses the table name as the Alias to make sure that Siebel CRM does not use the name of the explicit join. To make sure that no conflict exists, you must always create a unique alias name for the join.