EAR 9.2: Payment Worksheet Selection - Reference Criteria Being Set To 'Detailed References' Instead Of 'Specific Value', Which Triggers Error Message (6040,599) For Lockbox Payments When Building New Worksheet
(Doc ID 2548291.1)
Last updated on NOVEMBER 13, 2023
Applies to:
PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
ISSUE:
The functional team has detected a system inconsistency when trying to build a new Payment Worksheet for a Deposit/Payment loaded via Lockbox interface. At the Payment Worksheet Selection page, the Reference Criteria section has by default the below setting:
- Reference Criteria = Detailed References
Before the system's upgrade from FSCM 9.2 Image #24, to Image #30, this very same setting was always defaulting to a value of: Specific Value. Taking into consideration this difference, when the User tries to build the Payment Worksheet, the system triggers Error Message (6040,599), something it did not use to do before the upgrade.
REPLICATION STEPS:
1.- Upload a Lockbox electronic file with the information of a Regular Deposit, and a Payment, containing information of the Item/Invoice to be paid
2.- Run the Payment Loader process to generate the Regular Deposit, and its Payment transaction
3.- Go to create a new Payment Worksheet for this Deposit, and Payment combination
4.- Confirm that at the Payment Worksheet Selection page, at the Reference Criteria section, the field 'Reference Criteria' has a default value of 'Detailed References'
5.- Click on the BUILD button
6.- The system triggers an Error Message
ERROR MESSAGE:
Users are not sure as to why this Error Message is popping up, and it creates confusion. The Detailed References need to be manually reloaded again, or the Reference Criteria field needs to be set to 'Specific Value' manually. This means further steps, delaying the entire process.
Upon creating the new Payment Worksheet, the Reference Criteria drop down list should have by default a value of 'Specific Values' just as it used to have back prior to the FSCM 9.2 Image #30 system's upgrade.
Changes
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 |
Changes |
Cause |
Solution |
References |