Time tasks - standard approach

In the standard approach, two kinds of time tasks are sent to the cloud – one referring to an object (O-type) and another one referring to a person (P-type). They’re paired in FSM based on a common match code.

If a time task exists for a given activity (service order and person time tasks), it can be chosen as ‘task’ for time efforts created in the mobile app. This can generate an excessive number of tasks. For 5 operations, at least 10 tasks are sent (depending on /PACG/ECM_SOLAF - Activity types for time tasks config it can be more) – 5 referring to the person, 5 referring to the service order. This approach is recommended when time tasks are not person but service order dependent.

Configuration

/PACG/ECM_SCG - Service call general settings

[OBSOLETE] /PACG/ECM_SCTD – Service Call types definition: Overview and Detail / /PACG/ECM_VSCTD - Service Call types definition

Send activity types as time tasks  (short label TAT active) - Work with CO activity type for time confirmation. Those activity types are sent per order as defined in transaction /PACG/ECM_SOLAF - Activity types for time tasks .

Generate time task for order operation (short label Send Time Task) - Send order operation as „task” for time effort capturing.

Use time tasks’ act. type for conf./CATS (short label Act. Type as TT) - Activity type as time task.

No time task for person (short label Not for person) - Do not send time task for person.

/PACG/ECM_SOLAF - Activity types for time tasks

Steps

1. Create a service order of type YBS4 (the one set in /PACG/ECM_VSCTD - Service Call types definition) and release it.

2. Four /PACG/ECM_ITYPE_SCALL_TASK idocs are sent. Two reference an object, the other two a person. One pair for one activity type.

Activity types taken from /PACG/ECM_SOLAF - Activity types for time tasks .

The time tasks can also be found by creating a query in the Analytics and Reporting Module.

3. Release assignment in FSM.

4. Go to the mobile app and create an effort for the activity assigned.

Observe how one task with person reference for each activity type (101/102) can be found.

5. Save the effort with the task ‘Service Standard’ and synchronize.

6. Approve the effort in Time and Material Journal.

7. An idoc of type /PACG/ECM_ITYPE_TIMEEFF_IN is received. It contains the task id (activity type 101, person reference).

8. Notice how the actual work value of the activity has changed in PM Order Confirmation.

9. Create another effort, this time with task ‘Service specialist’.

Save, synchronize and approve in Time and Material Journal.

10. An idoc of type /PACG/ECM_ITYPE_TIMEEFF_IN is received. It contains the task id (activity type 102, person reference).

11. A new activity type and actual work value appears in PM Order Confirmation.

Also another cost element can be found in Plan/Actual Comparison in the service order.