Field Service>Calculated Cost for Scheduling: Non Critical Task Cost Is Getting Applied For Critical Tasks
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Field Service - Version 12.1.2 to 12.1.2 [Release 12.1]
Information in this document applies to any platform.
On : 12.1.2 version, Task Scheduling & Assignment
When a task is marked as critical (jtf_tasks_b.critical_task_flag), the calculated cost for scheduling should be less than for an identical task that is not marked as critical. The cost difference should be determined by the 'non critical task cost' in the scheduler rule. But that is not happening. The cost is exactly the same for both tasks.
Debug data shows that both tasks are handled as if they are not critical (ie both getting the 'non critical task cost'):
csr.core.server.CostCalculator.nonCriticalTaskCost.Critical Customer Cost - 17-11-2014 06:13:54 (1416222834759)>non Critical Task Cost 2000.0 : Cost Factor = 2000
The issue can be reproduced at will with the following steps:
1. In the scheduler rules, set a value for 'non critical task cost'
2. Create 2 identical tasks, for the same SR
3. Mark one of the tasks as critical (by setting jtf_tasks_b.critical_task_flag to Y)
4. Use intelligent mode in the scheduling advice to get plan options for both tasks (do not actually schedule them to keep the circumstances identical). The calculated cost as shown in the plan options is the same.
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