ReIM: When Running Discrepancypurge Batch 'qty_matched' is Not Filled
(Doc ID 2524960.1)
Last updated on JULY 30, 2019
Applies to:Oracle Retail Invoice Matching - Version 14.0 and later
Information in this document applies to any platform.
In Oracle Retail Invoice Matching (ReIM) 14.0, when receiving a partial order and running the discrepancypurge batch, the qty_matched in the shipsku table is not being filled, however it works fine when an order is received completely.
Steps to Reproduce
1: (@RMS Ordering -> Orders) Create, submit and approve a Purchase Order containing 2 items.
2: (@RMS Inventory -> Shipping -> Order Shipments) Ship one item fully.
--> In the database (DB) we can verify that we are expecting 100 units, but none have been received nor matched, as expected.
3: (@RMS Inventory -> Receiving -> Item Receiving) Receive the item fully.
Note the DB update on the qty_received column:
4: (@ReIM Document Maintenance -> Document Search -> New) Create an invoice with detail for the full purchase order.
5: Execute the reimdiscrepancypurge batch.
6: Execute the reimautomatch batch.
--> Note the DB update on the im_invoice_detail:
--> Now, as expected, one of the items is MTCH while the other is still UNMTCH.
--> Meanwhile, qty_matched column in shipsku is still NULL:
7: Execute the reimrollup batch.
8: Execute the reimposting batch
9: (@RMS Inventory -> Shipping -> Order Shipments) Ship the remaining item, fully.
10: (@RMS Inventory -> Receiving -> Item Receiving)
Receive the remaining item, fully.
11: Execute the reimdiscrepancypurge batch.
12: Execute the reimautomatch batch.
13: Execute the reimrollup batch.
14: Execute the reimposting batch.
Actual result: The invoice is POSTED, but qty_matched (shipsku) is still NULL, as well as match_invc_id.
Expected result tqty_matched (shipsku) and match_invc_id should be properly populated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!