Siebel Global Deployment Guide > Localizing Global Deployments >

Localizing Lists of Values and Multilingual Lists of Values

Lists of values (LOVs), which are used in static picklists in the Siebel application user interface, are also localized for many multilingual deployments. LOVs may also be converted into multilingual lists of values (MLOVs).

MLOVs and multilingual picklists allow values to be selected by a user in one language and retrieved by users working in other languages. The value that is stored in the database for the record is the Language Independent Code (LIC) from the LOV record, rather than the Display Value, as is true for monolingual picklists.

For MLOVs to work correctly, Language Independent Code (LIC) and Display Value must always be consistent within the same LOV type and language, as follows:

  • If you have two records with the same LIC, LOV type, and language, make sure that both records point to the same display value.
  • If you have two records with the same display value, LOV type, and language, make sure that both records point to the same LIC.

NOTE:  For MLOVs, do not set Type to LOV_TYPE, as is done with monolingual LOVs.

As noted in About Parameters for Language and Locale, the Language Code parameter controls the language for MLOV display. If a Preferred Language is specified for a user, this setting overrides the parameter value to determine the MLOV language.

In some localization efforts, you may choose to display LOVs/MLOVs in a common language rather than to use the same language as the application user interface. For example, for users working with a user interface in Czech (a language shipped for Siebel Business Applications) or Polish (an unshipped language), it may be appropriate for LOV/MLOV values to display in German, depending on the business needs of your deployment.

NOTE:  If you want LOV/MLOV values to display in an unshipped language, you can copy values from one of the languages shipped for Siebel Business Applications and translate them into your unshipped language. In general, it is recommended to copy values from a language other than ENU, because many LOV values are provided for ENU that are not translated into any other language. For more information about localizing an unshipped language, see Localizing an Unshipped Language.

LOVs, including MLOVs, can also be organization-enabled, and some LOVs can also be hierarchical. For more information about configuring these types of LOVs, see Technical Note 632 on Siebel SupportWeb. You must engage Siebel Expert Services both for the initial configuration and for the upgrade of these items at the next Siebel version upgrade.

NOTE:  In general, LOVs for newly deployed languages are inactive by default. You must enable the LOVs you require by using Siebel EIM or the List of Values view in the Administration - Data screen. Alternatively, you can engage Siebel Expert Services for this purpose.

For detailed information about creating and administering LOVs and MLOVs, and about converting LOVs to MLOVs, see Configuring Siebel Business Applications and Siebel Applications Administration Guide. Review all applicable guidelines and requirements.

Siebel Global Deployment Guide Copyright © 2007, Oracle. All rights reserved.