Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.5.04
This problem can occur on any platform.
-- Problem Statement:
When manually creating a voyage via the UI and populating departure/arrival dates/times for the
stops, the field DEP_DATE on the VOYAGE table is automatically populated with the departure date
from the VOYLOC table.
The VOYAGE departure date is not updated when the VOYLOC departure date is chaged.
As a result, when searching for a voyage the field departure date represents the DEP_DATE field rather than the first departure date on the stop details (voyage locations). If this is different, the voyage is not returned in the search results.
A similar effect happens, when using CSV files to upload data with a different DEP_DATE from the first
departure date from the VOYLOC table, or leaving it blank so that the system uses the sysdate.
Once the DEP_DATE is populated - it cannot be edited via the UI and any update to the dates for
the stop locations is also not reflected.
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