New Store Location Ranging Adds Records on POS_MODS Table for Non-Sellable SKU Items (Doc ID 2126324.1)

Last updated on APRIL 15, 2016

Applies to:

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

Symptoms

Actual Behavior
---------------
When attempting to add additional Store locations a day after a non-sellable SKU is created, the newly ranged locations are written to POS_MODS table with a tran_type '1' for the SKU/locations, and a tran_type '2' for the UPC/locations.


What is Working
-----------------------
When a non-sellable SKU is approved in RMS, records are not added to POS_MODS (as expected) on the create date.

Expected Behavior
-----------------------
Expect only sellable SKU on POS_MODS table.


Steps to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:

  1. Navigate to Items -> Items -> New Item
  2. Item Type = Regular Item
  3. Sellable = No / Orderable = Yes / Inventory = Yes
  4. Create a non-sellable SKU (with a UPC of UCC12), ranging it to at least 5 locations.
  5. Add the following Item Location Traits:
    • Qty / Key Options = Prohibited
    • Manual Price Entry = Prohibited
    • Returnable = No
    • Refundable = No
  6. Approve the Item.
  7. Confirm no records are written to POS_MODS for the Item / locations.
  8. (next day) Edit the Item, navigating to Item Location Window [itemloc].
  9. Add at least 5 additional Stores to the SKU.
  10. Add the same Item Location Traits to the newly ranged locations.
  11. Save changes to the SKU.
  12. Verify records exist on POS_MODS for the newly added / ranged locations.

 

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