Creating EBAL Multiple Times In Discount Rule Configuration
(Doc ID 2506462.1)
Last updated on JUNE 27, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.20.0 and laterInformation in this document applies to any platform.
Goal
One has created discounting configuration with two rules which get executed one after another and both create the same EBal. What is expected in this case? Should EBal be "overwritten" the second time when it is created or not? Currently it seems that both values of EBal are summed up.
Steps to reproduce:
1. Create a discount model having below 3 discount Rules.
A. Rule 1:
Drum Expression: TotalQ
Rule Type : Tiered
Drum Type : Quantity
Threshold from : 0
Threshold to : 120
Impact/Consume: Euro
Applied To : Event Owner
Percentage : 50%
Base Expression: TotalC
Event Balance ID:511
B. Rule 2:
Drum Expression: TotalQ
Rule Type : Tiered
Drum Type : Quantity
Threshold from : 120
Threshold to : infinity
Impact/Consume: Euro
Applied To : Event Owner
Percentage : 80%
Base Expression: TotalC
Event Balance ID:511
C. Rule 3:
Drum Expression: Ebal(511)
Rule Type : Threshold
Drum Type : Charge
Threshold from : 0
Threshold to : infinity
Impact/Consume: Euro
Applied To : Event Owner
Percentage : 1%
Base Expression: Ebal(511)
2. Create the discount Model with above rules and use OOB (out of box) discount trigger [ DT10%OFF ] with Delayed GSM event
3. Create the discount object for the above discount Model
4. Create the deal having above discount object and use OOB product [Standard GSM Telephony]
5. Create the Plan for the above deal.
6. Create the account via Customer Center and pass the cdr. The discount trace looks like below:
Is this the correct behavior or should EBal value be overwritten with 0.480 instead ?
Solution
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
Goal |
Solution |