Last updated on JULY 09, 2014
Applies to:Oracle Transportation Management - Version: 5.5 to 5.5 - Release: 5.5 to 5.5
Information in this document applies to any platform.
Checked for relevance on 23-Apr-2010
Client inputs a substitute location (say --LOS13425) to the Destination Location of LOS13424. They
then update the Order Release (say the latest delivery date) via xml. It is observed that OTM now
automatically adds the substitute location LOS13425 in the Destination Plan To field of the Order
Release. They then bring in a an Update 2 (via XML) which changes the Destination Location to a
different location (say LOS14387). It is observed that OTM does not take off the previous Destination Plan To location from the order release and so the order is sent to the wrong location. Client expectation is that the Destination Plan To location should be removed since the new destination location does not have any substitute location.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms