Incorrect Credit Profile Is Set for Daily Bundle Type of Grants (Doc ID 2871019.1)

Last updated on APRIL 08, 2024

Applies to:

Symptoms

 Scenario:

• In a setup with Elastic Charging Engine (ECE) integrated with Billing and Revenue Management (BRM), a user has Daily Bundle functionality to grant some resources when a subscriber uses his handset for the first time.
• A standard pricing configuration created from Pricing Design Center (PDC) is used for that with a conditional Ratable Usage Metric (RUM).
• The issue is that when the Call Detail Record (CDR) comes in and is processed by pin_rel (rated event loader) the corresponding entries in the balance group are created with credit profile of value 0 (no credit floor, no credit limit).
• If one activates some recurring charge offer granting the same resource, then the entry in the balance group is created with credit profile 2 (no credit flor, credit limit = 0).
• System should set consistent credit profile regardless of the path that leads to the balance group update.
• It might be that the source of the problem is in pin_rel plsql package, where the credit profile is hardcoded as 0 if no previously created sub-balance entry is found.

Steps to reproduce:

1. In PDC, create a package which contains a charge offer with first usage grant based on conditional rum (example configuration in <KM 2786998.1>)
2. Create account in Billing Care with above package
3. Bill cycle is 1 Oct to 1 Nov
4. Balance snap shot in ECE and BRM:
    

5. Issue is that:  PIN_FLD_CREDIT_PROFILE INT [0] 0
   Expected is that:  PIN_FLD_CREDIT_PROFILE INT [0] 2

Cause

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