My Oracle Support Banner

DATAFIX: To Remove Future Date From The Actual Departure Date User Entered By Mistake Enabling Interface Trip Stop To Complete Successfully (Doc ID 2770077.1)

Last updated on JULY 06, 2021

Applies to:

Oracle Shipping Execution - Version 11.5.10.CU2 to 12.2.10 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.


During Ship Confirm on 01-Mar-21, user incorrectly entered the "Actual Departure Date" as 26-Mar-21.
It caused  the transaction to get stuck during Interface Trip Stop with the following error:


Actual Departure Date of Trip Stop in batch nnnn is a future date.

It is understood that in order to successfully interface the transaction, user should  wait until the actual date and time has occurred or has past to resubmit  the interface trip stop as per the following document:

Interface Trip Stop Completes with Warning: Actual Departure Date of Trip Stop Is a Future Date (Doc ID 1399707.1)

Is there a datafix to change and correct the date to an earlier date versus waiting?


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

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