ASNOut Message from SIM to RMS Fails in RMS RIB Message Table Due to Duplicate BOL Number

(Doc ID 1541839.1)

Last updated on JULY 25, 2017

Applies to:

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

Symptoms

ASNOut message from Store Inventory Management (SIM) to Retail Merchandise System (RMS) fails in the RMS Retail Integration Bus (RIB) message table due to a duplicate BOL number.

When SIM publishes a Store to Store Transfer or a Store to Warehouse transfer (i.e., return to warehouse from store) to RMS, the ASNout RIB message generates a BOL number using the Transfer ID or Return ID in SIM, then inserts this BOL ID into the Shipment table in RMS.

In SIM, the Store to Warehouse transfer (i.e., return to warehouse from store) and Store to Store transfer information appears in two different tables.  The transfer ID and/or Return ID are sequence numbers generated in the transfer or return tables; therefore the the Transfer ID/Return ID are the same from time to time.
- Store to Store transfer is saved in TRANSFER and TRANSFER_LINE_ITEM.
- Store to Warehouse transfer is saved in RETURN and RETURN_LINE_ITEM.

Since the BOL number in the ASNout message is using the Transfer ID/Return ID in SIM, this has the potential to cause duplicate BOL IDs.  Messages are failing in RMS due to duplicate BOL IDs for these transactions.


Steps to Reproduce:

1. In SIM, create a Store to Store transfer.  Dispatch the Transfer.
   Example: Transfer ID is saved in this table as transfer ID #1

2. Go to RMS, TSFHEAD table:
   - Validate that there is a transfer from SIM published to RMS successfully.  Transfer TSF_NO #1 is saved in TSFHEAD table in RMS.

3. Go to RMS SHIPMENT table:
   - Validate that there is a shipment record in this table. The BOL number is also saved in this table. The BOL ID is ID #1; the same as the TSF_NO in the TSFHEAD table.

4. Go back to SIM, RETURNS.  Create and dispatch  a Return to Warehouse. 
   - SIM saves this record in the SIM tables: RETURN and RETURN_LINE_ITEM
   - Note the Return ID in this table
   Example: Since this is the first return record created in the system, the system is saved this record as Return ID #1 also.

5. Go to RIB_MESSAGE and RIB_MESSAGE_FAILURE table in RMS side:
   - Find an ASNOut failure message in the hospital.  The error reads "This bill of lading (BOL) number already exists for a different From location and To location"

   The reason for this failure is that the previous store to store transfer has been saved in the TSFHEAD and SHIPMENT tables with the BOL ID #1.

6. Go back to SIM and create and dispatch another Return to Warehouse.
   - The return record in SIM is now saved in SIM RETURN table with a Return ID #2.

7. Go to RMS and validate this: RMS inserts in TSFHEAD and SHIPMENT table with the Transfer ID #2 and BOL ID #2.

8. Go back to SIM and create and dispatch a different store to store transfer in SIM.
   - The transfer record in SIM is now saved in the SIM TRANSFER table with a Transfer ID #2

9 Go to RIB_MESSAGE and RIB_MESSAGE_FAILURE table on RMS side:
   - Find an ASNOut failure message in the hospital.  The error reads "This bill of lading (BOL) number already exists for a different From location and To location"

   The reason for this failure is that the previous return to warehouse has been saved in the TSFHEAD and SHIPMENT tables with the BOL ID #2.

Observe the following messages and the error failure message:

 

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