Issue With Backdated Payer Change: Amounts Not Reflecting In Correct Bills
(Doc ID 1597649.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
While creating a new billinfo object backdated to the previous billing cycle and associating the balance group to the new billinfo object, the charges related to the previous billing cycle were not accumulated in this new billinfo object instead it was getting accumulated in the old billinfo object.
1. 10/Nov: Create account
2. 10/Nov: Purchase RC(recurring charge) product
3. 20/Nov: Purchase OTC(one time charge) product
4. 01/Dec: Run partial billing
5. 01/Dec: Purchase OTC product
6. 01/Dec: Create new billinfo (backdated for 30/Nov) and modify balance group (with flag 2) of service to point to new billinfo
As the billinfo is created backdated for 30/Nov, the Recurring Charges(RC) and One Time Charges(OTC) charges for November should be reflected in the bill object of the new billinfo
The RC and OTC charges for Nov are associated with the old billinfo bill objects.
The /billinfo was supposed to be created on 30/Nov but due to some error between AIA (Application Integration Architecture) and BRM, the request came few hours later and the date was changed to 01/Dec.
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