EAR 9.2: Payment Predictor Books New On Account Item to Incorrect Customer ID if Customer Hierarchy Is Enabled
(Doc ID 2799570.1)
Last updated on AUGUST 16, 2021
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A problem has been detected with the Payment Predictor functionality when the action of 'Generate An Item' is selected for a Payment that has no Invoices/Items to get balanced with, and only provides a Customer ID value. While the system properly creates a new On Account Item, the Customer ID value used is not the one provided/defined at the Payment level, (Under Record Field PS_PAYMENT_ID_CUST.CUST_ID), but instead, it uses the maximum Customer ID value from Temporary Table PS_PP_CUST_TAO due to incorrect coding on the below Application Designer object:
- Application Engine Program, Section, Step, and SQL: AR_PREDICT2.GEN_ONE.ONEITEM8
While the generated Payment Worksheet suggests that the new On Account Item has been associated to the expected Customer ID value, the resulting Payment Group stores the incorrect one, (Record Field PS_PENDING_ITEM.CUST_ID).
This happens when there is a Corporate Customer with multiple Customer IDs reporting to it. The system picks up the Customer ID with the maximum value from the Temporary Table, instead of the one from the Payment transaction settings.
1.- Log into the FSCM Online Application as a Receivables User
2.- Define a new Payment Predictor Method that has a Step where the Action is to 'Generate An Item' (System Function WS-05) if no Items exist to balance the payment received
3.- At the Receivables Options level, in the Payment Options tab, define the newly created Payment Predictor Method
4.- Create 3 new Customers into the system as follows:
a) Customer ID ABC0001, which will be defined as a Corporate Customer
b) Customer ID EDF0001, which will report to Corporate Customer ID ABC0001
c) Customer ID XYZ0001, which will report to Corporate Customer ID ABC0001
5.- Create a Pending Group for the Customer ID XYZ0001, Business Unit US001, and define one Item for an amount of 250 USD. Continue by setting it to Post Action Batch Standard
6.- Run AR Update for the Business Unit value used, and Pending Items flag selected
7.- Ensure that the Item has been posted against the Customer ID XYZ0001 Account
8.- View the Customer Hierarchy for Customer ID ABC0001, and confirm that it lists underneath it the two Customer IDs DEF0001 and XYZ0001. Customer ID XYZ0001 has a Balance of 250 USD, while main Corporate Customer ID ABC001 has a Rollup Balance of 250 USD as well.
9.- Create a new Regular Deposit, under Deposit Unit US001, with one Payment for an amount of 1,500 USD, select the Payment Predictor flag, and in the Customer Information section, define Customer ID DEF0001, and Business Unit US001
10.- Launch the Payment Predictor process for the Business Unit at hand (US001)
11.- Confirm that the process completed successfully, and when checking the Message Log of the APR_PP1 AE Program, note that the system has created a Payment Worksheet, and it is ready for posting
12.- Open the Payment Worksheet, and confirm that in the Item List section, the Customer ID is DEF0001 and Business Unit is US001, as well as Post Action is set to Batch Standard
13.- Launch AR Update for Payment transactions, and Business Unit US001
14.- Review the Balance from Customer ID DEF0001, but no On Account new Item has been created at all
15.- ISSUE: Confirm that the new On Account Item has been wrongly added to the Balance of Customer ID XYZ0001 instead
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
Once AR Update has processed the Payment Group coming from the Payment Predictor generated Worksheet, the On Account Item has been booked against the Account of the incorrect/unexpected Customer ID. This causes problems when trying to match Invoices/Items from the expected Customer against the credit Item, or through Aging Reports. Manual tasks are needed to transfer the Invoice/Item from one Customer to another just to fix the problem.
The Payment Predictor should correctly associate the new On Account Item to the Customer ID the Payment has been entered for, and ensure that the resulting Payment Group is properly kept in-sync with this logic, so that AR Update posts the new Credit On Account Item into the desired Customer's Balance.
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