ReIM Discrepancy Purge Batch Purges Valid Cost Discrepancy (Doc ID 2061616.1)

Last updated on OCTOBER 02, 2015

Applies to:

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


The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

The reim discrepancy purge batch is purging a valid cost discrepancy due to which the invoice moves from URMTCH status to MTCH status.Leading to incorrect document matching.

Steps to replicate:
1)Consider item for which an order should be present with the unit cost of X, this order should be shipped and received. This order can be found in v_im_ordloc
2)Perform a Unit Cost change for this item. Old Cost is X and Changed Cost Y
3)Now the unit cost of item is Y
4)Create a order, ship and receive it fully.
5)Create an invoice for this item with cost discrepancy. The invoice cost should be X.
6)Run automatch. Invoice goes to URMTCH and a cost discrepancy is created.
7)Now run the reimdiscrepancy purge batch as ./reimdiscrepancypurge (BATCH ALIAS) PURGE ALL COMMIT
8)The cost discrepancy is getting purged and the invoice moves to MTCH status, instead of having a valid cost discrepancy


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