Inconsistent Pointers On Rollover Correction Event
(Doc ID 1371087.1)
Last updated on FEBRUARY 13, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
The item object points to the latest bill, and the service object points to the current bill in the rollover correction event. And both objects (item/service) are not populated on the rollover correction event.
Steps to reproduce:
1. Configure a product with rollover, e.g.
Rollover UOM : Months
Maximum Rollover cycles : 3
Max. Rollover Amount : 300
Max. cumulative rollover : 900
2. Set the Delay Billing to 5 in ~/sys/cm/pin.conf
3. Create an account to purchase the above product on Jan 1
4. Run partial billing on Feb 1
5. Load delayed usages from Jan on Feb 3.
6. Run billing on Feb 5
The item object and the service object point to the same bill and also populated on the rollover correct event.
The item object and the service object point to the latest and current bill and no population on both objects on the rollover correct event.
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