Cancelation, Shipment Or Receipts Of Stock Order Fails In WMS After It's Been Waved
(Doc ID 2757167.1)
Last updated on MAY 01, 2023
Applies to:
Oracle Retail Merchandising Foundation Cloud Service - Version 19.0 and laterOracle Retail Allocation Cloud Service - Version 19.0 and later
Information in this document applies to any platform.
Symptoms
When canceling a stock order (allocation or transfer) after the Logfire WMS has waved - Stock Order, Shipment and Receipt messages are failing to integrate in WMS/RMS.
Steps to Reproduce:
1. Create Allocation and notice that it is integrated in Logfire WMS.
2. Wave the Allocation. Notice that USM/RMS is not notified of this process. [Enhancement request (IDEA) is logged for Logfire WMS].
Issue#1:
Cancel the Allocation - Notice it deletes the existing Allocation from RMS and delete message fails to integrate in WMS.
Issue#2:
Continue to ship and receive this Allocation and correspnding ASNOut and Receipt messages fail to integrate in RMS as Allocation does not exist.
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 |
| Cause |
| Solution |
| References |