The Rate Of A Call With A Service With Two Discounts Has Wrong Behavior (Doc ID 2250627.1)

Last updated on APRIL 16, 2017

Applies to:

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

Goal

On : 11.3.0.2.0 version, Rating business logic

The rate of a call with a service with two discounts has wrong behavior

Before the call, the resources of the account are:

- ResourceID R1
-- BalanceElementCode: ULSLPRO
-- BalanceElementID: 1001504
-- Current_Balance: -4839
- This resource is associated with the discount offer:
- Discount D1, which have priority 100 (highest)

- ResourceID R2
-- BalanceElementCode: ULSBCON
-- BalanceElementID: 1001501
-- Current_Balance: -2903
- This resource is associated with the discount offer:
- Discount D2, which have priority 40 (lowest)

After a call of 5400 seconds, the expected behavior is:

- 4839 seconds from resource the resource 'ULSLPRO'/1001504 (consume all)
- 561 seconds from the resource 'ULSBCON'/1001501 (after that, it should have: 2342 )
- The net cost of the call should be 0 (monetary resource)

Instead the actual behavior is

- 4839 seconds from resource the resource 'ULSLPRO'/1001504 (consume all, and it is correct)
- 2903 seconds from the resource 'ULSBCON'/1001501 (consume all, and it is wrong, it should consume only 561)
- 561 seconds that has cost in the final impact of the call (monetary resource, and it is wrong, it should not consume nothing)
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms