Depot Cut Off Does Not Work Becasue Trigger Date Times Are In The Past (Doc ID 2103783.1)

Last updated on FEBRUARY 22, 2016

Applies to:

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

Symptoms

On : Scheduling

ACTUAL BEHAVIOR
---------------
Depot cut off does not work

Current the batch controlled depot cut off does not work in test environment. It is configured to run but no actual cut off are created. Depot runs are not closed.

The depot config in a test environment is identical to a development environment as they were imported via a Bundle. Batch control M1-DPTTW is running and also identical to development were everything is working.  The batch control M1-DPTTW looks identical.

There are activities that should have been in a cut off.

EXPECTED BEHAVIOR
-----------------------
Depot cut off should work as per designed.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. go to Menu. click on main menu
2. click on batch and go to batch control M1-DPTTW
3. navigate to admin menu, click on A --> activity

Cause

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 hundreds of Community platforms