Discrepancy Purge Batch Incorrectly Matches the Shipment and Shipsku Data

(Doc ID 2077670.1)

Last updated on MARCH 25, 2016

Applies to:

Oracle Retail Invoice Matching - Version 13.2 to 13.2.8 [Release 13.2]
Information in this document applies to any platform.

Symptoms

 

The Discrepancy Purge batch incorrectly updates the INVC_MATCH_STATUS = 'M' of the SHIPMENT table and the SHIPSKU table's QTY_MATCHED field.


Steps to Reproduce:

  1. Create 3 new items with a cost of $7.50 each.
  2. Create a new order with 100 qty of each item.
  3. Ship only quantity of 80 for each item.
  4. Receive the shipped quantities.
  5. Create a new invoice for a quantity of 70 of each item.
  6. Match the invoice by using Summary Match screen; click on Details after selecting the invoice and receipt.
  7. Bring the first item down.
  8. Select the receipt and click on split receipt.
  9. Click on detail match afterwards to match at the item level.
  10. Repeat for the remaining 2 items.  Invoice is now in matched status.
  11. Review the shipment.
  12. Create a new invoice for the same PO.
  13. Execute the Auto Match batch.  Invoice goes to unresolved match.
  14. Create one more Shipment and receive it.
  15. Execute the discrepancy purge job.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms