My Oracle Support Banner

Automatch Updates the DETAIL_MATCHED Value to 'Y' and Creates Invalid Discrepancies (Doc ID 2132919.1)

Last updated on NOVEMBER 23, 2019

Applies to:

Oracle Retail Invoice Matching - Version 12.0.12 and later
Information in this document applies to any platform.


The Automatch batch is updating the DETAIL_MATCHED flag to 'Y' and creating quantity discrepancies for invoices that have NOT met the routing days configuration for discrepancy routing.

Steps to Reproduce:

  1. Create one order with 3 items.  (Example: Item1 - 280 Units; Item2 - 8000 Units; Item3 - 80 Units)
  2. Create 2 different invoices for two of the items. (Inv1: Item2 - 3900 Units; Inv2: Item3 - 80 Units)
  3. Receive one item. (Item2 - 2900, which is 1000 less then the invoice)  This will create one shipment record in Retail Merchandising System (RMS) for only one item.
  4. Run the Automatch batch.
  5. Actual result:  The invoices are moved to 'URMTCH' and DETAIL_MATCHED is updated to 'Y'. Quantity discrepancies are created.  Because of this, when the receipt happens for the other items, Automatch does not pick up the invoices for matching. It is expected that ReIM should wait the routing days for the invoices to create discrepancies.



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

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