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

About the MLOV Upgrade Log File

After the utility runs in either validation mode or translation mode, it writes any errors to a log file. The default names of the log files are mlovupgd_verify.log and mlovupgd_translate.log. The files are located in the siebsrvr/LOG directory.

• LOVs Inconsistently Bounded or Translation Table Property Not Set to S_LST_VAL. The message that appears in the log file for LOVs that have the bounded property on columns where they are used set inconsistently (one bounded and one not bounded) or LOV domains that do not have the Translation Table property set to S_LST_VAL is the following:

  The following Validation checks for:

  1- Two or more columns defined in the same LOV domain are inconsistently bounded (one bounded, one not)

  2- Two or more columns are defined in the same LOV domain and at least one of them does not have a Translation Table Name of S_LST_OF_VAL.

  Any errors of these types are listed in the log file. The information listed includes the LOV Type, Column, and Table.

To fix the LOV types that appear in the log file

1. Open Siebel Tools, and connect to the server database.
2. Select the Flat tab in the Object Explorer.
3. Select the Column object type.
4. Choose Query > New Query, and then enter the name of the list of values type that has a problem in the LOV Type property.
5. Press Enter to execute the query.
6. For the columns displayed, make sure they are LOV BOUNDED = Y.
7. Set the Translation Table Name for the columns displayed to S_LST_OF_VAL.
8. Run MLOV Upgrade Utility in validation mode to make sure that there are no more errors.

• LOV Domains Not in the S_LST_OF_VAL Table. The message that appears in the log file for LOV domains that are not represented in S_LST_OF_VAL table is the following:

  The following Validation checks for:

  LOV domains in the repository that are not represented in S_LST_OF_VAL

  This message means that an LOV domain is in the repository, but is not represented as a value in the list of values table, with a list of values type of LOV_TYPE. This can happen when you delete a record in the list of values table, instead of deactivating it, or when you enter an incorrect entry in the LOV Type property for a column added using a database extension.

  For more information, refer to Deleting Compared to Deactivating MLOV Records.

  To fix this problem, add the LOV domain in the List of Values Administration view and specify LOV_TYPE in the Type list column, or correct the entry in the LOV Type property in the repository. For more information, see About Adding Records for MLOV Fields.

  For any values found in the target tables without matching records in the list of values table, the script will create a matching record in the list of values table. These records are marked as inactive. Remember to add language-specific entries for these base records, so that they display in the active language.

Recompiling and Deploying

Every time you change the configuration to enable another column to be multilingual, you must compile a new .srf file based on the newly configured repository. Only the Newtable project needs to be compiled again. Additionally, you need to deploy the changes to users so that users can see the configured picklists in the desired language.