Guidelines for Creating Joins With a Party Table

If you create a join that does or does not involve a party table, then use the following guidelines:

• If your join brings party data to a nonparty business component, then create a new join where the join specification references PAR_ROW_ID.

• If your join brings party data to a party business component, then use the appropriate explicit join.

• If you map fields in a party business component, then use the implicit join for the extension table.

• If a join references a table that is a party table, then you must display the foreign key value as the source field. Unlike a join to a table that is not a party table, the destination column must reference the PAR_ROW_ID column that resides in the joined table.

• If a join references a table that is not a party table, then Siebel CRM can update only the column that the field in the parent business component that contains the foreign key value references. You must define the following objects:

  • The joined table.

  • The join specification. The source field property must reference the parent business component that stores the foreign key value. The destination column property must reference the child table, which is typically ROW_ID.

For more information, see How the S_Party Table Controls Access.