"Invalid value for bounded picklist column. (severity 6, row eliminated)" EIM error for Target Base Table, but Parent Record Already Exists and EIM job is Only Importing to Child Table, Why are Target Base Table's LOV Bounded Required Columns Validated? (Doc ID 2132315.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Financial Services CRM - Version 8.1.1.14.13 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.13 [IP2014] version, EIM

I just have 1 question, while loading the data in S_WRNTY_CLM_IT, the data got loaded
only when we populated the columns WRCLCLAIMCATEGORYC (Warranty claim category) and
WRCL_STATUS_CD (Warranty claim status) in EIM_WRNTY_CLM.
The above mentioned 2 columns are not required columns for S_WRNTY_CLM_IT and even they
are not part of user keys of S_WRNTY_CLM_IT but still we were not able to load line item data until we populated these 2 columns.

ERROR
-----------------------

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 Process [Import_WRN] had 1 row fail

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 on EIM_WRNTY_CLM for batch 1 in step 4, pass 115:

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 Invalid value for bounded picklist column. (severity 6, row eliminated)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 Interface table:

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 EIM_WRNTY_CLM (EIM_WRNTY_CLM)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 -------------

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 WRCL_STATUS_CD (Claim Status Code)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 Base table:

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 S_WRNTY_CLAIM (Warranty Claim)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 -------------

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 STATUS_CD (Claim Status Code)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 This column contains a bounded picklist value and the value given does not

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 correspond to a value in the list-of-values table for the given picklist type.

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 You can add values through the UI or through the EIM_LST_OF_VAL interface

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 table.

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 This failure caused the rows to be eliminated from further processing for the

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 target base table. This failure will prevent these rows from being imported at

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 all.

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 SQL query to return rows which were eliminated:

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 SELECT ROW_ID,

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 WRCL_STATUS_CD

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 FROM SIEBEL.EIM_WRNTY_CLM

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 WHERE (T_WRNTY_CLAIM__STA = 115 AND

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45 IF_ROW_BATCH_NUM = ?)

EIMError EIMErrorSubEvent 0 0000000657221b48:0 2016-04-28 18:23:45



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Populate the EIM_WRNTY_CLM table to do an IMPORT for the 1:M child table S_WRNTY_CLM_IT.
the parent record for the target base table in S_WRNTY_CLAIM already exists..

BUSINESS IMPACT
-----------------------
If the target base table record already exists and the EIM table table is only populated for a child table, it is unexpected that the EIM interface record fails with a validation check on the
parent target base table's required column that is LOV Bounded.
The EIM job is only creating a record in a child table for an existing parent record, so why is this validated and stopping the eim record from being processed with " Invalid value for bounded picklist column. (severity 6, row eliminated)" error?

Changes

 New EIM ifb created to import records.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms