Date Update From Order Release To Shipment Even When Dates Are Invalid (Doc ID 2237552.1)

Last updated on AUGUST 24, 2017

Applies to:

Oracle Transportation Management - Version 6.3.3 to 6.4.3 [Release 6.3 to 6.4]
Information in this document applies to any platform.

Symptoms



2 order releases with the following details are created:
Order release 1: EPD as 16/12/2016 and LDD 21/01/2017
Order release 1: EPD as 16/12/2016 and LDD 21/01/2017
Both from the same source and destination.

These 2 Orders are planned into a single shipment with start date as 26/12/2016 and end date as 28/12/2016. Then an xml update is sent on order release 2 with the following dates: EPD as 22/01/2017 and LDD 31/01/2017. There is an order release agent which triggers on ORDER - MODIFIED and has the action ORDER RELEASE - MOD - PROPAGATE CHANGES with pickup and delivery dates being propagated.


This date does not fall in the shipment time window and also not in the time window of the 2nd order release. Yet it is seen that the shipment date was update to 23/01/2017 as start date and 25/01/2017 as the end date. There is also an agent error as well while propagating the changes to the shipment which says


If there is an error and the shipment dates would be infeasible then the dates should not be propagated

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create 2 Orders and plan them on to a shipment
2. An XML update is sent to change the order dates
3. Shipment Dates are changed even when the dates are not feasible



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms