Cycle Start And End Date Should Be Set On The Date Recharge Made

(Doc ID 2167430.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : version, Subscription Management

It is observed in OOB BRM, in a pre-paid scenario, even if the cycle renewal is not charged the cycle is advanced as per normal cycle.
For example, if cycle is of 7 days and when the pin cycle fees runs on the start date of the next cycle, it advances the cycle start and end date even if the renewal charge is not applied because of low balance or no balance.

If the credit balance does not exist and renewal of cycle product takes place on the renewal date. In the renewal flow, it throws a message Rating status as CREDIT_LIMIT_EXCEEDED and set unrated_quantity as 1 but renewal cycle start and end date advances.

If the customer does recharge/payment and sufficient balance some day after renewal then cycle should be set accordingly and start date should be set as the recharge date.
Current product does not do the same rather it waits for the next cycle renewal date and on that date it applies the charge.
So for the last cycle customer uses the service and there is a revenue leakage. If the product is inactivated by any custom means then also activation is expected and cycle resetting as on the date recharge/payment is made.


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