My Oracle Support Banner

EAP: SPSMISC SUPPLIER OFFSET TOP INCORRECT AFTER PAYMENT CANCEL (Doc ID 2854388.1)

Last updated on MARCH 09, 2022

Applies to:

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

Symptoms



ISSUE:

When a payment that uses SPSMISC EFT layout is cancelled, the process creates a new PYMNT_VCHR_XREF record for the new payment but it does not create the related PYMNT_VCHR_XSIB record.

STEPS:

1. Create new bank account SPSM under FDBNK that uses SPSMISC layout

  Banking > Bank Accounts > External Accounts 
2. Add PYMNT_VCHR_XSIB to query security
3. Update supplier 0000000050, Add loc 2 to have banking information, Supplier Offset TOP = N

Suppliers > Supplier Information > Add/Update Supplier


4. Create voucher to business unit FED01
- Use supplier 0000000050, location 2
- Use SPSM bank account
- Set Supplier Offset TOP to Y

Accounts Payable > Vouchers Add/Update Regular Entry

 

5. Budget check voucher
6. Create pay cycle and run through to create SPS file

Accounts Payable > Payments > Paycycle Processing > Pay Selection Criteria


7. Open SPSMISC file and confirm TOP is Y (POSITION 855)
8. Cancel payment

Accounts Payable > Payments > Cancel/Void Payments > Payment Cancellation


9. ERROR: Re-open voucher - new payment TOP is N (this should be set to same value as first payment)
10. ERROR: Query PYMNT_VCHR_XSIB and no row for payment 2
11. Re-run paycycle through to create SPS file
12. ERROR: open file and confirm TOP is Y even though page shows TOP N



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


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