My Oracle Support Banner

Overlapping Time Windows For The Same Time Window Usage Is Not Allowed, Time Window Calculation Corrections And Manual Allocation With A '0' Duration Time Window (Doc ID 2787042.1)

Last updated on SEPTEMBER 13, 2022

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.3.0.1.0 to 2.3.0.3.0 [Release 2.3]
Information in this document applies to any platform.

Symptoms

1) We have a couple of task types with cutoff times and complete within days = 1.  When this activity type is created after the cutoff time we are seeing the M1_EAR_SCHD_DTTM and M1_DUE_BY_DTTM are the same.  This causes a problem when the dispatcher tries to allocate it on the day created and the application indicates, "Overlapping time windows for the same time window usage is not allowed".  The scheduler will not move the activity to mobile device so as a workaround we have to go into the activity and change the effective end date and add some time to it.

2) When an activity with open ended time window and due by set in business days is updated, the time windows are calculated as if for the new activity, potentially resulting in a different (longer) ETW from the original even when startTime was not changed.

3) When an open-ended activity has a number of extension time windows and, during an update it's startTime was changed, it is possible to have an error due to overlapping time windows.

4) Manual allocation fails when the activity has a 0 duration ATW due to calendar or work profile limitations.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.