Shipping from RMS Does Not Guarantee Container ID and ASN Number Are Unique to RWMS Database (Doc ID 1980403.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Merchandising System - Version 13.2 and later
Information in this document applies to any platform.

Symptoms

Shipping from Retail Merchandising System (RMS) does not guarantee that the container ID and Advance Shipment Notice (ASN) number are unique to the RWMS DB.
When system_options.ship_rcv_store= 'Y' and system_options.ship_rcv_wh = 'N' (indicating that SIM is not installed and shipments for store to warehouse transfers can be created in RMS and published to RWMS), RMS does not guarantee that the Container ID/Carton number and ASN number created and published to RWMS are unique to the RWMS database.

Thus the message may fail in RWMS database hospital whenever a record with the same container ID or ASN number exists in RWMS.   During testing of store to warehouse transfers shipments published from RMS to RWMS, it was found that the ASNInCre message fails in RWMS database hospital tables as:

  
After making sure the Container ID and ASN number are unique, the message was successfully consumed.

Steps to Reproduce:

  1. Make sure system_options.ship_rcv_store= 'Y' and system_options.ship_rcv_wh = 'N' in order for RMS to publish ASNOut messages to RWMS.
  2. Create a store to warehouse transfer in RMS and ship it.
  3. Note that the ASNInCre message may fail in RWMS database if the CONTAINER_ID (carton number) already exists in RWMS database.
    RMS should guarantee that the created Carton and ASN IDs are unique to RWMS. The IDs generated can be RMS.CTNxx or RMS.ASNxx, for example, to guarantee uniqueness.

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