My Oracle Support Banner

DiscrepancyPurge Batch Not Updating QTY_MATCHED and INVC_MATCH_STATUS in SHIPSKU Table (Doc ID 2537289.1)

Last updated on DECEMBER 05, 2019

Applies to:

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

Symptoms

Discrepancypurgebatch was removing the discrepancy for matched item but QTY_MATCHED and INVC_MATCH_STATUS columns in SHIPSKU table were not updated accordingly.

This is applicable for both fully matched and partially matched invoices.

Steps to Recreate:

      Scenario1: Partially Matched

  1. Create a Purchase Order (PO) for 2 items. Do not receive the PO.
  2. Create an invoice with quantity discrepancy overcharge for one item.
  3. Execute automatch batch and notice that quantity discrepancy was generated for both items.
  4. Receive the PO fully.
  5. Execute discrepancypurge batch.
  6. Notice that status of matched item in the invoice was changed to MTCH. But, QTY_MATCHED and INVC_MATCH_STATUS columns in SHIPSKU table wer not updated accordingly.

      Scenario2: Fully Matched

  1. Create a Purchase Order (PO) for 2 items. Do not receive the PO.
  2. Create an invoice which is exact match to PO.
  3. Execute automatch batch and notice that quantity discrepancy was generated for both items.
  4. Receive the PO fully.
  5. Execute discrepancypurge batch.
  6. Notice that the invoice and receipt status was updated to matched. But, QTY_MATCHED and INVC_MATCH_STATUS columns in SHIPSKU table wer not updated accordingly.

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