Customer Balance Wrongly Impacted by Rounding Issues During Stop Accounting Call (Doc ID 1949425.1)

Last updated on AUGUST 26, 2024

Applies to:

Symptoms

On : BRM 7.4.0.20.0 version

Scenario:

* An account is having a free resource balance (say, ID 1000779) which is worth 60$ for example.
* Stop accounting call cost is 162 $ for a requested quantity of 200.
* The discount is configured to consume the free resource if available for the customer balance.

Actual result:

* Due to some rounding issues, customer's free resource balance bucket has been charged with 61 $ ( which is more than the available balance ) and then the remaining cost.

Expected result:

* Customer's free resource balance bucket should be charged with 60 $ and then the remaining cost.

Observations:

*  The rounding configuration of the resource 1000779:

During authorization, below flow was observed:

1. Available free resource ( 60 $ ) is not sufficient for the current call charge ( 162 $ )
2. To find the actual amount to be reserved, FCT_CreditLimitCheck is doing a reverse rating and calculated the amount eligible as ‘59.999999994’
3. So the final amount reserved from free resource is 60 $ as expected.
4. Now, during stop accounting call, as per the discount configuration, the complete available resources should be consumed first:
      --  Pipeline calculates the Discount Match factor as below
      --  Match_Factor = Available free resource / Total charge, which is 60/162, which is actually 0.3703703703703704.
5. Due to rounding, the actual match factor is calculated as ‘0.370370370371’
6. So, the calculated charge is 162*0.370370370371, which is 60.000000000102.
7. As the 1000779 resource rounding mode is configured PIN_BEID_ROUND_UP, the final amount is getting charged as ‘61’ Franks which is more than the available balance.

Changes

Cause

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