My Oracle Support Banner

Inccorrect Range StepQuantity For Cascading Discount When No Impact On Currency Balance Is Defined (Doc ID 2130904.1)

Last updated on MARCH 23, 2019

Applies to:

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

Goal

Scenario :

When there is a second discount rule in cascading mode, with 2 or more ranges, it looks like the the StepQuantity in second range (also the next ones) is not being evaluated correctly to discount only the remaining balance.

Business requirement :

* For an usage, need to debit a bucket1 balance until the available quantity of this balance, and then impact a second counter with the remaining quantity.
* So there is a discount offer, in CASCADING mode (Remaining charge and quantity), with 2 rules:
-- Rule 1 : while balance[Bucket1] < 0 => from 0 to Balance[Bucket1] => debit the balance Bucket1 with 100% of StepQuantity
-- Rule 2 : while balance[Bucket1] = 0 => from 0 to Infinite => impact a noncurrency balance COUNTER with 100% of StepQuantity.

Steps to reproduce :

  1. Pricing Setup :

    charge offer 1 = TelcoGsmTelephony, MCF , 1000 Free Seconds (resource ID = YES) , CREDIT

    charge offer 2 = TelcoGsmTelephony, EventDelayedSessionTelcoGsm , 2 $ per second, DEBIT

    discount offer : EventDelayedSessionTelcoGsm

    rule 1:

    Trigger : Free Seconds Less Than Zero
    Apply this discount to Remaining Charge and Quantity
    To select quantity ranges, evaluate Quantity and Distribute value across applicable quantity ranges
    Quantity Range 0 - Balance[Free Seconds]
    Debit , Free seconds , 100% of StepQuantity.

    rule 2:

    Trigger : FreeSecondsEqualToZero
    Apply this discount to Remaining Charge and Quantity
    To select quantity ranges, evaluate Quantity and Distribute value across applicable quantity ranges
    Quantity Range 0 - No maximum
    Increase , Loyalty Points (this is a counter resource, id = <NAME>), 100% , StepQuantity

  2. Create account with above pricing elements
  3. Initial balance :

     
  4. the above balances seem wrong :

    Expected : when 1000 seconds are rated, 900 are evaluated under Rule 1 , and expected that remaining 100 seconds are evaluated under Rule 2, increasing counter to 100. As per cascading rule.

    Actual : when 1000 seconds are rated, 900 are evaluated under Rule 1 , and actually the whole 1000 seconds are again evaluated under Rule 2, increasing counter to 1000

 

Solution

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
Goal
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.