Activity Time Factor Calculates Incorrect Appointment Durations
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Operational Planning - Version: 5.5
This problem can occur on any platform.
When using activity time factors of 0.49 and 0.51 on a location resource calendar, the number of appointment slots used is incorrect
Expect the correct number of appointment slots to be used
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Build a shipment with a delivery location and an order release that has the following attributes.
Location with a slot time interval of 10 min
Location role with a fixed handling time of 6 minutes and 3 minutes Variable handling time per
Location resource with a calendar attached that has a activity time factor specified. This needs
to be changed between 0.49, 0.50 and 0.51 to replicate the issue. The problem happens when the
factor is set as 0.49 or 0.51
Order Release with 26 ship units
2. Compute the Appointment time wirth the various activity time factors and find that when 0.49
and 0.51 is specified, the number of slots used is 4 for a 84 minute activity window when the time
taken would be 41.16 for 0.49 and 42.84 for 0.51.
-- Business Impact:
The issue has the following business impact:
Due to this issue, users cannot use activity time factors reliably
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