Configuring Siebel eBusiness Applications > Creating and Administering Lists of Values >

Configuration Considerations

MLOVs are implemented below the business component level, so there are no special configuration considerations, other than what is described here. Fields that point to MLOVs with enabled target columns will automatically return display values that match the client language setting.

Because MLOVs are configured on a column basis, target columns that are not configured to be multilingual will behave as before; that is, target columns will store display values instead of language-independent codes.

For display, the underlying language-independent code is converted to its corresponding display value using a Siebel eBusiness Applications lookup. For searching and sorting, however, a database join is performed by your Siebel application to the list of values table. Therefore, when configuring the application, make sure that any configuration directly involving the list of values table is compatible with your Siebel application MLOV functionality.

Only one multilingual picklist type for each column. This means that for a table that has more than one business component mapped to it and several fields mapped to the same column, a multilingual LOV can be associated with only one of the fields. The MLOV upgrade utility checks for this when running in validation mode. See Upgrading Existing Data Using the MLOV Upgrade Utility.