My Oracle Support Banner

EAP 9.2: Match Exception Status Incorrectly Remains as 'Unassigned' and Does Not Update to 'Open' on Match Exception Collaboration Center After Running the Matching Process (Doc ID 2894578.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

Match Exception status on Match Exception Collaboration Center is not updated correctly after running the Matching process.

Steps:
1) Ensure that User does not have ‘Work All Exceptions Authority’ checked on User Preferences for Match Exception Collaboration Center (MECC)
2) Ensure that Match Exception, say RULE_V200,is not assigned to any existing Match Exception Group.
3) Ensure that there are vouchers with match exception RULE_V200 listed on MECC for the user, with Unassigned status.
4) Create a new Match Exception Group for RULE_V200 and associated a Role to it. The Role is associated with the user.
5) Run Matching process.
6) Review the Match Exception RULE_V200 on the MECC.
7) Click on the Prompt of the 'Assigned to'.

Expected result:
After step 6 - status should be Open.
After step 7 - The list of users that are available to choose from appears to be ALL users

Actual result:
After step 6 - The status is (Invalid Value).
After step 7 - The list of users that are available should be within the Match Exception Group for the Rule.

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.