Charges Assigned To Incorrect Bill After Pin_rerate (Doc ID 1392824.1)
Last updated on SEPTEMBER 15, 2016
Oracle Communications Billing and Revenue Management - Version: 18.104.22.168.0 and later [Release: 7.3.0 and later ] Information in this document applies to any platform.
Charges generated by system rerating run in delayed period after running of any functionality triggering auto-billing, are sometimes assigned to next_bill_obj_id0 instead of bill_obj_id0. This happens in about 30% of the cases.
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