Configuring Siebel eBusiness Applications > Creating and Administering Lists of Values > About Organization Enabled Lists of Values >

Guidelines for Configuration and Scripting With Organization Enabled LOVs

When configuring objects in the Siebel repository or scripting, consider the following:

• If LookupValue() or LookupName() are used as expressions in repository configuration, be aware that in contexts where there is no data, such as a new record, the organization associated with the user's current position is used to drive visibility and thus the display of organization-enabled LOVs. In contexts where data exists, the primary organization associated with the record is used to drive visibility.
• If LookupValue() or LookupName() are used as functions in repository configuration or scripting, be aware that the organization associated to the users primary position is used to drive visibility and thus the display of organization-enabled LOVs.
• When a user selects an existing record, the organization context is determined by the primary organization associated with the record, not the organization associated with the user's position. The Owner Organization Specifier property on the business component's underlying base table specifies the column that holds the organization Id. (For business components based on S_PARTY, this property is specified on the primary extension table).

  For most tables in the repository, the Organization Specifier property is set to the column holding the primary organization Id. For example, for S_ORG_EXT, it is set to [BU_ID]. The property could also be defined in several levels, allowing you to configure a child business component so that it inherits the organization context from the row in the parent business component. For example, when a user is creating a child record, the LOVs initially displayed are determined by the organization associated with the user, but when the user performs a query on the child applet, LOVs displayed are determined by the organization inherited from the parent record.

  An example of the Organization Specifier property defined with several levels is [S_TAB_X][S_TAB_COL1][S_TAB1_COL2], where each element is one of the following:

  • A column in the current table.
  • The name of an extension table.
  • The name of a FK column.
  • The name of the column holding the BU_ID.

    NOTE:  You can only configure the Organization Specifier property for custom tables. The property is read-only for standard Siebel tables. If you have a requirement to modify the Organization Specifier property for a standard Siebel table, contact Siebel Expert Services.