"Cannot update the SHIPMENT_STOP record. LOCATION_GID must be set" Exception When Sending an Actual Shipment Transmission Inbound with RC Transaction Code
(Doc ID 2282554.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.7 to 6.4.3 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
When sending an ActualShipment transmission inbound to OTM, the transmission fails with the below error. The XML has a managed child field of ShipmentStopDetail ONLY and not
ShipmentStop. Defining the shipment stop in the ActualShipment xml should not be required.
ERROR
---------------
EXPECTED BEHAVIOR
-----------------------
It is expected that the transmission process successfully with no errors.
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Send a ActualShipment XML inbound to OTM with no LocationGid specified for shipmentstop element. Ensure the XML has a transaction code of RC and a managed child field of ShipmentStopDetail ONLY and not ShipmentStop.
2. The error is observed
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 |