Basics

Getting Started

Implementation Process

Database Concepts

Others

 

Implicit Join

Implicit Join exists between tables having 1:1 relationship. Implicit meaning implied join already exists between tables and need not be configured. For example S_CONTACT_X is the extension table for S_CONTACT and the relationship between them is 1:1 which is already defined within the BC.

To understand better if we look into the Contact BC under Siebel Tools, there are fields like ATTRIB_01, ATTRIB_02 that belong to S_CONTACT_X. This S_CONTACT_X is mentioned under the Join property. But when we try to look at the Join Specification for the extension table S_CONTACT_X, it is not mentioned. So there is a hidden relationship inside the Business Component Contact which makes the relationship between these two tables meaningful. The hidden join is done using the field “Id” (system field of Contact BC representing S_CONTACT.ROW_ID) and S_CONTACT_X. PAR_ROW_ID.

Similarly implicit join exists between the following table and many others

• S_SRV_REQ and S_SRV_REQ which is used by Service Request BC
• S_OPTY and S_OPTY_X used by Opportunity BC
• S_ORG_EXT and S_ORG_EXT_X by Account BC

So the following facts can be noted about Implicit Joins.

• Implicit joins are already defined by Siebel and need not be configured
• There is no join specification
• It only exists between the base table and extension table (_X).
• The join is done using the BC system field "Id" which is the ROW_ID of the parent table and "PAR_ROW_ID" of the extension table.