Tiered Aggregation Discount Impact Current Counter For CDR From Previous Billing Cycles.
(Doc ID 2609961.1)
Last updated on FEBRUARY 08, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Pipeline Manager
Given the following scenario:
- Current date is 3rd of June 2019
- May 1 - May 31st 2019 -- Bill run has been finalized (previous cycle)
- June 1 - June 31st 2019 -- Bill run not happened (current cycle)
- A delayed CDR having start time in previous cycle (May 29th, 2019) is coming.
Aggregation counters and tiered discounting feature is implemented as explained bellow:
Let's assume that for the period "May 1 - May 31st" balance for the aggregation counter was BAL(123) = 12
Bill run happened for May month
For the period "June 1 - June 31st" balance for the aggregation counter is BAL(123) = 2
There is tiered discounting eligible for the usage events.
Tiered Discount slabs are :
when BAL(123) is between
slab 1 : 0 - 5 ---> 2 % discount
slab 2 : 6 - 10 ----> 2.5 % discount
slab 3 : 11 - 50 -----> 3 % discount
slab 4 : 51 - Infinity ----> 100% discount
It is expected that when a delayed cdr is received in a current cycle, it should refer the balance of the aggregation counter of corresponding cycle(previous cycle, as per CDR start time) and then apply the tiered discounting which is eligible as per the value of the previous cycle.
In above mentioned scenario it should be referring the previous balance of BAL(123) = 12 and aggregate to that balance so the new balance of aggregation counter for May month cycle should be BAL(123) = 13 and this should be used to calculate the discount tier. So delayed cdr should be applied with the discount as per slab3 .
How it should be configured in order to obtain expected behavior?
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