My Oracle Support Banner

After the Shipment Stop Re-sequence Action, the Tender Offer - Stop Reason is Not Generated to Properly Match the New Sequence of Stops (Doc ID 2665542.1)

Last updated on MAY 17, 2020

Applies to:

Oracle Transportation Management Cloud Service - Version 19.3 to 20.2 [Release 19 to 20]
Information in this document applies to any platform.

Symptoms

After using the Buy Shipment Stop Re-sequence Action, the outbound Tender Offer XML generated will incorrectly have a Stop Reason that does not match the Stop Activity.


For Example:
Before Shipment Stop Re-Sequence (Stop Reason from Raw XML)

Stop#    Type  Stop Reason - Location ID
==============================
Stop 1   P         Partial Load - SAV
Stop 2   P        Complete Shipment - PHL
Stop 3   D        Partial Unload - ATL
Stop 4   D        Partial Unload - HOU
Stop 5   D        Complete Unload - DEN



After Shipment Stop Re-Sequence (Stop Reason from Raw XML)

Stop#    Type  Stop Reason - Location ID
==============================
Stop 1   P        Complete Shipment - SAV
Stop 2   D        Partial Unload - DEN
Stop 3   D        Partial Unload - HOU
Stop 4   P        Partial Unload- PHL
Stop 5   D       Complete Unload - ATL

*The Stop Reasons are not matching the Stop Activity as Stop 1 would be Partial Load and Stop 4 would be Complete Shipment

 

Changes

 N/A

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.