Incorrect Charge for a Rate Change Scenario With Cycle Forward Event
(Doc ID 2835330.1)
Last updated on SEPTEMBER 26, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
Consider this scenario:
1. In ~/cm/pin.conf, set:
#========================================================================
# rate_change
#
# Enables or disables the enhanced rate change management feature.
#
# If this feature is enabled then rate changes for cycle events
# in the middle of the cycle will be handled according to old and
# new rates prorated. If disabled only the old rate will be applied
#
# 0 = (Default) Disable enhanced rate change management feature.
# 1 = Enable enhanced rate change management feature.
#
#========================================================================
- fm_subscription rate_change 1
2. Create product A with two tiers rate:
Tier 1: Oct 21, 21 ~ Jan 1, 22 = $ 0.00
Tier 2: Jan 1, 22 ~ Never Ends = $ 0.77
3. On Nov 17, purchase product A for the account with Billing Day of Month (BDOM) set to 18. The charge (Nov 17, 21 ~ Nov 18, 21) is $ 0.
4. On Nov 18, run billing. The charge (Nov 18, 21 ~ Dec 18, 21) is $ 0.
5. On Dec 18, run billing. Two charges (Dec 18, 21 - Jan 01) is $0, and (Jan 1, 22 - Jan 18, 22) is $ 0.77.
Expectation:
========
0.77 * 0.422258064516134(scale) = 0.548387096774200
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 |