My Oracle Support Banner

EAR 9.2: Payment Predictor With Algorithm #DTL_TLR And Underpayment Within Tolerance Using System Function WS-09 (Write Off - WO) Not Generating Balanced Worksheet For VAT And Non-VAT Business Units (Doc ID 2441829.1)

Last updated on OCTOBER 01, 2020

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

Having defined a Payment Predictor Method that is using delivered Algorithm #DTL_TLR, and configured at the Predictor Detail Options level the Amount and Percentage Tolerances to be used, and what functions to execute in each scenario, (For an Underpayment within Tolerance it should use System Function WS-09, Write-Off), when running the Payment Predictor AE Program (AR_PREDICT1), the results obtained are not the expected ones.

While the system generates a new Payment Worksheet, this one is unbalanced, because the remaining amount is not being automatically written off even though it falls within the defined tolerances.

System Function WS-09 (Write-Off) is the one to be used for both VAT and non-VAT Business Units.

REPLICATION STEPS:

    1.- Define a Payment Predictor Method using Algorithm #DTL_TLR
    2.- Configure this Payment Predictor Method at the Business Unit, and Customer set up level
    3.- At the Predictor Detail Options tab from the Receivables Options level, define Write Off Tolerances of 5 USD, and 100% of the amount, as well as state that if there is an underpayment within such Tolerance, it should be Written Off (System Function WS-09)
    4.- Create an online Pending Item for an amount of 1200 USD, and set the Group to Post Action of Batch Standard
    5.- Launch AR Update to post the new Item into the Customer's Account
    6.- Follow suite with the creation of a new Regular Deposit, with a Payment of 1199 USD, and link the Item ID created in the Detail References. Flag such Payment for Payment Predictor
    7.- Run Payment Predictor AE Program
    9.- The process should go to Success
    10.- Check the generated Payment Worksheet, and confirm it is unbalanced for a remaining amount of 1 USD

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ACTUAL RESULTS:

Payment Predictor generates unbalanced Payment Worksheets, and this forces the User's manual intervention in reviewing the transactions, create the necessary Write Off Item row, and place the Group into Post Action of Batch Standard. These are lots of steps that delay the processing of outstanding transactions.

EXPECTED BEHAVIOR:

The Payment Predictor AE Program (AR_PREDICT1) should identify if the Payment being matched to the existing outstanding Item falls within the defined Tolerances, and if so, automatically generate the write off, balancing the Worksheet, and placing it into Batch Standard.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References

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