My Oracle Support Banner

Drip Horizon Calculation Does Not Consider Activities Dispatched Before Shift Start (Doc ID 2485906.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Real-Time Scheduler - Version 2.3.0.2.0 and later
Oracle Utilities Mobile Workforce Management - Version 2.3.0.2.0 and later
Information in this document applies to any platform.

Symptoms

In the evening, we dispatch the first activity for the shift next day in ORS.
The shift is not yet started and the activity has the status 'Queued For Dispatch'.
In the morning when the shift is started this activity status will change to 'Dispatched'.
The next activity in the shift will also change status to 'Dispatched'.

This is not what we expect because we have:
Enable Auto Dispatch = TRUE
Auto dispatch on completion = TRUE
Number of Tasks to Dispatch = 1

Shift templates all have:
Drip Mode = Standard
Drip horizon = 1

We have tested this and it seems that any activity already dispatched when shift is started is not considered by the Auto dispatch process and the next planned activity in the shift is dispatched.

Changes

 

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.