Configuring Siebel Business Applications > Localizing Siebel Business Applications > Localizing a Multilingual List of Values >

Configuring a Multilingual List of Values

To configure an MLOV, you modify objects in Siebel Tools, and then perform administration tasks in the Siebel client. If your implementation uses certain Siebel modules, such as Siebel Workflow, then you must perform more configuration. For more information, see Configuring Certain Siebel Modules to Use MLOV Fields.

To configure a multilingual list of values

1. Consider potential performance issues.

   For more information, see Considering Factors That Affect MLOV Performance.

2. In Siebel Tools, display the following object types:
   • Dock Object
   • Dock Object Visibility Rule

     For more information, see Displaying Object Types You Use to Configure Siebel CRM.

3. Make sure the list of values is translatable:
   1. In Siebel Tools, in the List of Values list, locate the list of values you must modify.

      For more information, see Creating a New List of Values.

   2. Make sure the Translate property contains a check mark.

      For more information, see Modifying the Translate Property.

   3. Make sure the Multilingual property contains a check mark.
4. Make sure the list is bounded:
   1. In the Object Explorer, click the Flat tab, and then click Pick List.
   2. In the Pick Lists list, query the Type Value property for the type of list of values you must modify.
   3. Make sure the Bounded property contains a check mark.
5. Make sure the columns that the list references are bounded and consistent:
   1. In the Object Explorer, click Column.
   2. In the Columns list, query the LOV Type property for the list of values type you must modify.
   3. Make sure the LOV Bounded property for each column contains a check mark.

      For more information, see Example of Determining If the List Is Bounded.

   4. Make sure the Translation Table Name property is set to S_LST_OF_VAL for all columns.
   5. Make sure the LOV Type for the list matches the LOV Type of the column that the field for the list references.
6. Make sure you can use the column with an MLOV.

   For more information, see Columns That You Cannot Use with an MLOV.

7. Make sure the column that is referenced by the field that uses the list contains the following property.

   Property	Value
   Translation Table Name	S_LST_OF_VAL

8. Check the visibility rules for references to the list of values that is a part of your MLOV configuration:
   1. In the Object Explorer, click the Flat tab, and then click Dock Object Visibility Rule.
   2. In the Dock Object Visibility Rules list, query the SQL Statement field for literals across all rows that are not empty.
   3. Identify the values that Siebel CRM must translate.
   4. If necessary, modify the Display Value to the language-independent code.

      You must modify the display value for any reference in a visibility rule that references a list of values entry for a type that you configure for multilingual support. Note that you cannot modify visibility rules.

9. Compile your modifications.
10. Configure display values for each language you must support:
    1. Open the Siebel client, navigate to the Administration - Data screen, and then click the List of Values link.
    2. Locate the list of values you must modify.
    3. Create a new record for each display value for the type of list of values that you use for a language.

       For more information, see Adding Records for All Supported Languages.

    4. Repeat Step c for each language you must support.
11. Use the MLOV Converter Utility to convert data for the current lists of values.

    For more information, see Converting Your Current Data for an MLOV.

12. Test your modifications.

Example of Determining If the List Is Bounded

Table 74 lists columns for the AVAILABILITY_STATUS list of values type. Three of the columns are bounded, but you cannot configure these columns as multilingual because the NEXT_AVAIL_CD column is not bounded. If you run the MLOV Converter Utility on this configuration, then the utility displays an error message similar to columns are inconsistently bounded. For more information, see Fixing an Inconsistently Bounded List of Values or an Improperly Set Translation Table Property.

You can modify the LOV Bounded and LOV Type properties of the column in the following situations:

• For a predefined column that is not already assigned to a predefined list of values type.
• For a predefined column that is already assigned to a predefined list of values type and that has the LOV Bounded property set to FALSE, you can modify the LOV Bounded property to TRUE. Siebel CRM supports this configuration only in the context of enabling an MLOV.

You can configure a custom extension column for use with an MLOV. Do not configure a column for an MLOV unless you are sure that you intend to use that column in your implementation.

Example of Translating Names That Siebel CRM Displays in a List of Values

The Tactics GanttChart Ax Applet - Home Page applet is a standard Gantt chart applet that is part of the Home Page View (DBM) view. This applet is similar to the FS DB Planned GanttChart AX Applet in the predefined FS AxGanttChart View. The FS Dispatch Board Screen includes the FS AxGanttChart View.

The following LOV types control how Siebel CRM displays information in the Tactics GanttChart Ax Applet - Home Page applet:

• The MONTH_NAME LOV type controls the month names.
• The DAY_NAME LOV type controls the day names.

Siebel CRM displays the month and day names in the right frame of the Gantt chart applet. This frame includes scheduled time periods in a calendar. You can translate the month and day names.

To translate names that Siebel CRM displays in a list of values

1. In Siebel Tools, in the List of Values list, locate the list of values you must modify.

   For more information, see Creating a New List of Values.

2. Add translated display values for the languages that Siebel CRM must display.

   For more information, see Adding Records for All Supported Languages.

3. Make sure the Multilingual property contains a check mark for the LOV type row and the display value rows.

Columns That You Cannot Use with an MLOV

Table 75 lists columns that you cannot use with an MLOV.