Configuration Parameter 'NumMinutesAfterInactivateCurrentShift' Added to DHTSVINI to Inactivate Old Shifts (Doc ID 975134.1)

Last updated on DECEMBER 05, 2019

Applies to:

Purpose

Prior to Mobile Workforce Management (MWM) v1.4.5.24, old shifts could remain active indefinitely for as long as a crew did not have another shift scheduled.  Shifts can possibly remain active forever if the crew has no future shifts.  In an integrated environment, Oracle Real Time Scheduler (ORS) and MWM are out of sync during this time since these shifts are removed from ORS as they are disabled 'X' hours after the scheduled completion of the shift. The reason they are still active in MWM is because the logic is based on the start time of the next shift.  Further, dispatchers can accidentally assign work to old shifts that have completed.

The activate next shift logic has been altered to address this issue.

Scope

This article is intended for use in MWM and ORS integrated environments.  Any changes should be evaluated as a change in business process and implemented by a system administrator.  The complete list of changes in the v1.4.5.24 maintenance release should be reviewed in its entirity for other effects on the system.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.