EAP: Why does Matching generate Match Exception of RULE_R600 when run for multiple Vouchers for the same PO?
(Doc ID 1500416.1)
Last updated on FEBRUARY 06, 2019
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
Why does Matching generate Match Exception of RULE_R600 when it is run for multiple Vouchers for the same PO at the same time?
1. Create a PO for quantity = 5
2. Create a Receipt for quantity = 1
3. Create 3 Vouchers using 'Purchase Order Only' Copy From option for Quantity = 1 for each Voucher
4. Run Matching process for ALL 3 vouchers at the same time
First Voucher is associated to the Receipt and is Matched.
Second and Third Vouchers have a Match Exception as expected BUT for RULE_R600 instead of of RULE_R500.
NOTE: When Matching is run on each of these Vouchers SEPARATELY, Matching generates a Match Exception of RULE_R500 for the second and third Vouchers.
RULE_R500: No receipts found
The Matching process could not find any receipts for the purchase order specified on the voucher line that were available for matching (for example not matched, not on hold, and not canceled).
RULE_R600: No receipt found, but unmatched ones exist
The Matching process found receipts for this purchase order that were available for matching (for example not matched, not on hold, and not cancelled) but could not make an association to the voucher line using any of the receipt aware criteria.
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