Fields Like ChargeableUnit And ChargedUnit Are Wrongly Calculated In TAP Out File Generation (Doc ID 1926333.1)

Last updated on MARCH 08, 2019

Applies to:

Goal

On BRM Pipeline Roaming:

Issue:

In a customer system, it was experienced that the ChargeableUnit and ChargedUnit are wrongly calculated in TAP out file Generation

Details :

* In Outcollect TAP file Generation, the generated TAP file contains wrong values in the below fields if the field value exceeds a certain limit:
   DataVolumeIncoming,
   DataVolumeOutcoming,
   ChargeableUnit and
   ChargedUnit

   For example, if in the input CDR, the following values are given in the respective fileds :
        VolumeIncoming = 2773519240
        VolumeOutgoing = 275464716
   But in the generated TAP file it is coming as:
        DataVolumeIncoming = 0
        VolumeOutgoing = 275464716
        ChargableUnit = 0
        ChargedUnit = 1000000512

* In the Pipeline, ROUNDED_QUANTITY_VALUE is SET after crossing the FCT_MainRating function Module.

* ROUNDED_QUANTITY_VALUE field is accepting a maximum value of "1000000512" only.

* If the Sum of VOLUME_SENT and VOLUME_RECEIVED exceeds the Value of "1000000512", the value of 1000000512 is assigned to the ROUNDED_QUANTITY_VALUE in the FCT_MainRating function Module which results in wrong TAP field value of ChargedUnit.

   For example, if VOLUME_SENT is 275464716 and VOLUME_RECEIVED is 2773519240, the ROUNDED_QUANTITY_VALUE is calculated as 1000000512 instead of 3048983956.


Question :

What is the reason for this behavior and how to resolve it?
 

Solution

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