My Oracle Support Banner

Failure in Re-activation After the Number of Days Set in Parameter ExpiredPurchasedChargesRetentionIntervalInDays (Doc ID 2614338.1)

Last updated on JUNE 03, 2022

Applies to:

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



  1. The following parameters are in "charging-settings.xml" configuration file of Elastic Charging Engine (ECE):


  2. On 15-Mar-2019, customer purchased a Bundle with validity ending on 01-Apr-2019 00:00:00
  3. On 20-Mar-2019, customer gets suspended (or inactivated in other words)
  4. Services and Products/Discounts are set to inactive status upon Suspension using opcode PCM_OP_CUST_UPDATE_SERVICES
  5. On 5-April-2019, customer un-suspends (or re-activates in other words) the above account using PCM_OP_CUST_UPDATE_SERVICES opcode wherein the same objects that are set to inactive status previously are now set to active status
  6. At this point, there is an error in cm (connection manager) pinlog during publish of information to ECE
  7. This error is thrown apparently because the PurchasedOffering is removed from ECE cache as the parameter expiredPurchasedChargesRetentionIntervalInDays is set to 3 days only
  8. Furthermore pin_cycle_fees/pin_discount_cleanup is executed daily with 'cancel' option but this does not pick up the inactive products and discounts so that they can be canceled; this point is raised because if the inactive products or discounts can be cancelled on their expiration date, then during un-suspension in step 5, the error would not occur






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.