EIM S_CON_ADDR and S_ADDR_PER
(Doc ID 544769.1)
Last updated on JANUARY 24, 2019
Applies to:Siebel Enterprise Integration Manager - Version 188.8.131.52 SIA  to 184.108.40.206 SIA [Release V7 to V8]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 220.127.116.11  Fin Svcs
Database: Oracle 18.104.22.168
Application Server OS: Sun Solaris 9
Database Server OS: HP-UX 11i
***Checked for relevance on 20-Oct-2015***
In our SIA application, account and contact addresses both use s_con_addr and s_addr_per.
We are trying to load account addresses into the 2 tables using eim_addr_per.
s_con_addr has foreign key addr_per_id. eim_addr_per mapping for that foreign key is only ap_addr_name column.
In s_addr_per, the user key is addr_name/per_id.
We have a situation where s_addr_per already has 2 records with the same addr_name but different per_id.
Now when we load addresses for accounts, we have if_row_stat of 'AMBIGUOUS' because eim_addr_per is using only ap_addr_name to resolve the foreign key but s_addr_per has a different user key that allows for 2 rows with same addr_name.
How should we resolve the AMBIGUOUS eim status?
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