23A Comission Amount Not Expected Due to Credit Amount Rounding (Doc ID 2937631.1)

Last updated on APRIL 21, 2023

Applies to:

Symptoms

The Commission amount is not what is expected after 23A update.  The formula is rounding the credit amount before calculating the results.

STEPS

1. Import transaction with transaction amount with value beyond 2 decimal place ( eg. 0.928839865 )
2. Submit Run All Transaction Processes jobset
3. Compensation Plan has incentive or measure formula that uses the Credit Amount field
    (eg. Rate Table Rate * Credit Amount * Measure result.PM2.PTD Output )
4. Review Commission and see credit amount was rounded
    Example :
         Rate Table Rate  X  Credit Amount   X   PM2.PTD Output = Commission
                  25%              0.928839865           50,000               11610.4983125
                                      --- versus ---
                  25%              0.93                       50,000               11625.00

User is getting commission as $11625.00 and expecting $11610.4983125

Changes

In the past, the Manage Credit UI would not let you enter transactions with more than the decimal places setup for the corresponding currency but the Import Transactions process would allow it. This led to some confusion.

In 23A Update, we moved to align the two experiences and added checking to prevent the import of a credit amount greater than the decimal places setup for the corresponding currency (eg. USD transactions will round to 2 decimal place ) . To clarify, this only is applicable to the transaction and credit amount. Numeric values for descriptive flexfield attributes are not rounded.

Cause

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