Date Update From Order Release To Shipment Does Not Raise Exception If The Change is Within The Window Of The First Order's Times
Last updated on OCTOBER 18, 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.
Having ORDER RELEASE - PROPAGATE CHANGES enabled, when changing the order release dates on one of the two order releases planned into shared shipments in such a way that the Early Pickup Date of the updated order fall WITHIN the window of the first order's times, these should be updated on the shipment as well, making the shipment infeasible
It is expected to have the dates propagated to the shipment and shipment be marked infeasible so that exception is raised.
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