Technicians can use prefilled checklists to collect measuring point readings during service execution. This data can then be used to automatically create measurement documents in SAP ECC/S4.
The following steps will help you set up an example process:
| Table of Contents |
|---|
Create a checklist template
The process setup should start with creation of a checklist template adjusted to measuring point processing. The template will serve the following purposes:
[SAP ECC/S4 → SAP FSM] It will be used to automatically generate a checklist instance for the technician - prefilled with equipment name, measuring point code, upper and lower limits and the value of the last reading. Learn more later on this page: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1598324737/Measuring+point+reading+using+checklist+instances#Configure-generation-of-prefilled-checklists
[SAP FSM → SAP ECC/S4] A technician will use the checklist instance to enter reading values for relevant measuring points.
The following template consists of two chapters. The first one serves the purpose of measuring point reading collection, the latter as a summary.
| Info |
|---|
It’s good practice to include field type in the field ID and use camel case, e.g. ‘TXT_MeasuringPoint'. |
Equipment
The ‘Equipment’ field is a picker field which points to the equipment for which measurement is performed. This field will be prefilled from SAP ECC/S4.
Equipment measuring point series/table
Since the structure used for mapping of measuring point data with checklist template fields in SAP ECC/S4(T_MEASURE_PTS)is a table structure, the corresponding fields in a checklist template must be part of a series or a table. The example series ‘Meter Reading’ consists of the following fields:
Field | Type | Prefilled from SAP ECC/S4 | Read-only |
|---|---|---|---|
Measuring point | Text input | X | X |
Obis Code | Text input | X | X |
Last Reading | Number input | X | X |
Meter Reading Result | Number input | ||
Lower Limit | Number input | X | X |
Upper Limit | Number input | X | X |
Download the example template
The following checklist template can be downloaded below:
| View file | ||
|---|---|---|
|
Configure generation of prefilled checklists
Checklists can be prefilled with measuring points data of the operation's equipment. If such equipment is , or if not found, the service order header’s equipment is used to retrieve measuring documents.
General overview
Transaction Use transaction /PACG/ECM_CL_PREF -Checklist prefilling configuration can be used to customize generation of prefilled checklists containing measuring points data of the operation or service order’s equipment.
Structure T_MEASURE_PTS can be is used to map selected measuring point properties data with checklist template fields:
The following measuring point data properties are supported by the standard solution and can be used in prefilled checklists without additional enhancements:
Measuring point and measuring position (obis code)
Upper and lower measurement range limits
Last measurement reading
Prerequisites
Apart from the prerequisites described on the following page: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1166737418/PACG+ECM+CL+PREF+-+Checklist+prefilling+configuration#Preconditions, it is crucial that the activity’s operation has equipment assigned (if not found, equipment is searched on the service order header level). Measuring documents should be maintained for this equipment. Please remember that prefilled checklists will be generated only for activities with a technician assigned.
Another equipment determination source
If equipment ought to be determined differently, please implement the following BAdI:
enhancement spot /PACG/ECM_CHKL_PREFILLER → BAdI definition /PACG/ECM_FILL_COMM_STR_ACT_EQ, method GET_EQUIPMENT:
Example prefilled checklist
template mapping The FSM checklist template fields should be mapped with relevant fields of structure T_MEASURE_PTSinstance
For the example checklist template, the following mapping is maintained in transaction /PACG/ECM_CL_PREF - Checklist prefilling configuration. An example mapping :
The following checklist instance was generated for an activity whose service order’s checklist template has conditions assigned and is set as active for prefilled checklist generation:
Create a service order. Its operation should have a technician and equipment assigned. The operation’s equipment contains 4 measuring points, each one is represented as a series in the prefilled checklist instance:
The measuring point data from SAP ECC/S4 is reflected in the checklist instance in SAP FSM, based on the maintained mapping:
