My Oracle Support Banner

Quantity Discrepancy Not Removed After Shipment is Fully Received (Doc ID 2352224.1)

Last updated on MARCH 01, 2019

Applies to:

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

Symptoms

Quantity Discrepancy not removed after shipment is fully received.After discrepancypurge batch was run the discrepancy still exists on the IM_QTY_DISCREPANCY table and invoice not moved MTCH status.

Steps to Recreate:

  1. Create an Item.
  2. Create a purchase order.
  3. Create an invoice which is the exact match to the PO.
  4. Make sure that “Discrepancy Routing Days” specified in Supplier Options are past vdate.
  5. Run Automatch batch.
  6. Notice that a quantity discrepancy was generated on the IM_QTY_DISCREPANCY table.
  7. Receive the PO fully.
  8. Run discrepancypurge batch and notice that quantity discrepancy was not removed from IM_QTY_DISCREPANCY table.
  9. Notice that the invoice is still in URMTCH status.

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.