Cycle Charges Applied Twice For Product Having Both Annual And Monthly Cycle Forward Event Configured
(Doc ID 2019114.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Core Billing
Cycle charges applied twice for product having both annual and monthly cycle forward event configured
Cycle charges should not be doubled when both annual and monthly cycle forward event is configured.
Consider the below scenario:
(i) Create an account with plan A (having monthly cycle forward) on 8th Apr’2015 [BDOM -8].
(ii) Change the PVT to 5th May’2015.
(iii) Do plan change to Plan B (having the product where annual and monthly cycle forward event configured) on 5th May’2015.
(iv) Run re-rating [pin_rerate]
(v) Run billing on 8th May’2015.
(a) On doing the plan change proper annual cycle charges of $218.5 (including tax) applied with proper start and end dates (5th May’2015 – 5th May’2016], program name coming as “PLAN TRANSITION”.
(b) On running re-rating two balance impact created one of $218.5 with program name as “pin_rerate” and another - $218.5 with program name “PLAN TRANSITION”.
(c) On running billing on 8th May, one balance impact is getting created with $218.5 with program name as – “TEST BILL”
But the date appears as 5th May’2015, there by making the charge double.
[Please note that in the product $199 is configured against the annual_cycle_forward event and 0 against monthly_cycle_forward event]
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