Last updated on NOVEMBER 11, 2015
Applies to:Siebel Enterprise Integration Manager - Version 188.8.131.52  and later
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0  Life Sci
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2
This document was previously published as Siebel SR 38-3393675731.
***Checked for relevance on 11-Nov-2015***
We ran the EIM Table Mapping Wizard on S_ORG_EXT which added all not-mapped columns to the EIM table EIM_ACCNT_DTL. This is fine, but one of the vanilla column mapping it added was DIRECTIONS, which is a long column. We have only just encountered a problem with this in that when running the ddlsync process during dev to test migration, it fails saying that a table can only have 1 column of type long in it. The EIM_ACCNT_DTL already had a vanilla column called NOTE_NOTE which is a long column.
If we want to use this DIRECTIONS column and map values to it, as well as for the NOTE_NOTE column, do we need to have the DIRECTIONS column mapping in a different EIM table? Why is there nothing in the wizard which prevents us from creating two columns of type long in the same table? Perhaps this should be an enhancement?
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