Receiving Missing Cartons In SIM Update Incorrectly Store_item_stock_history (Doc ID 2937811.1)

Last updated on MARCH 27, 2023

Applies to:

Symptoms

Receiving Missing Cartons in SIM updates incorrectly store_item_stock_history

When marking a carton as missing (CloseTransferDeliveries Batch), QUANTITY_IN_TRANSIT is updated to zero (destiny) and QUANTITY_TOTAL (origin) is updated ("gain") with the amount that had been shipped. This movement is registered in the store_item_stock_history table, but as "loss" (reason_code 183 - Stock Out), wouldn't the correct one be with reason_code 182 - Stock In? since the parts went back to their origin?


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. For example, today is July 4 and the parameter is set AUTO_CLOSE_RECEIPT =3 (config_store)
2. Create and dispatch a store to store transfer in SIM
3. Run CloseTransferDeliveries Batch on July 7, for close the open transfer deliveries and auto confirms all the transfer deliveries based on the store parameter “Auto Close Receipt”.
4. Note QUANTITY_IN_TRANSIT is updated to zero (destiny) and QUANTITY_TOTAL (origin) is updated with the amount that had been sent ("gain")
5. This movement is registered in the store_item_stock_history table, but as a "loss" (reason_code 183 - Stock Out)

Changes

Cause

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