Discrepancy in COLLECTIONS_SCENARIO_T Table Columns Data Structure
(Doc ID 1592896.1)
Last updated on SEPTEMBER 14, 2022
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Goal
Consider integration scenario between Siebel and Billing and Revenue Management (BRM) using Application Integration Architecture (AIA) (Agent Assisted Billing Care (AABC) Oracle Data Integrator (ODI Process Integration Pack (PIP) 11.2):
It is known that ODI is used by AIA to gather Collections data from collections_scenario_t table in BRM. It has been observed that the value in amount columns ($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 is a database-to-database 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.,
OVERDUE_AMOUNT,
ENTRY_AMOUNT,
EXIT_AMOUNT
..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 ?
Solution
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
| Goal |
| Solution |
| References |