Discrepancy in COLLECTIONS_SCENARIO_T Table Columns Data Structure
Last updated on OCTOBER 30, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
Consider integration scenario between Siebel and BRM using AIA (AABC ODI PIP 11.2) :
We know that ODI is used by AIA to gather Collections data from collections_scenario_t. It has been observed that the value in amount ($100.20 in BRM for example) gets transformed as rounded value ($100 in ODI and Siebel) hence causing a financial impact for the client.
As per ODI working design, the behavior is expected (when it’s a DB-to-DB conversion) when the column data type is just NUMBER rather than NUMBER-with a precision.
It is seen that there are three columns in table collections_scenario_t, viz.,
..defined as NUMBER without precision and scale, while many other fields have a precision. If the said columns are defined as NUMBER-with a precision (NUMBER(38) for example), then the issue would not surface.
What is the solution to this issue ?
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