ReleaseOnStop Elements Missing For Shipment Stop Going Into X-dock
(Doc ID 2217077.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.6 to 6.4.3 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
When tendering a shipment where one location has a role of XDOCK, the raw XML which is being sent does not contain the ReleaseOnStop element.
The expectation is that the ReleaseOnStop element will be generated for every Release that has a pick or drop activity at the stop.
The issue can be reproduced at will with the following steps:
1. Search for shipments 02067, 02068.
2. Both shipments have XDOCK location TIRASPOL
3. Perform Secure resources on any of them: Actions -> Shipment Managment -> Tender -> Secure Resources
4. Notice that in the received Tender XML you do not see the ReleaseOnStop for the Xdock location.
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 |