RMS 12: Consignment Purchase Order (PO) Is Not Extracted Correctly (Doc ID 1268399.1)

Last updated on NOVEMBER 30, 2015

Applies to:

Oracle Retail Merchandising System - Version 12.0.5IN and later
Information in this document applies to any platform.
Checked for relevance 23-Aug-2012
Checked for relevance as on 27-JAN-2014

Symptoms

In Retail Merchandising System (RMS) 12.0.5IN (India localized version), consignment purchase orders (PO) are not extracted correctly.


Steps to Reproduce:

  1. Set the consignment frequency as weekly (let EOW_DATE be 7).
  2. Load RTLOG with consignment item for date 1. 
  3. INVC_HEAD will be created for INVC_Date (say, 7). INVC_DETAILS will be populated.
  4. Load RTLOG with consignment item for date 2.
  5. INVC_HEAD will be created/appended for INVC_DATE (say, 7). INVC_DETAILS will be appended/created.
  6. RTLOG of dates 3 and 4 are not processed.
  7. EDIDLINV batch executes on day 7 and data is exported to Retail Invoice Matching (ReIM).
  8. EDI_SENT indicator is Y for the above invoice.
  9. On day 8, if RTLOG of 3 and 4 are processed, this will populate INVC_HEAD, INVC_DETAILS of the same PO generated for that time period (i.e., 1 to 7); however, INVC will not be extracted. This leads to data inconsistency, as TRAN_DATA and INVC_HEAD, INVC_DETAILS are not in synch.

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