Action ' Manually Assign Order To Existing Shipment' Throws Error "Cannot find a stop on shipment that matches dropoff location. (destLocationGid=???, shipmentGid=DOMAIN.XXXXX)"
(Doc ID 2092843.1)
Last updated on MAY 06, 2022
Applies to:Oracle Transportation Management - Version 6.0 and later
Information in this document applies to any platform.
Using "Manually Assign to Existing Shipment" Action to add an order to an existing shipment. The order dates and Source and Destination Locations on the order to be assigned match the same on the Shipment that the order is to be assigned to. When running the action it errors with the below error. If instead of using the action, "Manually Assign to Existing Shipment" the Action “Move Order to Existing Shipment.” is used, then the order is successfully assigned to the shipment.
The issue can be reproduced at will with the following steps:
1. Created two Order Releases having different "Plan To" (or "Plan From")
2. Plan order one order onto a shipment
3. For othe order, run Action - Operational Planning>>Create Buy Shipment>>Manually Assign to Existing Shipment and enter above shipment as the shipment to assign the order to.
4. Observer the error thrown: “Cannot find a stop on shipment that matches dropoff location. (destLocationGid=???, shipmentGid=DOMIAN.XXXXX)”
The issue has the following business impact:
Due to this issue, users cannot use the action “Manually Assign to Existing Shipment”
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