Last updated on JUNE 07, 2017
Applies to:Oracle Real-Time Scheduler - Version 22.214.171.124 to 126.96.36.199 [Release 2.1]
Oracle Utilities Mobile Workforce Management - Version 188.8.131.52 to 184.108.40.206 [Release 2.1]
Information in this document applies to any platform.
On : 220.127.116.11 version, Scheduling
Deferring field activity causes schedule manager to reject ALL scheduler updates.
If an FA has a timewindow 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 timewindow 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 timewindow 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:
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