EIM Import fails with "NULL values in IF table for required base table columns. (severity 7)" when the target attachment file is not found.
(Doc ID 1497026.1)
Last updated on JANUARY 03, 2023
Applies to:
Siebel Enterprise Integration Manager - Version 8.1.1 [21112] and laterInformation in this document applies to any platform.
Symptoms
To import an attachment file, concatenation of ATT_FILE_NAME and ATT_FILE_EXT columns on the corresponding EIM table must represent the actual attachment file name. This file also must reside on the location specified by ATTACHMENT DIRECTORY paramter (Default = SIEBEL_HOME\INPUT).
If the condtion is not met, the import operation of the attachment file fails but the error message may not be very clear as below.
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 NULL values in IF table for required base table columns. (severity 7)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 Interface table:
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 EIM_ACCNT_DTL (EIM_ACCNT_DTL)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 -------------
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ATT_FILE_NAME (File Routing Processing Column)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ATT_GNRC_DATA_FLG (GNRC_DATA_FLG)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ACCNT_BI (Name)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 NAME (Name)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 LOC (Site)
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 Base table:
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 S_ACCNT_ATT (Account File Attachment)
...
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 rem Failure Log: get columns which failed
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 rem (started at 10/8/12 15:18)
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 rem
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 SELECT ROW_ID,
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 ATT_FILE_NAME,
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 ATT_GNRC_DATA_FLG,
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 ACCNT_BI,
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 NAME,
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 LOC
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 FROM SIA81.EIM_ACCNT_DTL
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 WHERE (T_ACCNT_ATT__STA = 115 AND
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 IF_ROW_BATCH_NUM = ?)
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 ?1: 2010
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 ;
EIMSQL EIMSQLSubEvent 4 00004c8f507304cc:0 2012-10-08 15:18:19 rem Query executed. Execution (only) time: 0s
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ROW_ID ATT_FILE_NAME ATT_GNRC_DATA_FLG ACCNT_BI NAME LOC
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ------ ----------------- ----------------- -------- -------- -----
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 X-4-1 apply_tables.txt N 0-R9NH test account NULL
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 ------ ----------------- ----------------- -------- -------- -----
EIMError EIMErrorSubEvent 0 00004c8f507304cc:0 2012-10-08 15:18:19 (only row which failed)
Above message showed what record was failed to import, but the reason was not clear.
Once the event log "EIM Trace" (EIMTrace) was set to 3 or higher, additional message error was recorded as below.
EIMTrace EIMTraceSubEvent 3 00004e37507304cc:0 2012-10-08 15:41:36 Attachment Not Found: E:\S81\siebsrvr\input\apply_tables.txt.txt
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |