Detailed Explanation Of AABC 2.5 PIP ODI Collections Process
Last updated on MAY 05, 2016
Applies to:Oracle Communications Integration Pack for Agent Assisted Billing Care - Version 2.5 to 2.5 [Release 2.5]
Information in this document applies to any platform.
ODI SYNC COLLECTION ACTIONS :
Regarding the process there are doubts from a global point-of-view of the process
ODI parameter BatchSize - How is this parameter used when reading data from BRM, and later when loading data to Siebel EIM tables?
Please explain with detail to what are the following parameters used for in ODI. IF_ROW_BATCH_NUM_*
What are GLOBAL.Coll_StartTime and GLOBAL.Coll_EndTime used for? How do we use it/set it?
Why is are the default values for IF_ROW_BATCH_NUM_CREATE and IF_ROW_BATCH_NUM_UPDATE 110 and 200 respectively? Are they fixed or do these values change over time?
When loading data from BRM is there logic associated with scenarios and actions? Are they correlated? Do actions from one specific scenario have to have the same BATCH_NUM as the scenario? The scenario's number of actions must always follow a logic? Which logic?
How is processed a collections cycle and it's relation with the values IF_ROW_BATCH_NUM_CREATE (110), IF_ROW_BATCH_NUM_UPDATE (200), BATCH_SIZE, ROWNUM and IF_BATCH_ROW_NUM. If possible please present a cycle execution of the collections process for to better understand the underlying assumptions and mechanisms.
What motives could cause the violation of the SIEBEL.EIM_ALERT_CUT_U1 constraint when loading the data to Siebel EIM_ALERT_CUT table? How are the columns ROW_ID and IF_ROW_BATCH_NUM calculated and used (For e.g. something like "#IF_ROW_BATCH_NUM_CREATE+FLOOR(rownum/#BatchSize)+1! is used, but we need further explanation).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms