/PACG/ECM_SCG - Service call general settings

No Scall task / OLD LABEL No time task	Do not generate time tasks for specific service calls. Activate this setting if time tasks should be generated for technicians and sent with technician master data (the option below - ‘task for technician’ is enabled).
Task for technician	If set, tasks are sent only once, with the user data (/PACG/ECM_USERMASTER – User), and they are assigned to a person. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/72974378/PACG+ECM+SCG+-+Service+call+general+settings#Task-for-technician
Send Equi	In the past the Equi&telo setting in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953646 handled this functionality. The new customizing has been separated and expanded. Customize what is sent as equipment in outbound service call idocs. Open Open No send – Do not send any equipment nor functional location within the outbound service call Equipment from Header (/Operation), 2nd Functional Loc. From Header (/Operation) – If equipment cannot be found, use functional location Learn more:   If ‘No send’ option is set for service calls in /PACG/ECM_SCG, the ‘+’ setting in the same transaction should be set to ‘No structure’. Otherwise header equipment structure will be still sent in outbound service call idocs.
Object Struct.	The field enables sending top-down structure of equipment, functional location or both (depending on the selected option) for objects found in the service order’s object list, header and related notification’s header. The structure is sent within outbound service call idocs (/PACG/ECM_ITYPE_SERVICECALL), as separate equipment segments.  Learn more:
(S4)PACG 200 SP05 Pl.Equip./FL	If marked, planning plant and planning group for service orders created from FSM will be determined from the service call’s equipment/functional location.         Otherwise, the default plant for object SERVICECALL will be used (see ).
(S4)PACG 200 SP12 Max.No.Equi/FL	Specify up to how many equipment/functional location objects within a structure can be sent together with service calls. This is particularly important when equipments are organized in hierarchies containing thousands of subobjects and the root node is sent to FSM. See also:

No time task

The side effects in FSM is that the table “TimeTask” will not have an entry for the said service call.

This will eventually cause the following list of effort types to be shown.  The multiple lines here actually refer to the service task per activity.  If SAP doesn’t send to FSM, FSM will take all other entries of other activity to be shown in the mobile.

In the windows app, this will be shown:

If the settings were made like below or no entries at all, then the message type /PACG/ECM_SERVICECALL_TASK will be sent.

As noted, the outbound messages in relation to the task below:

The data stored in FSM:

In mobile app, only two will be shown on the activity level per technician:                    

In the windows app, it will be shown as:

Task for technician

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 (depending on /PACG/ECM_SOLAF config it can be more) tasks are sent – 5 referring to the person, 5 referring to the service order.

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

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

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.

Send equipment structure within outbound service call idocs 

Set the ‘+’ setting in transaction /PACG/ECM_SCG to ‘1 Send Equipments’.

Add an equipment to the service order header.

Keep in mind its structure (can be checked in IE02):

Add another equipment, this time to the objects of the service order.

Keep in mind its structure as well:

Save the service order. The outbound service call idoc should contain additional equipment segments.

Apart from equipment entered in the service order header and object list, children equipments are sent – based on the top-down hierarchy of the two main equipments. The number of equipment segments corresponds to the number of all the relevant structure elements.

Send equipment within outbound service call idocs

Send equipment from service order header as service call equipment 

In transaction /PACG/ECM_SCG, set the ‘Send Equi’ field to ‘Equipment from Header’.

Create a service order with equipment assigned in its header.

After saving and releasing, the order header equipment can be found in a new /PACG/ECM_SERVICECALL idoc, segment ‘/PACG/ECM_IS_SERVICECALL2’ and field ‘EQUIPMENT’.

Send functional location from service order header as service call equipment

In transaction /PACG/ECM_SCG, set the ‘Send Equi’ field to ‘Functional Location from Header’.  

Create a service order with any functional location assigned in its header.

After saving and releasing, the order header functional location can be found in a new /PACG/ECM_SERVICECALL idoc, segment ‘/PACG/ECM_IS_SERVICECALL2’ and field ‘EQUIPMENT’. 

Do not send any equipment for service calls

In transaction /PACG/ECM_SCG, set the ‘Send Equi’ field to ‘No send’.  

Create a service order with any functional location or equipment assigned in its header. After saving and releasing, no ‘EQUIPMENT’ field can be found in a new /PACG/ECM_SERVICECALL idoc,  segment ‘/PACG/ECM_IS_SERVICECALL2’.