Incorrect Balance Reservations on Auto Topups
(Doc ID 2932336.1)
Last updated on MARCH 06, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Goal
After bundle change, when auto topups are granted, extra 0 balance auto topup bucket is created which is not expected
Steps:
1. Created a customer with Login: xxxx
customer ID: yyyyy , Balance ID: zzzzz
Bundle: abc (no auto topup discounts are not purchased here)
DA(Daily Allowance) balance : 10MB
2. Update request (request number: 1) with Requested Service Units (RSU):10MB
DA: Current balance: 10MB , Account Receivable(AR):10MB, Credit Request(CR): 0
3. Update request (request number: 2) UsedServiceUnit(USU):10MB
DA: Current balance: 10MB , AR:0MB, CR: 10MB
4. Change bundle to xyz (auto topup discounts are purchased here)
New DA balance is 0.
5. Update request (request number: 3) with USU:10MB
As DA balance is 0 and auto topup discounts are available, auto topup is triggered here
DA: Current balance: 0MB
balanceItemId = 5, current balance: 1014MB (10MB consumed and committed) , AR: 10MB, CR:0MB
But here an extra 0 balance bucket with no valid_to is created and 10MB is consumed which is not expected.
How to fix this extra bucket issue?
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 |
References |