Cycle Forward Annual Charge Is Not Applied Correctly If Start Date Is Backdated (Doc ID 1952621.1)

Last updated on NOVEMBER 24, 2024

Applies to:

Symptoms

On : BRM 7.5.0.8.0 version, Subscription Management

When a cycle_forward_annual product is purchased with few days back dated in the same month, annual charge is applied for 1 month and again annual charge for 1 year is applied in next month bill run and it is observed only after upgrade to BRM 7.5 PS8 from 74 PS16 ( where the same issue was not present).

STEPS
-----------------------

1. 01.Aug.2014 - Create a parent account without any deals and child account with 1st as billing date and with one monthly_cycle_arrear deal and another annual_cycle_forward deal to start charging from 01.Aug.2014.
2. 02.Sep.2014 - Do billing for both accounts for Aug period. Monthly arrear charges for Aug period and annual forward charges for Aug 2014 to Jul 2015 will be applied.
3. 15.Sep.2014 - Purchase another cycle_forward_annual deal for the child account to start charging from 01.Sep.2014. Here it applies annual charge only for September period.
4. 02.Oct.2014 - Do billing for both accounts for Sep period. Monthly arrear charges for Sep period is applied and for the second annual_cycle_forward deal, one annual charge is applied for only Sep 2014 period and another annual charge is applied from Oct 2014 to Sep 2015 period instead of applying one annual charge covering Sep 2014 to Aug 2015; this is resulting over charging to the customers.

NOTE: Same behavior is observed even if we purchase deal/product with start date as just the previous day.

ACTUAL BEHAVIOR
-----------------------
One annual charge applied for only Sep 2014 period and another annual charge applied from Oct 2014 to Sep 2015 period.

EXPECTED BEHAVIOR
-----------------------
Apply one annual charge covering Sep 2014 to Aug 2015.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.