Posted by: Mandeep Grewal | July 3, 2009

EIM Data Load of LOV / MLOV / HLOV

EIM process to load LOV,Multilingual List of Value, Hierarchical List of Values, In this article we will learn the steps to upload data in List of values LOV,Multilingual List of Value MLOV, Hierarchical List of Values HLOV and the fields /colums which needs to populated.

LOV (List of Value)

In case of LOV load make sure that the following fields are populated:

o Type (LOV Type)
o Display Value (LOV Value)
o Translate (Y/N)
o Multilingual (Y/N)
o Language Independent Code (LOV Value)
o Active (Y/N)
o Language Name (Language Name)
o Sub Type (Organization name; can be null)

List of Values Fields : Field Description

Type: The type of list of values (the field name).

Display Value: Value as displayed in the drop-down list.

Translate: When checked, indicates that internationalization
is needed

Multilingual: When checked, indicates that the list of values
is part of a multilingual list of values (MLOV). (There is no client or server functionality associated with this field)

Language Independent Code (LIC): Along with the Display Value, the Language Independent Code uniquely identifies a value for a particular LOV type. In most cases the Language Independent Code is the same as the Display Value. However, the Language Independent Code and Display Value are different for multilingual lists of values (MLOVs). MLOVs allow a single logical list item to support multiple display values for users who are accessing the Siebel application in different languages.

Parent LIC (Language Independent Code): The Language Independent Code of a parent list of values. Used in hierarchical lists of values, where the values that will display in a drop-down list are constrained by the value selected in the parent drop-down list of values
There are only parents and children in this hierarchy. Grandchildren are not allowed. This is enforced by limiting the values in the Pick Parent dialog box to those values which do not themselves have parent display values.

Replication Level: Specifies whether the translation is intended for use at all levels in the translation hierarchy or only at the regional level.

High: Extra field available for use by pick maps or
for customization.

Low: Extra field available for use by pick maps
or for customization.

Order: The numerical order in which a value is
displayed within a drop-down list.

Active: When checked, indicates that the value is
displayed to the end user. When
unchecked, indicates that the value is not
displayed to the end user.

Language Name: Language used for the list of values
Display Value field.

Target Low: Extra field used in Smart Reports.

Target High: Extra field used in Smart Reports.

Weighting Factor: Extra field available for use by pick
maps or for customization.

Bitmap: Bitmap file that is displayed.

Description: Description of a specific value.

Some list-of-values fields, such as High, Low, and Weighting Factor, are for use by specialized Siebel C++ code to store additional information about the selected list of values record. In addition, pick maps can use list-of-value fields such as High, Low, and Weighting Factor. Pick maps normally use the Display Value field, which causes the list item selected by the user to be stored in the database exactly as it appears in the list. These fields can be used to populate other fields of the business component in which the pick map is defined.

Analyze the data.
Prepare a mapping sheet by finding the base table columns, EIM columns, required columns, and the user keys.
First load the LOV TYPE.
Then load the values that correspond to this particular Type.

Constraints :
LOVs are constrained in the following ways:

You cannot have children of a list of values entry active when
the parent list of values entry is inactive.

Hierarchical LOVs do not support MLOVs.

LOV_TYPE should not be enabled for multilingual list of
values. It has a single-language entry only.

MLOV (Multilingual List of Value)

LOV’s can be converted to MLOV
MLOV’s allow values to be selected by a user in one language and retrieved by users working with other languages. The value that is stored in the database for the record is the Language Independent Code (LIC) and the Display Value must be consistent with the same LOV Type and language as follows:

o If you have 2 records with the same LIC, LOV Type and Language make sure that both the records are pointing to the same Display Value

o If you have 2 records with the same Display Value, LOV Type and Language make sure that both records point to the same LIC

Language Code parameter controls the language from MLOV display if a preferred language is specified for a user, this setting overrides the parameter value to determine the MLOV Language.

For Example: If MR_MS (Personal Title) list of values were multilingual, lets assume that there are 3 list of values with LIC. That is it will have a Display Value ‘Mr’ in ‘English- American’, ‘Senor’ in ‘Spanish- Modern’ and ‘Herr’ in ‘German’. Then the Spanish people would see Senor , the Germans would see Herr and the English would see Mr in their Personal Title drop down list . Although the Display Value varies across language instances, the stored value in the database when a user selects any one of these is always Mr. because that is the LIC that is associated to Senor, Herr, and Mr.

LOV /MLOV can also be Organization – Enabled. In general LOV’s for newly deployed languages are inactive by default.

The list columns in the list of values for multilingual LOVs:

Multilingual: This field indicates which list of values types have been configured to be multilingual. When you run the MLOV upgrade utility (mlovupgd.exe), it sets this flag for the list of values entries. If you add entries after the script has been executed, you must manually update this information to reflect your configuration.

Language: This field indicates for which language the entry is valid. The entries for this pick list come from the Language Administration view. To access this view, from the application-level menu, choose View > Site Map > Application Administration >Languages.

Translate: This field indicates whether the entry’s display value can be changed—for instance, translated to another language.Only the LOV types that are marked as translatable are candidates for multilingual configuration. For any entries added, you must update this information manually to reflect your configuration .Existing Siebel entries should not be changed. Doing so will not allow the LOV to be translated.

Language-Independent Code: This field is the internal code used for a list of values entry. It is stored in the database when MLOV is enabled and referenced by configurations. The language-independent code must be 30 characters or less. It is typically the English-American version of a particular selection value. The language-independent code cannot be changed.

Display Value: This field is required and holds the text that will appear in pick lists. The display value is stored in the database when MLOV is not enabled. If there are display values for more than one language for a list of values entry, the display value shown is determined by the current active language.

HLOV (Hierarchical List of Values)

Hierarchical Pick lists are dependent on or constrained by values in another pick list. In case of HLOV the Parent LIC column should not be NULL. If the Parent LIC is NULL, then it is not a HLOV.

For Example: On Service Request BC, the Area and Subarea fields use H-LOVs so that the values are available in the Subarea pick list are dependent on the value picked for Area. Here the Area and the Subarea fields both use the pick list that are based on the List Of Values table which use the same LOV_TYPE. Hierarchical pick list set the SUB_TYPE (Parent LIC) field in the child or dependent LOV to the name of the parent LOV. If SUB_TYPE (Parent LIC) is NULL, the pick list is not hierarchical.

There are two techniques commonly used to configure hierarchical pick lists.
o The first technique uses LOV data from the S_LST_OF_VAL table.
o The second technique is implemented by storing hierarchical
data in the S_LOV_REL table.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: