Last updated on JULY 03, 2017
Applies to:Siebel CRM - Version 15.2 [IP2015] and later
Information in this document applies to any platform.
EIM creates redundant rows in S_OPTY extension tables
Suppose a new Opportunity record is inserted through Siebel UI, and fill only a couple of fields that map to S_OPTY.
Save the record, and as a result Siebel creates a new row in S_OPTY but doesn’t create any on S_OPTY_X, S_OPTY_UTX and similar tables (if none of the fields from those extension tables were updated).
How to set up the same logic using EIM?
The IFB being used is as follows:
[Siebel Interface Manager]
PROCESS = IMPORT_OPPORTUNITY_DTL
TYPE = SHELL
INCLUDE = IMP_OPTY_DTL
TYPE = IMPORT
BATCH = $BATCH
LOG TRANSACTIONS = FALSE
USE INDEX HINTS = TRUE
TABLE = EIM_OPTY_DTL
ONLY BASE TABLES = S_OPTY, S_OPTY_X, S_OPTY_UTX
INSERT ROWS = S_OPTY, FALSE
INSERT ROWS = S_OPTY_X, TRUE
INSERT ROWS = S_OPTY_UTX, TRUE
ONLY BASE COLUMNS = S_OPTY.NAME,\
So, in a situation if, for instance, EIM_OPTY_DTL.UTX_PAYBACK_PERIOD (that maps to S_OPTY_UTX.PAYBACK_PERIOD) is filled with a value, obviously, a new record is created in S_OPTY_UTX.
However, if EIM_OPTY_DTL.UTX_PAYBACK_PERIOD is null, we would expect that no row is inserted into S_OPTY_UTX, but it is.
Similar situation with S_OPTY_X table and ATTRIB_06, ATTRIB_19, ATTRIB_20, ATTRIB_21 columns.
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