Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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.

Summary of necessary steps

  • 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 /PACG/ECM_USERMASTER. This generates a time  task with a reference object of ‘Person’ and task key ‘SCUSU/[CLOUD USER NAME] [ACTIVITY TYPE]' (see transaction /PACG/ECM_SOLAF - Subtasks - Filter 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.

Idoc of type /PACG/ECM_ITYPE_SCALL_TASK generated after sending a user to the cloud.  

The technician’s task can be found in the FSM mobile app while creating an effort for the assigned operation. It’s placed among other person-related tasks.

The ‘Task for technician’ option is recommended when time tasks are not service order but person dependent. The setting should be used with the ‘No task’ field checked as well.

Example

Settings maintained in /PACG/ECM_SCG - Service call general settings . Both ‘No time task’ and ‘Task for technician’ fields are set.

Configuration

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 /PACG/ECM_USERMASTER. This should cause a generation of /PACG/ECM_ITYPE_SCALL_TASK idocs – one for each activity type set in transaction /PACG/ECM_SOLAF - Subtasks - Filter .

/PACG/ECM_SOLAF - Subtasks - Filter

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

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

4. Release assignment in FSM.

5. Go to the mobile app and create an effort for the activity assigned. Among other person-referring tasks, find the one related to the specific technician.

See other examples of time tasks creation and assignment:

‘Act. type as TT’ option set in transaction /PACG/ECM_SCTD, no settings in transaction /PACG/ECM_SCG:

Time tasks - standard approach

‘Act. type as TT’ option not set in transaction /PACG/ECM_SCTD, no settings in transaction /PACG/ECM_SCG:

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136054/PACG+ECM+SCTD+Service+Call+types+definition+Overview+and+Detail#%7C-_Ref36827017Example-5%3A-Act.-Type-as-TT-(checked-and-unchecked)

‘No time task’ option set in transaction /PACG/ECM_SCG:

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/72974378/PACG+ECM+SCG+-+Service+call+general+settings#No-time-task

  • No labels