ReIM EDI Invoice Upload Process Updates Existing Credit Note Request When Ext_doc_id/RTV Authorization Number Already Exists (Doc ID 1552161.1)

Last updated on FEBRUARY 22, 2016

Applies to:

Oracle Retail Invoice Matching - Version 11.0.16.7 and later
Oracle Retail Merchandising System - Version 11.0 and later
Information in this document applies to any platform.

Symptoms

In Oracle Retail Invoice Matching (ReIM) version 11.0.16.7:

'reimediinvupload' batch process is updating the total cost and total quantity of existing Credit Note Request - Quantity (CRDNRQ) when ext_doc_id/RTV Auth_num already exists in IM_DOC_HEAD.

The process will add the Cost and Quantity of the items in the new CRDNRQ to the existing CRDNRQ document. If one reprocesses the same flat file again, it will continue to add the cost and quantity to the existing document. If the process does not find any items that are the same, no records are created or document updated and the process finishes successfully without creating a document.  If the new document in the flat file generated from the EDIDLINV has an ext_doc_id/RTV Auth_num that already exists for a different vendor, it will finish successfully without creating any document or updating the existing document because no item will match. If there are two different different RTVs in the flat file for the same vendor for different orders with the same auth number, only one will process and the second will error out.
  

Steps to Reproduce:

1a. Create Return To Vendor (RTV)s in Oracle Retail Merchandising System (RMS).
2a. Ship the RTV.
3a. Run the EDIDLINV batch to generate the flat file.
4a. Run reimediinvupload batch in Retail Invoice Matching (ReIM) to load the documents into ReIM. Confirm documents loaded.
5a. Run reimediinvupload batch again using the same file, total and quantity are doubled on the document.

1b. Create Return To Vendor (RTV)s in Retail Merchandising System (RMS) with the same RetAuth# as a previous RTV for the same vendor with at least one item similar to the previous one.
2b. Ship the RTV.
3b. Run the EDIDLINV batch to generate the flat file.
4b. Run reimediinvupload batch in Retail Invoice Matching (ReIM) to load the documents into ReIM.
5b. No new document is created. Existing document with the same auth#/Ext_doc_id is updated adding the cost and quantity of the items in common to both documents.


Impact on Business:
Not able to track RTVs / Credit Note Requests created in RMS/ReIM. Erroneous data or no data created for specific scenarios in ReIM.

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