Return to Warehouse in SIM, Using the Unavailable Stock Option Fails at RMS Side.
Last updated on JUNE 24, 2017
Applies to:Oracle Retail Merchandising System - Version 14.1.2 and later
Oracle Retail Store Inventory Management - Version 14.1.2 and later
Information in this document applies to any platform.
While creating a return to warehouse in SIM, using the unavailable stock option And when the SOStatus reaches after ASNOut to RMS, it will go to the error hospital with below error.
While creating a return to warehouse in SIM, using the unavailable stock option As a result, SOStatus message gets published with inventory type as ‘U’ and ASNOUT with NULL disposition values. If these messages are received out of sync i.e. ASNOUT message reaches first to RMS and process same, it deducts the qty_shipped from the Available to Sell (ATS) bucket since the disposition values are NULL in SOStatus.xml.
When SOStatus message is received later, RMS update the tsf_qty in tsfdetail incase it is not equal to the shipped qty and skip any further processing. As a result, return is created in SIM from unavailable bucket reduces the stock from ATS bucket in RMS which makes Inventory_type as 'A' in tsfhead table instead of 'U'.
Steps to Reproduce:
Step-1 : Make Sure ASNOut and SOStatus Subscribers are down in RIB-RMS admin GUI page.
Step-2: Perform below navigation in SIM application:
i) Return Type: Warehouse
ii) Enter reason as: Unavailable Inventory
iii) Enter the quantity: 10
Step-3: Make ASNOUT Subscriber up and check transfer is created in RMS with Inventory_type as 'A' in tsfhead table.
Step-4: Make SOStatus Subscriber up and you will see error in adapter logs and record has been stuck in error hospital table.
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