My Oracle Support Banner

EAP 9.2: Match Exception Status Remains Resolved Incorrectly For Voucher In Match Exception (Doc ID 2894555.1)

Last updated on SEPTEMBER 12, 2022

Applies to:

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

Symptoms

When using the Match Exception Collaboration Center, user's have the option to update the status of match exceptions to 'Resolved'. Once in a 'Resolved' status the match exception no longer displays in the MECC for average users.
Once the match exception was in a resolved status. Ran the voucher through matching again, the exception still showed on the voucher but was not showing in the MECC.

Steps:
1) User has only 'Enable Group/Users Assigned' on Exception Collaboration Authority.
    Set Up Financials/Supply Chain > Common Definition > User Preferences > Define User Preferences
2) User opens Match Exception and marks it Resolved.
    Procurement Operation > Match Exceptions
3) Run matching for the Voucher which had the match exception.
     Accounts Payable > Batch Processes > Vouchers Matching
4) Voucher remains in Exception status.

Actual result:
Match Exception remains in Resolved status.

Expected result:
There should be a way to prevent the Match Exception to marked as Resolved by user incorrectly.

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
References


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