Page Comparison

With a new approach, time tasks have only one reference – person. If the ‘Task for technician’ field is set in transaction /PACG/ECM_SCG - Service call general settings , tasks are sent only once, with the user data (/PACG/ECM_USERMASTER – User), and they are assigned to a person.

...

• Set the ‘Task for technician’ and ‘No task’ fields in transaction /PACG/ECM_SCG - Service call general settings .

• Send a user to the cloud using transaction(or have it sent automatically when saving /PACG/ECM_MAINT_USER - FSM users / Users → /PACG/ECM_USERMASTER_ALV_USERS - Mass User Maintenance). This generates a time  task time task with a reference object of ‘Person’ and task key ‘SCUSU/[CLOUD USER NAME] [ACTIVITY TYPE]' (see transaction /PACG/ECM_SOLAF - Subtasks - FilterActivity types for time tasks for activity type ranges).

• Create a new service order in SAP, assign an activity to a technician, release, then in the mobile app create a new effort for a given operation, choosing a task related to the technician.

...

See the ‘Configuration’ section in: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/109969456/Time+tasks+-+standard+approach#Configuration

Steps

...

1. Send a user to the cloud with transaction the sending transaction or have it sent automatically by saving /PACG/ECM_

...

1. MAINT_USER - FSM users. This should cause a generation of /PACG/ECM_ITYPE_SCALL_TASK idocs – one for each activity type set in transaction /PACG/ECM_SOLAF -

...

1. Activity types for time tasks .

...

/PACG/ECM_SOLAF - Subtasks - FilterActivity types for time tasks

...

2. Create a service order of type YBS4 (the one set in /PACG/ECM_SCTD – VSCTD - Service Call types definition: Overview and Detail) and release it.

...

3. Observe how no idocs of type /PACG/ECM_ITYPE_SCALL_TASK are sent.

...