Credit Limit Error During Rerating
(Doc ID 3045973.1)
Last updated on SEPTEMBER 10, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.5.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
The user has upgraded from Billing and Revenue Management (BRM) 7.5 and Elastic Charging Engine (ECE) 11.7 to BRM 12 Patch Set (PS) 5, and ECE PS5 Interim Patch (IP) 5.
Rerating on demand results in error CREDIT LIMIT BREACH during rerating of usage and grant. Rerating is performing by executing PCM_OP_SUBSCRIPTION_RERATE_REBILL directly via custom opcode (not using pin_rerate).
EXPECTED BEHAVIOR
-----------------------
Rerate on demand should proceed without error PIN_ERR_CREDIT_LIMIT_EXCEEDED
STEPS
---------------------
1. Purchase bundle with consumption rule
2. Purchase bundle with resource grant
3. Rate usage
4. Run rerating on demand.
From the logs, the details regarding the current balance for balanceItemId=32 before the balance update is as followed:
After the balance update, the impact amount of 2048 is added to the current balance of -1024, resulting in a new balance of 1024. Since the credit ceiling is set to 0, this causes a Credit Ceiling Breach.
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 |