When a Transfer/Allocation Shipment Is Late Posted in RMS, Such That A Stock Count Has Already Been Processed After the Ship Date, the Stock On Hand Is Still Updated for the Pack Item
Last updated on FEBRUARY 01, 2018
Applies to:Oracle Retail Merchandising System - Version 13.2 and later
Information in this document applies to any platform.
In Version 12 of Retail Merchandising System (RMS), when a late shipment transaction is posted into RMS for a transfer or an allocation, such that a stock count has already been performed and variance adjusted for the shipping location, the ITEM_LOC_SOH table STOCK_ON_HAND column is still updated (reduced) by the quantity shipped. This happens only for a pack item. The corresponding PACK_COMP_SOH is also updated for the component item in this scenario.
The expected behavior in this case is that if the shipment date is before the stock count was performed, the stock on hand should not be updated. This is because, the shipped inventory is assumed to have been accounted for during the physical count.
Steps to recreate:
1. Create a transfer/allocation from a warehouse (WH) to a store.
2. Approve the transfer, but do not ship yet.
3. Create a unit stock count for the item and the Warehouse.
4. Run Stkupd batch to take a snapshot of the current inventory at the warehouse.
5. Run Stkupld batch to upload the physical count to the STAKE_SKU_LOC table.
6. Create a Unit and Variance Adjustment through the RMS Stkfind screen for the cycle count.
7. Run Stkvar batch such that the ITEM_LOC_SOH table is updated with the counted quantity.
8. Now run a shipment script (with the ship_date as the date before the stock count was performed).
9. Check the ITEM_LOC_SOH table. The STOCK_ON_HAND is deducted by the qty shipped from the WH to the store.
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