Two /event/billing/sub_bal_validity Created During First Usage For Account With Subscription Group
(Doc ID 2961610.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
When an account has a primary and secondary service in a subscription group and Elastic Charging Engine (ECE) sends a first usage notification to Billing and Revenue Manager (BRM), two /event/billing/sub_bal_validity events are generated with exactly the same information and without service object populated in the event.
Since some customers are using this event in the event notification mechanism in BRM, the fact that they are getting the event duplicated means that also the action triggered by the called opcode will be done twice.
Customer has group notification enabled in ECE and so the two events happen because of the two services being in a subscription group.
Expectation: Each events have the service object populated so customers can distinguish between both events and take the appropriate action
Changes
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 |
Changes |
Cause |
Solution |
References |