My Oracle Support Banner

EAP: Match Exception Data On The AP_MTCH_EXCPTN Table Is Not Deleted For The Deleted / Recycled / Closed Vouchers That Are In Match Exception. (Doc ID 3036948.1)

Last updated on JULY 25, 2024

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Match exception data on the AP_MTCH_EXCPTN table is not deleted for the deleted / recycled / closed vouchers that are in match exception.

The issue can be reproduced at will with the following steps:

1. Create a purchase order (Purchasing - Purchase Orders - Add / Update Purchase Orders).
2. Create a voucher for that purchase order such that it triggers a match exception. (Accounts Payable - Vouchers - Add / Update - Regular Entry).
3. Run matching (Accounts Payable - Batch Processes - Vouchers - Matching).
4. Verify the match exception collaboration tile (Home - Payables Operations - Match Exceptions) to make sure that the voucher exists.
5. Delete the voucher (Accounts Payable - Vouchers - Add / Update - Delete Voucher).
6. Verify the match exception collaboration tile (Home - Payables Operations - Match Exceptions) and still the voucher exists.

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.