Shipment Start Time The First Leg Does Not Consider Minutes Correctly and the Shipment Starts 59 Minutes Earlier than Expected. (Doc ID 1513342.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.2.0 and later
Information in this document applies to any platform.

Symptoms

On OTM version 6.2:

ACTUAL BEHAVIOR
---------------
When a carrier offers an agreed daily pickup time at 16:00, before the actual pickup, handling is required, for this purpose a handling leg is used that should have a time of zero minutes. This was both the Shipment and Handling Shipment will start at 16:00, however the following is seen:

Date Available by 15-10-2012 9:00:
Rate Inquiry Result:
The start time is correctly set to 16:00 on both the first leg and the second leg.

Date Available by 15-10-2012 9:01:
Rate Inquiry Result:
The start time is incorrectly set to 15:01 (expected result is 16:00).



EXPECTED BEHAVIOR
-----------------------
Expect the start time to be 16:00 in both cases.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1 - Log onto OTM.

2 - Create an Itinerary with two legs.

3 - Create two Rate Records, one for each leg
a - For the first leg (handling) this is to include a Rate Service where the rate service is based on LOOKUP, using values set to 0 minutes.
b - For the second leg set the Rate Record to use a Rate Service based on DAYDURATION so the Shipment will start at 16:00.

3 - Run the Rate Inquiry (RIQ):
Date Available by 15-10-2012 9:00:
Rate Inquiry Result:
The start-time is correctly set to 16:00 on both the first leg and the second leg.

Date Available by 15-10-2012 9:01:
Rate Inquiry Result:
The start-time is incorrectly set to 15:01 (expected result is 16:00).


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