EIM Mapping for Custom tables
(Doc ID 579133.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel Enterprise Integration Manager - Version 8.0  to 8.2.2 SIA [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 16-SEP-2015***
Customer´s requirement was to create a custom 1:M extension table CX_PROFILE to S_ORG_EXT , an intersection table between CX_PROFILE and S_ADDR_PER and the corresponding EIM table mappings for this table.
While creating extension table CX_PROFILE they realized that they could not create extension table to S_ORG_EXT hence they created it as an extension to S_PARTY and created a foreign key reference to S_ORG_EXT. The EIM mappings of CX_PROFILE were created in EIM_ACCOUNT successfully.
When ran EIM mapping wizard for intersection table it has created two foreign keys, one for CX_PROFILE as 'CX_PROFILE Foreign key' and other for S_ADDR_PER as 'S_ADDR_PER Foreign key' after completing EIM mapping, was observed that it has successfully created foreign key mapping columns for 'S_ADDR_PER Foreign key' but it has not created foreign key mapping columns for 'CX_PROFILE Foreign Key'.
The doubt was if EIM mappings could be created for a custom intersection table where one of the tables is custom table.
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