EIM Foreign Key (FK) to Custom Table and EIM support
(Doc ID 517947.1)
Last updated on JANUARY 10, 2019
Applies to:Siebel Enterprise Integration Manager - Version 7.7.1 SIA  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1  Auto
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1476226991.
***Checked for relevance on 11-DNov-2015***
Our business requirements designate that we must create a custom extension table named CX_STATE_DEFAULTS. We also need to create an FK extension column (X_PSC_ID) on S_ASSET, which will have Foreign Key Table "CX_STATE_DEFAULTS". According to SR# 38-886102251, Custom tables will be created with a User Key that is NULL. That same SR also states that EIM does not support Foreign Keys to custom tables.
Our initial data conversion will include more than 10 million Financial Accounts, each of which must be populated with a Foreign Key reference to this custom table. This makes it impossible to populate these base table columns with anything other than EIM. Several questions then.
- Has EIM been enhanced in 7.7 to support resolution of Foreign Keys to custom tables?
- If not, can Solution Support Engineering enable this functionality by creating a valid User Key on the custom table and using Advance Db Extensibility?
- If not, how should be support this requirement and our initial data conversion needs?
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