Last Monthly Charge Is Not Correct When Plan Is Ended In New Tier
Last updated on APRIL 05, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
We have a business scenario where customer will not give plan end date during plan purchase but they will update few months/days in advance before product end date.
In this case, product end date is pre-defined at the time of open billing. When we run open billing for the month where product is going to be terminated, BRM should charge up to the product cycle end date. It is charging up to product cycle end date, but the charge is not correct.
Steps to reproduce
1. Created an account by purchasing the product ( which is valid from, let say, Mar 5 2013 to null ).
DOM is 1, and config_billing_delay is 1
2. Moved pvt to Feb 2, 2015, 12 hours; ran billing.
Bills got created and total amount is $3827.0322580645.
3. Moved pvt to Feb 15, 2015, 12 hours; changed the end of the product to Mar 16th.
4. Moved pvt to Mar 1, 2015, 12 hours; ran billing.
Cycle Forward got created for Mar 1st to Mar 16th with value $32.709.
Expected value is $82.98.
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