1. Enterprise Integration Manager Administration Guide
  2. Importing LOV and MLOV Data into Base Tables

Importing LOV and MLOV Data into Base Tables

When importing data into base tables, such as S_ORG_EXT or S_CONTACT, any column that is LOV-bounded in the target base table must be populated with the Display Value in the corresponding column in the EIM table, whether into an LOV column or a multilingual LOV (MLOV) column, you must populate the table column with the display value of a specific language.

The difference between the LOV and MLOV cases is the following:

  • When importing into an LOV column, EIM puts the display value directly into the column.

  • When importing into an MLOV column, EIM translates MLOV values during the import process. The EIM engine looks up the Language Independent Code (LIC) of the display value in the EIM table column and populates the LIC into the MLOV column.

By default, EIM runs in the same language as that of the Siebel Server installation. For example, if the Siebel Server installation is in German, then the LANGUAGE parameter setting defaults to German. You might import an Account Status of "Activ" (English equivalent: Active) into the Account table using EIM, in which case the following takes place:

  • If the column is not MLOV-enabled, then the EIM table loaded with "Aktiv" places that value, "Aktiv", into the Account base table.

  • If the column is MLOV-enabled, then the EIM first translates from German to the Language-Independent Code (LIC) for "Aktiv" ("Active") and places that LIC value into the Account base table.

Note: You must always populate EIM table columns that are mapped to LOV bounded base table columns with values that correspond to S_LST_OF_VAL.VAL, even when MLOV are used.

When importing data LOV data from EIM tables into base tables, you might encounter the following error message in your trace file:

[ERR00] Interface table:
[ERR00] S_XXXX_XMIF (Interface for XXXX Built-In M:1 Extension Table)
[ERR00] --------------
[ERR00]
[ERR00] Base table:
[ERR00] S_XXXX_XM (Account M:1 Extension)
[ERR00] ------------
[ERR00] TYPE (Type)
[ERR00] This column contains a bounded picklist value and the value given does not
[ERR00] correspond to a value in the list-of-values table for the given picklist 
type.

This error message indicates that either a picklist has not been created for this column (TYPE) or the value in your EIM table for this column does not correspond to one of the values in the LOVs available for the corresponding LOV Type. To resolve this issue, you need to make sure that:

  • An LOV Type with associated LOVs already exists for this column.

  • The value you are importing for this column corresponds to one of the values associated to that LOV Type.

The following procedure explains how to import data into an LOV-enabled column, using the LOV Bounded Column S_ORG_EXT.ACCNT_TYPE_CD (which stores the Account Type Code) as an example.

To import data into an LOV-enabled column

  1. Determine the LOV Type for the column in the S_ORG_EXT table, as follows:

    • Search for the table S_ORG_EXT.

    • Expand the Object Explorer to the Column object and query for the column that stores the LOV data (ACCT_TYPE_CD).

    • Identify the LOV Type for the column (CUT_ACCOUNT_TYPE).

    Note: For a column to be LOV bounded, it must have an LOV Type and the LOV Bounded attribute must be TRUE. For a column to be MLOV-enabled, additional attributes must be set: Translate Flag must be set to Y and Translation Table Name must be defined as S_LST_OF_VAL.

  2. Navigate to the List of Values View in the Siebel client and query for that LOV Type (CUT_ACCOUNT_TYPE).

    A list of all Display Values and LICs is presented. Note that EIM runs in a specific language and requires the display values that match that language. For example, if EIM runs in German, then all the values you load into the EIM table for this column must use the DEU display values. The LICs are never used for loading data into base tables via EIM.

  3. Load the EIM table, as follows:

    1. Populate the appropriate EIM table (for example, EIM_ACCNT_CUT) with the account data and set the values in the column mapped to the base column (EIM_ACCNT_CUT.AC_ACCNT_TYPE_CD) to one of the display values identified in the previous step. As noted previously, you cannot use LICs here (unless they happen to match the defined Display Value).

    2. Execute the EIM job.

Related Topics

Importing LOVs Using EIM

Related Books

How List of Values (LOV) or multilingual LOV (MLOV) data is updated or imported in Siebel CRM has evolved relative to earlier releases. For more information about some of the key changes in the LOV framework, first in Siebel CRM 17.0 and then in subsequent update releases, see Using Siebel Tools.

For more information about working with LOVs and MLOVs and about rolling back to a prior version of the runtime repository, see Siebel Applications Administration Guide.

For more information about performing repository migrations, see Siebel Database Upgrade Guide.