What is difference between Link and Join in siebel ?

Home » Interview Question, Siebel Configuration

Link and Join

11 April 2009 8,294 views 2 Comments

If you are facing siebel job interview, the probability of question " What is difference between Link

and Join? " is very high. Links and Joins have following differences in siebel world.

For experts : In a nut shell

Relationship:

Joins: Joins are configured between a Business Component and a table.

Links: Links are configured between 2 Business Components.

They represent Parent Child relationship Cardinality:

Joins: Joins have 1:1 & M:1 cardinality.

Links: Links have 1:M & M:M cardinality.

Configuration:

Joins: Joins are configured as child properties of a BC.

Links: Links are created through Link Object in Siebel tools and they are referenced

in Business Objects and Multivalue Links (MVL) to establish parent child relationship.

Examples:

Joins: A Service Request can only have a single owner. So a Join is created in the

Service Request BC to pull the owner information from the S_USER.

Links: An Account can have multiple Addresses. A link between BC: Account &

BC: Business Address reflects this 1:M relationship.

For beginners : Below details will help freshers to understand clearly.

Link:

Link specifies the relationship between two business components. The relationship can be one-to-many (1:M), such as parent/child, or many-to-many (M:M).

A link implements a one-to-many (or master-detail) relationship between business components based on their base tables.

The Link object type makes master-detail views possible, in which one record of the master business component displays with many detail business component records that correspond to the master.

Join:

Join defines the logical join between a business component’s base table and another table.

A Join object definition creates a relationship between a business component and a table other than its base table.

The join allows the business component to use columns from that table.

The join uses a foreign key in the business component to obtain rows on a one-to-one basis from the joined table, even though the two do not necessarily have a one-to-one relationship.