Configuring Siebel eBusiness Applications > Configuring Joins >

About Joins

A Join object definition creates a relationship between a business component and a table other than its base table. This relationship allows the business component to use columns from the other 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 tables do not necessarily have a one-to-one relationship.

Figure 36 shows the Service Request List Applet that exposes the Account field. A join brings the Account field into the Service Request business component and the Service Request List Applet displays the data in the user interface.

Figure 36.  Example of Joined Field Exposed in the User Interface

The master-detail relationship is implemented with a foreign key column in the detail table (as shown in Figure 37). Multiple rows in the detail table have the same foreign key value pointing back to the same row in the master table. A join is always one-to-one and it is always between a business component and a table. After a join is created, you can create additional fields in the business component based on columns in the joined table.

Figure 37.  Master-Detail Relationship in a Join

NOTE:  It is possible to use a joined field as Source Field on the join specification. This is important if, for example, you need to join in grandparent data through the parent id field on the parent business component.