BRM ECE Data are not Synchronized During Reactivation Order
(Doc ID 2964982.1)
Last updated on AUGUST 17, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
- The issue is related to 2-phase commit between Billing and Revenue Management (BRM) and Elastic Charging Engine (ECE).
- There was an issue where existing service, which was part of Discount sharing Group (DSG) group of main subscription, was disconnected and reactivated as a standalone user.
- Post reactivation, it looks like there is synchronization issue between BRM and ECE resulting in suspension of Call Detail Records (CDRs) and 5031 DIAMETER ERROR (since no ratable product is found).
- Once the account is synchronized via incremental loading, one is able to recycle the suspended CDRs and new CDRs are also rated as expected.
<TEST_NUMBER> was disconnected at 25-AUG-2021 15:29:44 EUROPE/STOCKHOLM CEST and reactivated at 25-AUG-2021 15:31:57 EUROPE/STOCKHOLM CEST. The disconnected number has service poid: 30793012738 while the new activated instance has service poid: 35251091357.
However, in ECE cache, the old service poid is shown active, while in BRM it is inactive. Below is ECE cache snippet:
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