My Oracle Support Banner

EAP: Voucher Released From Payment Hold Is Populating the Payment Schedule Due Date With the Current Date Instead of Calculating Based On the Payment Terms (Doc ID 3047972.1)

Last updated on SEPTEMBER 20, 2024

Applies to:

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

Symptoms

Vouchers are loaded directly to the Voucher STG records where the Hold Payment flag =Y. Since the payment is on hold, the Scheduled Due date is not calculated for these vouchers after Voucher Build completes. However, these vouchers are Voucher Posted successfully.

Once the business unchecks the Payment Hold flag on the Voucher, the Scheduled Due date defaults to the current date instead of calculating based on the Payment Terms.


STEPS TO REPLICATE
-----------------------------
1. Load voucher data directly to the VCHR_HDR_STG, VCHR_LNE_STG, PS_VCHR_PYMT_STG

2. Populate PS_VCHR_PYMT_STG with the following values:
    a. PYMNT_HOLD = 'Y'
    b. PYMNT_HOLD_REASON = 'OTH'

3. Do not populate data in PS_VCHR_DIST_STG

4. Run Voucher Build: Accounts Payable > Batch Processes > Vouchers > Voucher Build

5. Take the voucher off of Payment Hold: Accounts Payable > Vouchers > Add/Update > Regular Entry > Payments tab
    a. Uncheck box for Hold Payment
    b. Remove Hold Reason value
    c. Save

6. Payment Scheduled Due date populates with the current date instead of calculating based on the Payment Terms

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


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