After upgrading Siebel applications to a higher release, certain columns that were previously not List-of-Value (LOV) bounded became LOV bounded that could cause EIM import failure Oracle Siebel highly recommends that users evaluate the potential impact of schema upgrade before they perform any EIM loading in a new release.

If a field in a business component is associated with a bounded pick list, the base column that the field is mapped to will become LOV bounded to maintain consistency. More columns become LOV bounded after upgrading Siebel applications to a higher release.

EIM import would fail in a new release if a user does not populate the valid LOV data in EIM interface table. You may get the following error in EIM log files:
"This column contains a bounded picklist value and the value given does not correspond to a value in the list-of-values table for the given picklist type."

The following approaches are strongly recommended:

Run utleimdiff.exe utility to compare the differences of EIM interface tables between the old repository and new repository. For detailed instruction on how to run this utility, please refer to FAQ 1737: How can users find differences in all interface tables between two repositories? On Oracle Siebel support web.

The following SQL scripts are used to identify all the changes of LOV bounded columns between two repositories:

lov_diff_check.sql

This script compares differences between the older repository and the new repository. It will generate a list of LOV columns that were changed from LOV un-bounded to LOV bounded in the new repository. Users need to include the names of the two repositories in the first two lines of the SQL script. For example:
Define repository1 = "Siebel Repository 14068 FINS"
Define repository2 = "Siebel Repository 14010 FINS"

In addition, users can run this script to generate a list of LOV columns for the specific EIM tables by modifying the following statement in the script:
And IT2.NAME in ('EIM_FN_CENSUS')