Last updated on JULY 20, 2016
Applies to:Siebel Enterprise Integration Manager - Version 220.127.116.11 SIA  to 18.104.22.168  [Release V7 to V8]
Information in this document applies to any platform.
Statement of what the issue is
Siebel/Platform: 22.214.171.124 SIA /Windows 2003
Database/Platform: Oracle 10.1.0.5/HP-UX
This issue is database independent but may be Siebel version dependent
Loss of functionality
For some of the records, the primary column PR_ADDR_ID on S_ORG_EXT is not being updated correctly by EIM.
Sequence of events/Steps to reproduce
The requirement is to update S_ORG_EXT.PR_ADDR_ID through EIM for about 950 records.
1) Populated EIM_ACCOUNT2 with required data, as this is the table that you would use to update the primary column. This involves populating user keys for S_PARTY, S_ORG_EXT and S_CON_ADDR tables. In addition, the explicit primary column ACC_PR_ADDR was also be populated, which is a requirement for EIM to update the primary PR_ADDR_ID.
2) Created ifb file. This ifb file is created to allow updates on S_ORG_EXT table.
3) Ran EIM.
The process does not update 3 records (on S_ORG_EXT.PR_ADDR_ID) correctly out of 950 records. It was observed that EIM is unable to identify the unique S_CON_ADDR rows associated with these 3 EIM_ACCOUNT2 records. This means EIM fails to populate the correct T_CON_ADDR__RID value, which as a result is unable to populate the primary column.
Where it happened
The issue occurs with update on S_ORG_EXT, which can reproduced using either GUI or command line.
The significance of loss
The update on S_ORG_EXT.PR_ADDR_ID is partially successful. As a result, the primary column do not show right values in the application.
Process [soe_pr_addr_id] had all rows fail
on EIM_ACCOUNT2 for batch 70200:
Import processing failed for all rows. (severity 3)
All rows specified for importing in this process failed. Either no rows were
specified or all rows could not be imported into the base tables.
All rows failed to be processed for this interface table. Either the data in
the rows is invalid for import or row specifications did not match any existing
base table rows for export, delete or merge.
Note: The above error message shows all rows were failed because this is the result of rerunning EIM job with the 3 records that were not imported previously. This detail log message that was created after the customer was instructed to set detail logging following the original import with 950 records.
What is working
EIM updates about 947 records on S_ORG_EXT.PR_ADDR_ID, which means the update on the primary column runs correctly on partial set of records.
EIM is expected to work on all the records involved to update the primary column.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms