Last updated on AUGUST 23, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 30-Aug-2013.
Checked for relevance on 23-Aug-2016.
The user has configured a currency resource (CAD, 124) in pin_beid to round up to 6 decimal places (dp) ONLY for delayed data events at rating and discounting stages. For all other events/stages, it is rounding up to 2dp. With this setup, the delayed data events are being generated with amounts rounded up to 6dp as expected. The corresponding /item objects are having item_total amount rounded up to 6dp as expected as well.
During billing, the due in /item is being rounded up to 2dp as expected. However, the /journal entries are being created with amounts rounded up to 6dp whereas G/L reports will have the amounts rounded up to 2dp.
This is causing below rounding difference for a particular bill cycle:
The Sum(all journal entries corresponding to a particular GLID) and the amount being shown in the G/L report for that GLID are not same.
It is in the case of a hierarchy with paying parent and non-paying child with differences between Round(an unrounded pending item amount) and Sum(round(journal entries correspond to that item)) for an item belonging to child account, the journal entry for epsilon is not created.
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