My Oracle Support Banner

EAP: MATCHING Master Resolution for Working as Designed Issues and Scenarios (Doc ID 948103.1)

Last updated on DECEMBER 13, 2019

Applies to:

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

Purpose

The purpose of this knowledge document is to act as a repository for Matching regarding Working as Designed Issues and Scenarios.

Questions and Answers

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
Purpose
Questions and Answers
 Match Rule 550, Line qty not = PO line qty with PO received % tol, is not working as expected.
 Matching is executing RULE_E200, Extended Price % Tolerance, error incorrectly.
 Matching is triggering a Match Exception RULE_V300, Life to Date Voucher Amount > PO Amount, when there is a Change Order for a Unit Price on the PO.
 Receiving RULE_E200, Extended Price % Tolerance, Matching Exception for Amount Only PO
 Why is Match Exception RULE_E100 generated when Quantity is over but not when it is under?
 Unable to correct Match Exception RULE_S210, Invalid PO Status, for an Adjustment Voucher tied to a closed PO.
 Match Exception for RULE_R950, Voucher quantity does not equal sum of receipt qty, received in error.
 How do you setup the configuration for tolerance levels in relation to the Matching process for RULE_E100, Extended Price Tolerance?
 Rule E100, Extended Price Tolerance, is not working as expected
 Why is the message: "This voucher is currently in use by a Payables batch process. (7030,236)" received when running On-Demand Matching?
 Why is Matching generating a RULE_R650 Match Exception for Vouchers created from Receipts associated to 'Amount Only' POs?
 Deleted Vouchers are still in the PS_AP_VCHR_LN_SUM and PS_VCHR_HDR_SUM Records
 Is there a way to configure which attributes are displayed on the Associated Document Information - Match Object Details?
 Amount only PO should be partially Matched to a Voucher but it's showing as fully Matched
 Lost functionality using Match Workbench when Match Status Required.
 Unable to Override the System Match Exception Rules in the Match Exception Override page because the button is grayed out.
 Match Exception not received when two Vouchers are Matched to the same Receipt
 Unable to Unmatch a Voucher that is tied to a Closed PO
 There appears to be no way to tie a regular Voucher to a PO once the Voucher is created. Can an Adjustment Voucher or Unposting it work?
 In Release 8.9 and later, where is the direct link to the Match Workbench from the Voucher pages?
 When you run the Two-Way Match process for Vouchers and PO's, does the process automatically close the PO in the Purchasing system or do you still have to Manually Close it?
 If a Voucher is matched but has not been Posted or Paid, why can't is be selected to Unmatch?
 In release 8.9, what Record(s) replace the VCHR_MTCH_EXCPT record from release 8.4?
 There is no DMS script available to move AP Match Rules from one environment to another
 What do some of the fields from the AP_VCHR_LN_SUM mean with description?
 What is the meaning of the data in the VCHR_RECV_MTCH, RECV_VCHR_MTCH and VCHR_MTCH_DETLS tables?  What is the context of that data?   When is the data populated?
 Users are not given access to the Action field and Run button on the Match Workbench page.
 If a Voucher has Match Exceptions, it is possible to mark that Voucher's Match Action Status to No Match on the Voucher Attributes page?

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