My Oracle Support Banner

Automatch Batch (line Level) Updates Qty_matched In Shipsku Table Incorrectly (Doc ID 2829824.1)

Last updated on DECEMBER 22, 2021

Applies to:

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


On : 14.1.3 version, Batches

  You observe that SHIPMENT.INVC_MATCH_STATUS is updated to Y when the invoice is still discrepant

The issue can be reproduced at will with the following steps:
1. Create a PO for 3 items, and receive it completely.
  sku 1 = $10, 1 unit
  sku 2 = $10, 1 unit
  sku 3 = $10, 1 unit
2. Create an invoice in ReIM for this PO with cost discrepancy on two of the items.
  sku 1 = $30, 1 unit
  sku 2 = $10, 1 unit
  sku 3 = $20, 1 unit
3. Run automatch batch so that it attempts line-level match.
4. The QTY_MATCHED flag in im_invoice_detail table is updated to Y for all the line items as expected.
5. The COST_MATCHED flag in im_invoice_detail table is updated to Y for sku2 as expected.
6. The QTY_MATCHED in shipsku table for all items is updated to 1 which is not expected.
7. Search for the PO in Summary Match Find screen
8. Resolve the cost discrepancy of sku1 using a Debit Memo Quantity.
9. Notice that the INVC_MATCH_STATUS of shipment is updated to M which is not expected as sku3 is still not matched.




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.