My Oracle Support Banner

E1: 43: VMA Produces Different Results In Final Mode (Match Not Found) Vs Proof Mode (Match Successful) (Doc ID 2547743.1)

Last updated on MAY 28, 2019

Applies to:

JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Voucher Match Automation UBE for Automation Rule 06 (R4304021)

The “Proof Mode” version of Voucher Match Automation UBE for Automation Rule 06 (R4304021) does not reject duplicate invoice numbers while the “Final Mode” version does.

This creates confusion during integration testing, because errors are going undetected and not discovered until the final mode version is run.

Steps to Duplicate

  1. In Accounts Payable Constants, the Duplicate Invoice Number Edit field is set to “H” (Hard error upon duplication)
  2. Create a VMA Supplier with USD Currency (86259) and set Purchasing 2 Tab with the following settings:
    1. Automation Rule = 06
    2. Partial Receipt Allowed = Checked
    3. Single Voucher Per Invoice = Unchecked (Single Voucher Per Invoice Line)
  3. Create a three-line purchase order for the VMA Supplier
  4. Receive the purchase order in full
  5. Use A/P Batch Voucher Entry (P0411Z1 version ZJDE0003) to add a Record in Batch Voucher Entry (P0411Z1). Use one Invoice Number for all three lines.
  6. Voucher Match Automation Driver program (R4304010) calls VMA Rule 06 Processor Proof Mode Version (R4304021 Version XJDE0001).
  7. Process Tab Option #1 is set to Blank (Single Voucher Per Invoice Line)
  8. VMA Rule 06 Processor (R4304021 Version XJDE0001) is set to Proof Mode
  9. Run Voucher Match Automation Driver program (R4304010) in Proof Mode. All three lines show Match Successful. There are three vouchers with one invoice. These should have been rejected.
  10. Change Voucher Match Automation Driver program (R4304010) to calls VMA Rule 06 Processor Final Mode Version (R4304021 Version XJDE0002).
  11. Run Voucher Match Automation Driver program (R4304010) in Final Mode. The first line was matched, but the second and third line were rejected as duplicates.

“Proof Mode” should not accept one invoice number for multiple invoice lines. It should work the same as “Final Mode”.

Changes

 

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
Changes
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.