EAR: Payment Predictor Not Releasing Payment For Next Step Processing, If Next Step Uses Same Algorithm
(Doc ID 2619305.1)
Last updated on DECEMBER 11, 2019
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Payment Predictor process does not seem to properly release selected Payments at the end of one particular step, so that the next Step from the Method defined can continue working on it.
In the Payment Predictor Method, the system will be using delivered Algorithm #REFS, and Item Reference will be provided at the Payment level. Note though that the desired outcome is:
1) First, the system should use #REFS to perform the potential matches
2) If there is an underpayment of less than 10.00 USD, then the remaining amount should be written off
3) If the underpayment however falls between 10.00 USD and 25.00 USD, then the system should adjust an underpayment instead
1.- Define a new Payment Predictor Method, with two Steps using Algorithm #REFS in the following way:
a) Step #1, Condition #1: Execute Algorithm #REFS
b) Step #1, Condition #6: Release the Payment if an underpayment exceeds 9.99 USD
c) Step #1, Condition #7: Write off the underpayment, if this one is less than 10.00 USD
a) Step #2, Condition #1: Execute Algorithm #REFS
b) Step #2, Condition #7: Adjust remaining underpayment, if this one is less than 25.00 USD
2.- Define the Payment Predictor Method at the Business Unit level, as well as at the Customer's Bill To Options level
3.- Create a new Pending Item Group for Customer ID 1000, with one Item for 500.00 USD
4.- Set the Pending Item Group into a Post Action of Batch Standard
5.- Launch AR Update to process Pending Items
6.- Create a new Regular Deposit, with one Payment for 480.00 USD, for the Customer ID 1000, Business Unit, and Item ID reference previously posted. Ensure that the Payment Predictor flag is selected, and save the changes.
7.- Launch Payment Predictor process
8.- Confirm that no Payment Worksheet has been created for the Payment and Item in question, even though all 2 Steps, and total of 5 conditions/actions were executed
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.
Payment transactions are not being automatically applied by Payment Predictor process, which leaves it to Users to have to manually build Payment Worksheets, and perform all the tasks to achieve the desired results. This is not efficient, nor user friendly, at the same time that could leave Payments without processing if Users forget to query them.
In this case, the Payment Amount of 480.00 USD is less than the 500.00 USD amount of the Item, therefore, there is an underpayment of 20.00 USD. With that in mind, Payment Predictor Step #1 should activate Condition #6, confirming than 20.00 USD is greater than the maximum of 9.99 USD to write off, and hence, release the payment. Then, on Step #2, the Payment should be picked up again for processing, and on Condition #7, identify that the underpayment is less than 25.00 USD, and as such, should create a new Payment Worksheet for an adjust underpayment, and set it ready for review.
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