|Bookshelf Home | Contents | Index | PDF|
Figure 17 illustrates how Siebel CRM constructs a join.
A joined field obtains values through a join. The name of the join is included in the Join property of the field. The Join property and Column property together identify the column and how to access it. If you create a joined field in a business component, then you can change the Type property from the default DTYPE_TEXT to a more appropriate type. For example, if you join a table column that contains phone numbers, then you can change the Type field to DTYPE_PHONE.
The Source Field property of the join specification identifies the foreign key field in the business component. If left empty, then the Source Field is the Id field, which indicates a one-to-one relationship between the business component and the joined table. Siebel CRM sometimes defines a system field as the foreign key field in the Source Field property. The Created By and Updated By fields are examples of system fields. For more information, see System Fields of a Business Component.
The Destination Column property identifies the primary key column in the joined table. If the join occurs on a column other than ROW_ID, then the Destination Column property must not be empty. An empty value in the Destination Column property indicates that the destination column is ROW_ID, which is typically the primary key in a table.
In rare situations, multiple join specifications can exist in a single join. For example, the Sub Campaign business component includes a join to the S_LANG table with two join specifications. In these situations, the source fields in the join specifications must reference the same table. For more information, see Join Specification.
A join between two business components can return one or more records. For example, if the joined table is an intersection table. However, in the applet, Siebel CRM displays only the first record in the result set. An applet that references a business component cannot display duplicate records from the base table of the business component.
For example, in Siebel CRM, there is a many-to-many relationship between the Service Request and Organization business components. The link between these business components is Service Request/Organization, and the link uses the S_SRV_REQ_BU table as the intersection table. In the Service Request business component, you can add a join to the S_SRV_REQ_BU table and a related joined field. If you query the business component to retrieve a service request, then the SELECT statement retrieves all the organizations that are associated with the service request. However, Siebel CRM displays only one service request record in the Siebel client. To view all the organizations that are associated with the service request, the user can open the multi-value group applet that references the Organization business component.
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|