Rating Behaved Differently for Fixed Charge Calls which Overlapped Timezones (Doc ID 2001047.1)

Last updated on JULY 25, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On BRM 7.5 PS6, Batch Rating

Let us consider the below scenario:
(a) Created an account with any plan.
(b) Processed a batch usage corresponding to the call scenario which fell in both Peak (PK) and Offpeak (OP) timezones.
      For e.g, call started from PK and ended in OP with 5 mins falling in PK time and 5 mins in OP time.

Observations:
The RUM group (multi RUM) has the fixed charge $2.5 configured against "DUA" RUM and $0 charge configured against "DUT" RUM.

An end customer has been charged $5.0 initially, and then another balance impact of -$2.5 was there. Although the final charge was proper, values against individual RUMs were wrong.

The main objective was to charge the end customer $2.5 irrespective of the duration and that was how the configuration was made. Since the call fell in both Peak and Offpeak times, 4 charge packets have been created (2 for Peak and 2 for Offpeak).

The main discrepancy:
(a) $2.5 has been charged twice (one for PK time and one for Offpeak time), thereby making the charge against DUA as $5.0
(b) -$2.5 has been refunded, but against DUT, which did not have any charge configured.

Additional Notes:
(a) This is issue is not occurring if the call fell in same timezones (PK/OP).
(b) Minimum charge of $2.5 was configured in the pricemodel.

Expected:
A fixed rate ($2.5) need to be charged for some specific calls irrespective of the duration.

Changes

 

Cause

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