My Oracle Support Banner

Patches For Very Slow Dispatching And Errors Deferring Field Activities in MWM/ORS (Doc ID 2274585.1)

Last updated on SEPTEMBER 28, 2022

Applies to:

Oracle Real-Time Scheduler - Version to [Release 2.1 to 2.3]
Oracle Utilities Mobile Workforce Management - Version to [Release 2.1 to 2.3]
Information in this document applies to any platform.


**Disclaimer:** This KM article may include the following abbreviations:

MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
FA - Field Activity



Deferring field activity causes schedule manager to reject ALL scheduler updates.

If an FA has a time window that ends at midnight, for example, 12-12-2016 12:00AM to 12-17-2016 12:00AM and, the dispatcher defers the FA to 12-17-2016, the schedule manager completely stops working and the system stops working.

This is because the time window inside the system defers the FA to 12-17-2016 12:00AM and the system can't calculate an arrival time window for the FA (it would be from 12-17-2016 12:00AM to 12-17-2016 12:00AM).

The only workaround is to go into the FA (after looking at log files which dispatchers don't have access to) and adding time to the end data. If the schedule manager would just ignore this error and continue on, it would resolve itself when the time window gets extended.

In some instance, this case can be found where the number of registry records doesn't match as shown in the the logs as:



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.