During Service Transfer BRM Temporarily Sets Credit Limit to Zero
(Doc ID 2449087.1)
Last updated on MARCH 17, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Billing and Revenue Management (BRM), it is observed that during change of ownership request, the PCM_OP_SUBSCRIPTION_SERVICE_BALGRP_TRANSFER opcode is being called. This opcode, while creating new balance group, is setting the credit limit to zero irrespective of the credit limit of the older balance group.
Due to this, Elastic Charging Engine (ECE) is immediately triggering a ceiling breach event and end users are getting barred just after change of ownership order completion.
Despite calling the set credit limit opcode in same order (which set the credit limit back to the correct value), ECE still triggers the notification.
Steps to reproduce the issue :
- Transfer one service from a billing profile to another billing profile(can be of different account).
- New balance group created will have credit limit as zero.
What is the reason behind this issue?
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