Bill Cycle Validity For Recurring Products And Discounts Is Not Working
(Doc ID 3006982.1)
Last updated on FEBRUARY 28, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.7.0 and laterInformation in this document applies to any platform.
Goal
Given the following scenario for environment running Oracle Communications Billing and Revenue Management (BRM) 12.0.0.7.0 version:
- new account created while having pin virtual time as 3-jan-2024, having Billing Day of Month (BDOM) as 1
- purchase a bundle that includes a product with a CycleForwardMonthly(CFM) charge; bundle is configured to end "6 cycle(s) after Start"
- usage/cycle/purchase end_T are set as following for the relevant /purchased_product object: "Jul 3 00:00:00 2024"
- CFM charge created for period: 3-jan to 01-feb
- move pvt on 1-feb-2024
- run billing
- CFM charge created for period: 01-feb to 01-mar
- move pvt on 1-mar-2024
- run billing
- CFM charge created for period: 01-mar to 01-apr
- move pvt on 1-apr-2024
- run billing
- CFM charge created for period: 01-apr to 01-may
- move pvt on 1-may-2024
- run billing
- CFM charge created for period: 01-may to 01-jun
- move pvt on 1-jun-2024
- run billing
- CFM charge created for period: 01-jun to 01-jul
- move pvt on 1-jul-2024
- run billing
- CFM charge created for period: 01-jul to 03-jul 00:00
actual results : account created on 03-JAN-2024 with BDOM as 1st, it is charging till 03-JULY-2024
expected results : account created on 03-JAN-2024 with BDOM as 1st, it should stop charging after 6 bills i.e it should charge till June 30.
Is this a product defect or it is expected behavior?
Solution
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
Goal |
Solution |
References |