Discount Order not following Priority
(Doc ID 2213783.1)
Last updated on APRIL 05, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.5.0.16.0 version, Pipeline Manager
When discounting occurs and multiple discounts are considered at once, a discount with lower priority is used before a discount with higher priority.
ACTUAL BEHAVIOR
------------------------------
Discount order is not properly applied.
Ex: BALANCES of [3000016] applied before BALANCES [3000031]
EXPECTED BEHAVIOR
-----------------------------------
BALANCES of [3000031] should be applied before BALANCES [3000016]
STEPS
-----------------------
- With configured discount models:
Discount - Using EXXX, on [3000031], Priority 200
Discount - Using QXXX, on [3000016], Priority 170
- Create a new account and purchased both discounts.
- Generate usage which triggered discounts.
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 |