My Oracle Support Banner

Delayed Events Fail To Rate When MSISDN Is Changed (Doc ID 2507085.1)

Last updated on SEPTEMBER 04, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


The user has a requirement to support and rate delayed events post MSISDN (Service number/login) change in Oracle Communications Billing and Revenue Management (BRM).

Scenario 1:

Observed that op_cust_update_services calls are syncing to ECE and PublicUserIdentity table is getting populated accordingly. However, these changes are not stored anywhere in BRM. Does this mean there is no need to have anything modified to accommodate this requirement?

Scenario 2:

When ECE is restarted, ECE crashes and data is loaded back through CustomerUpdater process.
As audit is not enabled in field, how will the successive updates on the serviceNumber be available?
Observed that rating failed with "No user data found". Does auditing need to be enabled on the field or is there any alternatives that is followed in ECE?

How to achieve this requirement; currently for few subscribers, delayed events have failed rating.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.