First Month Not Charged If Arrear Deal Purchased and End Date Set For Future Twice In Same Month
(Doc ID 1911041.1)
Last updated on APRIL 05, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On BRM 7.4, it has been observed that If a monthly cycle arrear deal is purchased and later in the same first month, end date is set in future twice, then the charge of that deal for first month is not applied.
It is expected that if a monthly cycle arrear deal is purchased and later in the same first month, end date is set in future twice, then the charge of that deal for first month should be applied. The following steps are an example how to reproduce this problem :
- 01.Jun.2014 - Create a subscription account with 1st as billing date and with a cycle_forward_arrear charging deal to start from current date and without end date.
- 02.Jun.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 05.Jun.2014 - Set end as 15.Aug.2014 to the previously purchased deal using op_subscription_set_prodinfo opcode.
- 06.Jun.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 21.Jun.2014 - Set end again as 15.Sep.2014 to the previously purchased deal using op_subscription_set_prodinfo opcode.
- 22.Jun.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 06.Jul.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 06.Jul.2014 - Do billing, Here charges of first month, June, for the deal is not applied
- 06.Aug.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 06.Aug.2014 - Do billing, Here charges of July for the deal is applied
- 06.Sep.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 06.Sep.2014 - Do billing, Here charges of August for the deal is applied
- 06.Oct.2014 - Run pin_cycle_fees with purchase, cancel and cycle_fees options
- 06.Oct.2014 - Do billing, Here charges from 01.Sep.2014 to 15.Sep.2014 for the deal is applied
Changes
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 |
Changes |
Cause |
Solution |
References |