Issue With Rplatupd Batch Populating PRIMARY_REPL_SUPPLIER Field (Doc ID 1956947.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Merchandising System - Version 13.0.3.1 and later
Information in this document applies to any platform.

Symptoms

Whenever activating replenishment for SKU level item, the values are populated in REPL_ATTR_UDDATE_HEAD.  Then after running the rplatupd batch, records are inserted in REPL_ITEM_LOC, filling the PRIMARY_REPL_SUPPLIER field for warehouse stock category.  This is correct in the case of using WH location in order to be able to generate the automatic orders; but at the same time, this is not correct in the case of using Store as a location.  In the latter case, PRIMARY_REPL_SUPPLIER should not be populated.


Steps to Reproduce:

  1. Create an item
  2. Set up replenishment for the created item; confirm to populate the schedule date
  3. Conclude that there are records in REPL_ATTR_UDDATE_HEAD and not in REPL_ITEM_LOC table
  4. Run rplatupd batch
  5. Conclude that an entry will go to REPL_ITEM_LOC table, and PRIMARY_REPL_SUPPLIER field is populated

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