|Bookshelf Home | Contents | Index | PDF|
If you define a primary ID, then Siebel CRM can retrieve one primary record more quickly from the master business component through a join than it can retrieve all records through a subquery. The primary ID converts a one-to-many relationship into a one-to-one relationship, which simplifies retrieval of the row from a query with subqueries to a simple join query. This configuration improves performance, especially if the user scrolls through the records of a list applet that displays the parent.
For example, in the Account business component the Primary ID Field property of the Business Address multi-value link is Primary Address Id. The Account Address Mvg Applet displays the corresponding multi-value group. Siebel CRM stores the row ID for the primary record in the Primary Address Id field in the account record. The Primary check mark in the list column identifies the primary. Each time Siebel CRM displays a different account record, the multi-value fields for the Address load only the values from the record of the primary Business Address. It is not necessary to query the Business Address business component for multiple rows. This configuration can significantly improve performance, especially in a list applet.
Most predefined multi-value links designate a primary record. A multi-value link that does not designate a primary record uses the first record that Siebel CRM retrieves from the child business component. The link and multi-value link include a set of properties that you can define to instruct Siebel CRM to obtain the record Id of the first record that displays records from the child table each time the parent record changes. You can create a primary field for a one-to-many or a many-to-many relationship.
NOTE: In a multi-value group applet, the list column that displays the check mark indicates the primary or nonprimary status of each record. This list column obtains data for the column from the SSA Primary Field system field. Although Siebel Tools does not display this field in the Object Explorer or Object List Editor, you can reference it from a list column.
The Use Primary Join property of a multi-value link enables the primary join feature. If you set Use Primary Join to TRUE, then Siebel CRM obtains the primary child record for each parent record through a join with the Primary ID Field. If you set Use Primary Join to FALSE, then Siebel CRM queries the child table each time a parent changes.
The Auto Primary property determines how Siebel CRM enters row IDs into the Primary ID Field. It uses the Primary system list column in the multi-value group applet. The user can manually choose the primary. You can set the Auto Primary property to one of the following values:
The SELECTED option only applies if several multi-value links reference the same child business component. For example, with the predefined Bill To Business Address multi-value link and the predefined Ship To Business Address multi-value link. These multi-value links exist in the Order business component and in the Account business component. In this example, if a primary is not set for the Bill To address, then when Siebel CRM performs a separate query to bring back all addresses that are associated with the account or order, Siebel CRM determines if one of the addresses is or is not already chosen as the primary for the Ship To address. If it is, then Siebel CRM sets that address as the primary for Bill To address.
If the Auto Primary property of a multi-value link contains a value of SELECTED, then defining a read-only property at the applet level does not force the SSA Primary Field to be read-only. If the destination business component of the multi-value link is read-only, then Siebel CRM might display an error message that is similar to the following:
|Configuring Siebel Business Applications||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|