|Bookshelf Home | Contents | Index | PDF|
Lists of values (LOVs), which are used in static picklists in the Siebel application user interface, are also localized for many multilingual deployments. LOVs can 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. For records with the same LOV type and language, but different Parent LIC or organization:
NOTE: Where the LOV type is not organization-specific and not hierarchical, user keys normally prevent the creation of different LIC and display value combinations for the same LOV type and language on the server database. It is recommended to create LOVs on the server database whenever possible, because NULL value handling on the local database allows creating LOV records that do not meet the described requirements. (NULL handling is similar on Microsoft SQL Server.) Offending records violating user keys will not successfully replicate to the server database on synchronization.
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, then this setting overrides the parameter value to determine the MLOV language.
In some localization efforts, you might choose to display LOVs or 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 Norwegian (an unshipped language), it might be appropriate for LOV or MLOV values to display in English, German, or some other language, depending on the business needs of your deployment.
NOTE: If you want LOV or MLOV values to display in an unshipped language, then 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 473813.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 632.
You must engage Oracle's Application Expert Services both for the initial configuration and for the upgrade of these items at the next Siebel version upgrade. Contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.
NOTE: In general, LOVs for newly deployed languages are inactive by default. You must enable the LOVs that you require by using Siebel EIM or the List of Values view in the Administration - Data screen. Alternatively, you can engage Oracle's Application 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 of the applicable guidelines and requirements.
|Siebel Global Deployment Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|