ITEM_SUPP_COUNTRY/ITEM_SUPP_COUNTRY_LOC Unit Cost Mismatch After Change to PRIMARY_LOC_IND (Doc ID 2043868.1)

Last updated on AUGUST 17, 2016

Applies to:

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

Goal

In Oracle Retail Merchandising System (RMS) 13.2.x, there is a noted mismatch between the UNIT_COST appearing in ITEM_SUPP_COUNTRY and ITEM_SUPP_COUNTRY_LOC tables after a change is made to PRIMARY_LOC_IND.


Steps to Reproduce:

  1. Create an item as in the example below:

    ITEM_MASTER.STATUS = A
    ITEM_SUPP_COUNTRY.UNIT_COST = 83,620
    ITEM_SUPP_COUNTRY_LOC.LOC = 910    unit_cost = 83,620    PRIMARY_LOC_IND = 'Y'
    ITEM_SUPP_COUNTRY_LOC.LOC = 12     unit_cost = 78,520    PRIMARY_LOC_IND = 'N'
      
  2. Note that the UNIT_COST for ITEM_SUPP_COUNTRY matches the UNIT_COST for the primary supplier (83,620).

  3. Go to [ITEMSUPPCTRYLOC] form and change PRIMARY_LOC_IND to location 12.

    ITEM_SUPP_COUNTRY.UNIT_COST = 83,6200
    ITEM_SUPP_COUNTRY_LOC.LOC = 910    unit_cost = 83,620   PRIMARY_LOC_IND = 'N'
    ITEM_SUPP_COUNTRY_LOC.LOC = 12     unit_cost = 78,520   PRIMARY_LOC_IND = 'Y'
      
  4. Now note that the UNIT_COST in ITEM_SUPP_COUNTRY does NOT match that of the primary supplier (78,520).

 

Why is this happening, and how can we prevent this?

Solution

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