My Oracle Support Banner

SIM Receives Carton as Missing at Intended Store Prior To Receiving Misdirected Carton (Doc ID 2530418.1)

Last updated on JULY 12, 2023

Applies to:

Oracle Retail Store Inventory Management - Version 16.0 and later
Information in this document applies to any platform.

Symptoms

Scenario 1:

If the intended location receives carton as missing prior to it being received as misdirected, the In-Transit Stock on Hand (SOH) goes negative at the intended receiving location. After reviewing the SIM receipt message, SIM does not include any business-context that the receipt represents a misdirected carton. Retail Store Inventory Management (RSIM) includes an auto-generated container ID (not the original container ID). SIM does not send a receipt against intended receiving location that was updated to missing.  RMS handles as if Transfer was an Overage with an unexpected new container. In-transit SOH should remain at zero if carton was received as missing at intended location prior to receiving carton as Misdirected.

Scenario 2 :

When a store receives a misdirected container the intended store’s container displays as missing (expected) in SIM. However, in RMS intended receiving location remains In-Transit and the sending location appears to have their shipped SOH quantities deducted a second time.  After reviewing the SIM receipt message, SIM does not include any business-context that the receipt represents a misdirected carton. SIM includes an auto-generated container ID (not the original container ID). SIM does not send a receipt against intended receiving location that was updated to missing. RMS handles as if Transfer was an Overage with an unexpected new container.


EXPECTED BEHAVIOR
-----------------------
Retail Merchandising System (RMS) updates (missing carton) intended location In-Transit = 0 since carton was misdirected and received at another location. We do not expect In-Transit to remain open in RMS until the tsfclose/docclose processes are ran. Additionally, SIM and RMS on hands should match after receipt. Lastly, if there is only one container and it is misdirected, the transfer should be marked as received with a missing status in the intended location.

Steps to Reproduce:

Scenario 1 :

1. Create and dispatch a store to store transfer in SIM (store A1 to A2 in this example)
    a. For simplicity sake, use 1 SKU (XXX in this example with a quantity of 7)
    b. Note this container number as it will be received as misdirected later
2. Create and dispatch a second store to store transfer in SIM to the store that will receive the misdirected container (store A3 )
    a. For simplicity sake, use 1 SKU (YYY  in this example with a quantity of 4)
3. In the intended receiving location (1st transfer created), receive the container as missing (Confirm new container)
4. In the misdirected location (A3 ), open the second transfer and select Misdirected Container
5. In the Misdirected Container pop up, enter the container number that was marked as missing, then select the container and then the item, selecting apply
   a. Printing a label is optional
   b. Note the new container number if needed for queries
6. Marked the received column to match expected then Confirm the misdirected container
7. Select Default qty then select Confirm and Yes to confirm the delivery
8. Note the on hands of the item that was misdirected at the sending location
   a. In this example both items shipped were affected


Actual Result:


If the intended location receives carton as MISSING prior to it being received as Misdirected the In-Transit SOH goes negative at the Intended receiving location.


Scenario 2 :

1. Create and dispatch a store to store transfer in SIM (store B1 to B2 in this example)
    a. For simplicity sake, use 1 SKU (XXX in this example with a quantity of 5)
    b. Note this container number as it will be received as misdirected later (01380591812011)
 
2. Create and dispatch a second store to store transfer in SIM to the store that will receive the misdirected container (store B3)
    a. For simplicity sake, use 1 SKU (YYY  in this example with a quantity of 3)
 
3. In the misdirected location (B4), open the second transfer and select Misdirected Container
4. In the misdirected Container pop up, enter the container number that was marked as missing, then select the container and then the item, selecting apply
    a. Printing a label is optional
    b. Note the new container number if needed for queries
 
5. Marked the received column to match expected then Confirm the misdirected container
6. Select Default qty then select Confirm and Yes to confirm the delivery
7. Note the Stock on Hand of the item that was misdirected at the sending location

Actual Results:

Misdirecting a container yields out of balances between SIM and RMS. The in transit values of the intended location are affected as well as the on hands of the actual receiving location.
Also of note: the intended location’s Transfer is still listed with a Status of New, but does indicated that the single container is Missing.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.