Accounts Canceled in BRM Are Not Purged in ECE (Doc ID 2937330.1)

Last updated on MARCH 23, 2023

Applies to:

Goal

An analysis of the growth of accounts charged in Elastic Charging Engine (ECE) has been carried out and has identified which accounts and services that have already been canceled continue in ECE. The synchronization processes between Billing and Revenue Management (BRM) and ECE are always active. Even the accounts that are canceled in BRM are also canceled in ECE, only they continue to be loaded in memory. These canceled accounts are not purged and causing the coherence database to grow day by day. Today, the size of the database has doubled and half of the accounts are canceled in both BRM and ECE.

As a workaround, the user has tested sending a publish opcode to BRM with a CustDelete operation in a development environment and got the same result in ECE, such as executing PCM_OP_CUST_DELETE_ACCT on BRM without deleting the BRM data. Once the accounts are "purged" in this way, any subsequent action will fail because the account does not exist in ECE. However, it is validated that if the account is manually synchronized again, it normalizes. However, the objective is not to reload the account after purging, since they are canceled accounts and with a fairly long period of inactivity.

Could we run this procedure as a workaround to decrease the ECE cache size without deleting BRM information?
Are there any parameters or configuration that eliminate canceled accounts in ECE?

Solution

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