The Cycle Charges Are Incorret When We Suspend And Resume Account With Annual Bill Cycle (Doc ID 1458339.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.1 [Release 7.3.1]
Information in this document applies to any platform.

Symptoms

When an account  with annual bill cycle is suspended and resumed in a different billing cycle, the product cycle is wrongly triggered.

Steps to reproduce:

1.  Create account having Annual Cycle Forward Product on 28-Dec-11
     -- Account created successfully having Billing Cycle as Dec 28, 2011 to Jan 28, 2012
2.  Change the Bill Frequency to 12 through Customer Center
     -- Billing Cycle became Dec 28, 2011 to Dec 28, 2012.
3.  Change the PVT to Dec 29, 2012
4.  Run billing
     -- Billing Cycle changed to Dec 28, 2012 – Dec 28, 2013.
5.  Change the PVT to Oct 28, 2013
6.  Suspend the account
7.  Change the PVT to Oct 28, 2014 (i.e. Next Bill Cycle)
8.  Resume the account
     -- Billing Cycle changed to Dec 28, 2013 to Dec 28, 2014. This is correct.
     -- Cycle Forward Product Cycle Date changed to Oct 28, 2014 to Oct 28, 2015.This is wrong.

Expected result: the Cycle Forward dates have to be Oct 28, 2014 to Dec 28, 2014.

Cause

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