EAP WTHD: Incorrect Payment ID (PYMNT_ID) On 1099 WTHD_TRXN_TBL After Override And Manual Adjustment
(Doc ID 2877630.1)
Last updated on FEBRUARY 21, 2023
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.
Incorrect Payment ID (PYMNT_ID) on 1099 WTHD_TRXN_TBL after Override and Manual Adjustment.
An incorrect PYMNT_ID is being saved to a manual 1099 adjustment transaction (legacy transaction) after an override change is made to a transaction with an associated payment. When an override is made, it resets the process instance of that transaction back to zero (0) and then when a manual adjustment is made after that, instead of setting the payment id of the manual adjustment to a value that ends in ".00", it sets it to the PYMNT_ID of the override transaction plus a value of 1.
1. Enter a voucher for a 1099 Vendor.
2. Pay and then post both the voucher (accrual) and the payment.
3. Run the 1099 posting process.
4. Query the WTHD_TRXN_TBL and make sure the transaction is there, and has a process instance number.
5. On the 1099 adjustments page, add a manual adjustment of say $-10.
6. Add another adjustment for say $-20.
7. Query the WTHD_TRXN_TBL again, this time the 2 adjustments should have payment IDs of 1.00 and 2.00.
8. Change the declaration date of the original 1099 transaction created in Step 1.
9. Query the WTHD_TRXN_TBL again, this time the process instance for the newly "overridden" transaction is set back to 0 (zero).
10. Enter a 3rd manual adjustment for say $-30.
11. Query the WTHD_TRXN_TBL one last time. Notice that they payment ID of the 3rd manual adjustment is incorrect. Instead of being 3.00 it is the payment ID of the original transaction plus 1.
- Due to this issue, if you are just querying the table it does not look right to show a PYMNT_ID associated with a transaction that isn’t even related to the Vendor.
- If the PAYMENT_TBL is queried for the new legacy row’s PYMNT_ID, it will be seen that the PYMNT_ID is associated with a totally different Vendor. This causes some confusion.
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