My Oracle Support Banner

Incorrect Charges After Backdated Cycle_Arrear_Semiannual Fee Activation (Doc ID 2423809.1)

Last updated on MARCH 25, 2019

Applies to:

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

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.5.0.16.0 version,

ACTUAL BEHAVIOR
-----------------------
It is observed that the system charges incorrect fees after backdated activation of product with cyclic, arrear, semiannual fee.
Event with this fee should be created 6 cycles after purchased_product start_t but during backdated activation its created at once like it is cyclic forward fee. What is more after 6 cycles from purchased_product created_t, event with this fee is created one more time. In both cases events have incorrect cycle dates.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

(date of action in brackets):
1. (1.1.2017) create account with  effective_t = 1.9.2016 BDOM=1  (billing day of month)
2. (1.1.2017) create service1 with effective_t = 1.9.2016, on this service purchase product with cyclic forward fee (start_t = 1.9.2017)
3. (1.1.2017) create service2 with effective_t = 1.9.2016, on this service purchase product with cyclic, arrear, semiannual fee (start_t = 1.9.2017)
     Event (302005057855039571) /event/billing/product/fee/cycle/cycle_arrear_semiannual is created with cycle_start = 2016-09-01 cycle_end = 2017-06-01
     This event should not be created here since the fee is arrear and semiannual, what is more cycle dates show that it is more than semiannual
4. (1.2.2017) billing
5. (1.3.2017) billing
6. (1.4.2017) billing
7. (1.5.2017) billing
8. (1.6.2017) billing
  event (304661477947771977) /event/billing/product/fee/cycle/cycle_arrear_semiannual is created with cycle_start = 2016-12-01 cycle_end = 2017-06-01
  this event is also incorrect: it should not be created here, cycle dates show that it is semiannual but its cycle dates overlap cycle dates of event 302005057855039571

EXPECTED BEHAVIOR
-----------------------

Events 302005057855039571, 304661477947771977 are not created.
Event /event/billing/product/fee/cycle/cycle_arrear_semiannual is created first time after billing on 1.3.2017 and has cycle dates = 2016.09.01 - 2017.03.01
Second /event/billing/product/fee/cycle/cycle_arrear_semiannual is created after billing on 1.9.2017 and has cycle dates = 2017.03.01 - 2017.09.01

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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