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

Guidelines for Setting Up Organization Enabled Lists of Values

Before setting up organization-enabled LOVs consider the following:

• Organization-enabled LOVs can become complex without careful planning. Be sure to identify all LOV types that require organization-specific LOVs. For each of these LOV types:
  • Define default LOVs (values intended for all organizations that do not require custom LOVs).
  • Define the organizations that require custom LOVs.
  • For each organization, define the custom LOVs for the organization.
• If you require the same value to appear for more than one organization associated with the LOV type, you must create duplicate values for each organization.

  A list of values associated with an organization is displayed to members of that organization only. LOVs not associated with an organization are displayed to all organizations, except the organizations associated with the LOV type. For example, Value 1 may be associated to Org ABC. Value 2 may be associated to Org XYZ. Value 3 may not be associated to any organization. Value 3 is displayed to all organizations, except Org ABC or Org XYZ. For Value 3 to also appear for Org ABC and Org XYZ, you must create duplicate values and add them to the organization-specific lists of values, one assigned to Org ABC and one assigned to Org XYZ.

• For large implementations, consider using EIM to load organization-specific LOV data. Be sure to associate the appropriate organizations with the LOV types and a single organization with each LOV value.

  For more information about using EIM, see the Siebel Enterprise Integration Manager Administration Guide.

• Organization-enabled LOVs are specific to one organization only. There is no inheritance based on organization hierarchy. For example, an LOV associated with a parent organization does not mean that all child organizations inherit access to the LOV. You must explicitly associate LOVs to each organization.
• After an upgrade be sure to review your LOVs to verify that any LOVs delivered as seed data do not interfere with your custom LOV implementation.
• If you are using both organization-enabled LOVs and MLOVs, be sure one of the following is true:
  • The values for both the Language Independent Code and the Display Value are distinct from all other records.
  • The values for both the Language Independent Code and the Display Value are the same as another record belonging to another organization.