Last updated on AUGUST 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Subscription Management
When a deal configured with cycle_forward_annual event for non currency bundles is purchased in last couple of days in a month, then non currency sub balances are provided with overlapping validity period.
01.04.2014 - Create customer and subscription account with 1st as billing date and with any monthly cycle arrear charge deal (This deal is not dependent to the current issue and any currency charging deal can be purchased just to track the billing)
10.04.2014 - For subscription account, purchase a deal configured with cycle_forward_annual event for non currency bundles that provides sub balances 12 months in advance. Here two sub balances, one for 10.Apr.2014 to 09.Apr.2015 period and another for 10.Apr.2015 to 09.Apr.2016 period. This is expected and fine.
29.04.2014 - For subscription account, purchase another deal similarly configured with cycle_forward_annual event for non currency bundles that provides sub balances 12 months in advance. Here three sub balances, first one for 29.Apr.2014 to 28.Apr.2015 period, second for 01.May.2014 to 30.Apr.2015 period and third for 01.May.2015 to 30.Apr.2016 period.
Here sub balances are provided with overlapping periods instead of providing two sub balances, one for 29.Apr.2014 to 28.Apr.2015 period and another for 29.Apr.2015 to 28.Apr.2016 period.
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