AP Match Rules R500 And R950 Are Not Mutually Exclusive Causing Needless R950 Match Exceptions.

(Doc ID 2412641.1)

Last updated on JUNE 19, 2018

Applies to:

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

Symptoms

On : 9.2 version, Voucher Processing

Match Rules RULE_R500 and RULE_R950 are not mutually exclusive.  This causes needless R950 exceptions. Currently RULE_R950 will always occur when no receipts exists (RULE_R500).   This causes the AP Matching process to needlessly generate the RULE_R950 Match Exception error. This forces a team of AP users to investigate many hundreds of Vouchers per month to see if the R950s are true errors.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create PO.

2. Ensure that Receipt is required.

3. Do not create receipt to force RULE_R500 exception.

4.  Set PO using Standard Match Rule Control.
     Note that Standard Match Rule Control uses RULE_R500 and RULE_R950

5. Create regular voucher using the PO.

6. Run Matching.
    Match exceptions encountered: RULE_R500 and RULE_R950.



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms