Incorrect Charge For A Rate Change Scenario With Purchase Within 2 Cycles Of The Rate Change
(Doc ID 2433519.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
There is an incorrect charge for a rate change scenario below with purchase within 2 cycles of the rate change. The product charges 2 months in-advance and rate change is configured as "Enable enhanced rate change management feature".
1. A product with rate change on 1st June 2018.
2. pin.conf entry (- fm_subscription rate_change 1)
3. The product charges 2 months in advance.
4. Customer cycle day 4.
5. Purchase this product on 8th April 2018 with an purchase end date of 4th June 2018
6. Since the product is 2 months in-advance, this order generates the following charges -
i. 8th April 2018 to 4th May 2018 -- Current accounting cycle
ii. 4th May 2018 to 1st June 2018 -- Prorated old charge for next accounting cycle
iii. 1st June 2018 to 4th June 2018 -- Prorated new charge for next accounting cycle
The scale for 2 split events from 4th May to 1st June and 1st June to 4th June is set 0.000000 and hence $0 charge.
This is only the case at the purchase time. If such a product is purchased earlier (say in Jan 2018) with the same end date (4th June), and billing generates the events from 4th May to 1st June and 1st June to 4th June, then the scale and charge are correct.
The prorated scale should be set correctly for 2 split events from 4th May to 1st June and from 1st June to 4th June to charge correctly.
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