My Oracle Support Banner

PCM_OP_BAL_CHANGE_VALIDITY Is Not Working in ECE as Expected for a First Usage Based One-time Charge Offer (Doc ID 2859947.1)

Last updated on APRIL 06, 2022

Applies to:

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

Symptoms


Issue is that PCM_OP_BAL_CHANGE_VALIDITY opcode is not working as expected for a first-usage based one-time charge offer wherein the validity change is updated in Billing and Revenue Management (BRM) but not in Elastic Charging Engine (ECE).


Scenario:

Steps to reproduce:

  1. In Pricing Design Center (PDC), create charge offer with first usage validity..  with purchase fee event, credit some non-currency resource, validity is from first usage to 14 days from validity
  2. In PDC, create bundle/package
  3. Create account and purchase above package, 29 Dec
  4. Check ECE balance cache and BRM balance group object, both should reflect same validity. See below snippets, see that duration:"P14D" in ECE cache:

  5. See that in ECE: duration:"P14D" ------> this is not OK, expected is "P30D"
    See that in BRM: PIN_FLD_VALID_TO_DETAILS INT [0] 123908 -----> this is OK

 Note: If the same scenario is repeated with an existing customer where first usage has already triggered the 14 days allowance, then the above is not present.



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
Cause
Solution
References


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