Maintenance steps to follow (/PACG/ECM_CL_PREF)

Use the latest available template version.

Table /PACG/ECM_ACTI, data of the activity to which the checklist instance refers to

Table EQUI, the related operation’s equipment

Table EQUZ, the related operation’s equipment

Table EQUI, service order’s header equipment

Table EQUZ, service order’s header equipment

Measuring points and documents of the operation’s equipment. If no equipment is found in the operation, equipment from the service order header is used.

Table IFLOT, the operation’s functional location

Table IFLOT, the service order header’s functional location

Table QMEL. the assigned quality notification

The assigned QM notification’s items

The assigned QM notification’s tasks

All partners of a notification (tables IHPA, KNA1, PA0001). The notification number is taken from /PACG/ECM_ACTI-QMNUM (the case when activities are created based on notification tasks) or if not found, from activity’s order’s header. This is a table structure, requiring mapping to table or series fields.

Data of a SHIP-TO partner of a notification (table KNA1). The notification number is taken from /PACG/ECM_ACTI-QMNUM (the case when activities are created based on notification tasks) or if not found, from activity’s order’s header.

Data of a SOLD-TO partner of a notification (table KNA1). The notification number is taken from /PACG/ECM_ACTI-QMNUM (the case when activities are created based on notification tasks) or if not found, from activity’s order’s header.

Data of a PERSON RESPONSIBLE partner of a notification (table PA001). The notification number is taken from /PACG/ECM_ACTI-QMNUM (the case when activities are created based on notification tasks) or if not found, from activity’s order’s header.

Service order components assigned to the specific operation

Service order object list

Service order operation related to the activity

Table AFIH, data of the related maintenance order’s header

Table AUFK, data of the related order’s header

All partners of the service order related to a given activity (tables IHPA, KNA1, PA0001). This is a table structure, requiring mapping to table or series fields.

Data of a SHIP-TO partner of the service order related to a given activity (table KNA1)

Data of a SOLD-TO partner of the service order related to a given activity (table KNA1)

Data of a PERSON RESPONSIBLE partner of the service order related to a given activity (table PA0001)

If checked, a checklist instance will be sent with the ‘Mandatory’ property set. The checklist will be mandatory to filled on the mobile app during service execution.

Allow generation of multiple checklist instances for one activity. If the flag is set, it will not be checked if the checklist was already generated for a given activity and a new one will be generated after each activity update. Otherwise, only one checklist instance will be created for one activity.

Generate a checklist instance only for the activity related to the first operation whose status is other than the one specified in this field. Only one checklist instance per service order can be generated. Leave this field empty, if checklist instances should be generated for all order operations' activities.

Example

Generate a checklist instance for the activity related to the first service order operation whose status is not 'Locked' (I0043).

Generate a checklist instance only for the activity related to the first operation. Only one checklist instance per service order can be generated.

If checked, the checklist instance will be generated only if there is at least one active measuring point defined for the equipment assigned to the header of the service order.

Specify where the checklist's language should be determined from.

• The first company language - determined from transaction /PACG/ECM_LANG - Language Definition

• Customer’s language - language of the customer added to the service order as partner role specified in field ‘Sold-to’ in transaction /PACG/ECM_SCTD

E.g. if in field ‘Sold-to’ value ‘SP’ is entered, the language of the customer added to the service order as partner function ‘Sold-to-party’ will be used

When activated, empty checklist instances would not be generated regardless of any other conditions

Reassign an existing checklist instance to a new technician after activity reassignment. If not enabled, new, duplicated checklist instances will be created after activity reassignment.

This setting must be used in combination with the Business Rule SAMPLE - Update responsible person of all checklists linked to an activity when releasing the activity to technician activated. 

When technicians are reassigned in SAP ECC/S4 (in service order), Business Rule Update responsible person of all checklists linked to an activity when changing technician on the SAP side (Extension of sample) must also be enabled, it can be downloaded below:

Open