Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
The issue occurs when a new service account is created for an existing account within the period defined by the billing delay feature and exists an billing cycle that has been delayed.
The last_cycle is defined for the billinfo of the second service account is set with a value greater than the value defined for next_cycle.
Bill Now is not able to detect the service and to correctly bill it.
ApplyCycleFeeForBillNow = enabled in business param
Product used is a cycle arrear one
1. The pin_virtual_time is set to 1-Jan-2013
2. Delayed Billing is set to 1
3. Restart CM
4. Create two accounts parent and child
5. Change delayed billing to 20
6. Restart CM
7. Move pin_virtual_time to 10-Feb-2013
8. Create another child account
9. Run bill now
The second child account created does not get billed.
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