| Status | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
Introduction
The aim of this transaction:
Automatically generate prefilled checklist instances.
The instances will be filled with data retrieved from SAP ECC/S4 tables, based on configurable mapping.
Build a set of rules based on which a checklist instance will be assigned to an activity.
Preconditions
To trigger generation of a checklist instance referring to an activity, the following criteria should be met:
The activity has status ‘OPEN’
The activity has a technician assigned
The conditions specified in the view cluster are met
Maintenance steps to follow
Step 1. - Maintain mapping between checklist instance fields and SAP tables fields
Step 1.1. - Select a company ID and enter the ID of the template relevant for mapping.
Enter a specific template version or activate the ‘Latest template’ option.
...
Latest Template
...
Use the latest available template version.
| Info |
|---|
If you leave the template version empty, then this flag will be automatically checked. |
Step 1.2. - For all relevant checklist template fields, specify a corresponding structure (which reflects SAP tables) and the structure’s field.
Mapping between checklist instance fields and SAP ECC/S4 tables data can be maintained using the following provided structures:
Activity-related
...
S_E4C_ACTI
Table /PACG/ECM_ACTI, data of the activity to which the checklist instance refers to
...
| title | Extend the list of the available SAP ECC/S4 fields and their data types |
|---|
...
Field
...
Component type
...
Data type
...
Length
...
Description
...
MANDT
...
MANDT
...
CLNT
...
3
...
Client
...
ACTNR
...
/PACG/ECM_ACTNR
...
CHAR
...
10
...
E4C Activity number
...
VKORG
...
VKORG
...
CHAR
...
4
...
Sales Organization
...
VTWEG
...
VTWEG
...
CHAR
...
2
...
Distribution Channel
...
SPART
...
SPART
...
CHAR
...
2
...
Division
...
VKBUR
...
VKBUR
...
CHAR
...
4
...
Sales Office
...
ACTI_TYPE
...
/PACG/ECM_ACTI_TYPE
...
CHAR
...
4
...
Activity type
...
ACTI_STATUS
...
/PACG/ECM_ACTI_STATUS
...
CHAR
...
1
...
Activity status
...
KUNNR
...
KUNNR
...
CHAR
...
10
...
Customer Number 1
...
KUNWE
...
/PACG/ECM_KUNWE
...
CHAR
...
10
...
Ship-to party
...
CONTACT
...
PARNR
...
NUMC
...
10
...
Number of contact person
...
PERNR
...
PERNR_D
...
NUMC
...
8
...
Personnel Number
...
ACTI_TOPIC
...
/PACG/ECM_ACTI_TOPIC
...
CHAR
...
4
...
Activity topic
...
SUBJECT
...
/PACG/ECM_ACTI_SUBJECT
...
CHAR
...
255
...
Subject
...
TECHNICIAN
...
/PACG/ECM_ACTI_TECHNICIAN
...
CHAR
...
32
...
Technician
...
ADDRESS
...
/PACG/ECM_ADDR_OBJKEY
...
CHAR
...
30
...
Address - Object Key
...
PREV_ACTNR
...
/PACG/ECM_REF_ACTNR
...
CHAR
...
10
...
E4C Reference Activity Number
...
SOURCE_ACTNR
...
/PACG/ECM_SOURCE_ACTNR
...
CHAR
...
10
...
E4C Source Activity Number
...
ACTI_START_DATE
...
/PACG/ECM_ACTI_START_DATE
...
DATS
...
8
...
Activity start date
...
ACTI_START_TIME
...
/PACG/ECM_ACTI_START_TIME
...
TIMS
...
6
...
Activity start time
...
ACTI_END_DATE
...
/PACG/ECM_ACTI_END_DATE
...
DATS
...
8
...
Activity end date
...
ACTI_END_TIME
...
/PACG/ECM_ACTI_END_TIME
...
TIMS
...
6
...
Activity end time
...
DURATION
...
/PACG/ECM_DURATION
...
INT4
...
10
...
Duration in minutes
...
PLANNEDDURATION
...
/PACG/ECM_PLANNEDDURATION
...
INT4
...
10
...
Planned duration in minutes
...
ACTI_REM_DATE
...
/PACG/ECM_ACTI_REM_DATE
...
DATS
...
8
...
Activity remainder date
...
ACTI_REM_TIME
...
/PACG/ECM_REM_TIME
...
TIMS
...
6
...
Activity remainder time
...
ACTI_CHECKEDOUT
...
/PACG/ECM_ACTI_CHECKEDOUT
...
CHAR
...
1
...
Activity checked out
...
COMPID
...
/PACG/ECM_COMPID
...
NUMC
...
4
...
E4C Company ID
...
SERVICE_RATING
...
/PACG/ECM_SERVICE_RATING
...
CHAR
...
2
...
Service Rating
...
SCOPE
...
/PACG/ECM_FSM_SCOPE
...
CHAR
...
255
...
FSM Scope
...
AUFNR
...
AUFNR
...
CHAR
...
12
...
Order Number
...
VORNR
...
VORNR
...
CHAR
...
4
...
Operation/Activity Number
...
UVORN
...
UVORN
...
CHAR
...
4
...
Suboperation
...
SPLIT
...
CY_SPLIT
...
INT1
...
3
...
Split number
...
QMNUM
...
QMNUM
...
CHAR
...
12
...
Notification No
...
MANUM
...
MANUM
...
NUMC
...
4
...
Sequential Task Number
...
EQUNR
...
EQUNR
...
CHAR
...
18
...
Equipment Number
...
TPLNR
...
TPLNR
...
CHAR
...
30
...
Functional Location
...
TEAM_ID
...
/PACG/ECM_TEAM_ID
...
CHAR
...
128
...
Team Id
...
TIMEZONEID
...
/PACG/ECM_TIMEZONEID
...
CHAR
...
50
...
Time Zone
...
EXECSTAGE
...
/PACG/ECM_FSM_EXECSTAGE
...
CHAR
...
30
...
FSM Exceution stage
...
REGION
...
/PACG/ECM_REGION_ID
...
CHAR
...
128
...
Region Id
...
TRAVELTIMETO
...
/PACG/ECM_ACTI_TRAVELTIME_TO
...
INT4
...
10
...
Travel time (in minutes) to the customer site.
...
TRAVELTIMEFROM
...
/PACG/ECM_ACTI_TRAVELTIME_FROM
...
INT4
...
10
...
Travel time (in minutes) from the customer site.
...
HAZARDTYPE
...
/PACG/ECM_ACTI_HAZARDTYPE
...
CHAR
...
8
...
Hazard type
...
OBJ_REF_TYPE
...
/PACG/ECM_CLOUDMESSAGE
...
CHAR
...
40
...
Cloud message type
...
OBJKEY
...
/PACG/ECM_OBJECTKEY
...
CHAR
...
128
...
Object key
...
RELEAS_UDF_SEND
...
/PACG/ECM_RELEAS_UDF_SEND
...
CHAR
...
1
...
Release UDF was sent (or not)
...
PD_TYPE
...
/PACG/ECM_PLANNED_DURATION_TYP
...
CHAR
...
1
...
Planned duration type
...
ERDAT
...
ERDAT
...
DATS
...
8
...
Date on Which Record Was Created
...
ERZET
...
ERZET
...
TIMS
...
6
...
Entry time
...
ERNAM
...
ERNAM
...
CHAR
...
12
...
Name of Person who Created the Object
...
AEDAT
...
AEDAT
...
DATS
...
8
...
Changed On
...
AEZET
...
AEZET
...
TIMS
...
6
...
Time last change was made
...
AENAM
...
AENAM
...
CHAR
...
12
...
Name of Person Who Changed Object
...
LOEKZ
...
/PACG/ECM_LOEKZ
...
CHAR
...
1
...
Marked for deletion
...
CLOUD_CREATED
...
/PACG/ECM_CLD_CREAT
...
CHAR
...
1
...
Activity created from CloudApp
...
CHANGEDBYSAP
...
/PACG/ECM_ACT_CHANGED_BY_SAP
...
CHAR
...
1
...
Activity dates were changed by SAP
...
DUMMY
...
CHAR1
...
CHAR
...
1
...
Single-Character Indicator
Equipment-related
...
S_EQ_OPER_EQUI
...
Table EQUI, the related operation’s equipment
...
S_EQ_OPER_EQUZ
...
Table EQUZ, the related operation’s equipment
...
S_EQ_SCALL_EQUI
...
Table EQUI, service order’s header equipment
...
S_EQ_SCALL_EQUZ
...
Table EQUZ, service order’s header equipment
...
T_MEASURE_PTS
...
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.
| Info |
|---|
Equipment determination procedure can be overwritten by implementing BAdI /PACG/ECM_FILL_COMM_STR_ACT_EQ. |
Functional location-related
...
S_FL_OPER_IFLOTi
...
Table IFLOT, the operation’s functional location
...
S_FL_SCALL_IFLOT
...
Table IFLOT, the service order header’s functional location
Quality Notification-related
...
S_NOTIF_QMEL
...
Table QMEL. the assigned quality notification
...
T_NOTIF_ITEMS
...
The assigned QM notification’s items
...
T_NOTIF_TASK
...
The assigned QM notification’s tasks
Service/Maintenance order-related
...
T_SCALL_COMPONENTS
...
Service order components assigned to the specific operation
...
T_SCALL_OBJLIST
...
Service order object list
...
S_SCALL_OPERATION
...
Service order operation related to the activity
...
S_SCALL_AFIH
...
Table AFIH, data of the related maintenance order’s header
...
S_SCALL_AUFK
...
Table AUFK, data of the related order’s header
Object Picker
Object Picker fields can also be pre-filled in SAP ECC/S4. Information about relevant Object Type (e.g. Equipment, Business Partner) is retrieved automatically based on inbound checklist template data.
| Note |
|---|
Keep in mind that information about Object Picker’s reference object is stored in SAP ECC/S4 starting from Service Pack 2 for Add-on 200. Checklist templates created before installation of this Service Pack should be resent from SAP FSM to SAP ECC/S4. Moreover, please note that the field mapping should point to a table value which was sent to SAP FSM as the key of a given object, e.g. pointing to value ‘CHY' or ‘Jake Austin’ for a Person Object Picker will not work properly on the mobile app, ‘U/CHY’ should be used instead. |
Additional mapping remarks
All structures and their fields (including technical details) can be viewed in structure /PACG/ECM_STR_CHKL_COMM.
Checklist template fields of type ‘long text’ (text input with multiple lines) should be mapped only with structure fields of type TLINE_TAB.
Table types in SAP should be mapped as checklist series or tables.
Step 2. - Maintain at least one condition
Step 2.1. - Enter the condition’s name and description.
The conditions contain circumstances in which a checklist instance should be generated.
...
Step 2.2. - Maintain condition criteria
An example condition - checklist instances will be generated only if the activity’s service order’s plant number is between 1000 and 1200.
...
| Info |
|---|
If no specific conditions are required, maintain only a generic condition name and description, without maintaining the sub-nodes. In such a case checklist instances will always be generated if technical conditions in node ‘Technical condition assignment’ are met. |
Step 3. - Assign the conditions to the mapped checklist templates. Configure additional assignment options.
Step 3.1. - Enter the mapped template’s ID in the ‘Conditions assignment’ node.
Create a new entry with the mapped template’s ID. Mapped templates will be displayed on the search help list.
...
Step 3.2. - Specify additional technical assignment conditions
Click on the template ID entry and navigate to node ‘Technical condition assignment’. Enter the condition’s name (already created in the ‘Conditions list’). Make sure to check it as ‘active’. Only active entries will be used during checklist instance generation processing.
...
Other available options include:
...
Mandatory
...
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 Duplication
...
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.
...
Exclude status
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).
...
1st operation only
...
Generate a checklist instance only for the activity related to the first operation. Only one checklist instance per service order can be generated.
...
Measuring Point on
...
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.
...
Language source
...
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
...
| Info |
|---|
The customer’s language should also be maintained in transaction /PACG/ECM_LANG. If no customer language is found, the first company language will be used. |
Step 4. - Optionally maintain additional mapping configurations
Optionally, additional mapping configuration can be specified for each mapped field. Start by entering a mapping configuration name in node ‘Additional mapping config’. After saving, it will be available in node ‘Additional fields mapping’, field ‘AddMap’. FSM Cloud Connector doesn’t provide specific implementations (nor BAdI definitions), the additional mapping logic should be implemented locally by the Customer. Depending on an implementation, the mapping key and mapping value fields should be filled.
Example usage: mapping between checklist template drop-down fields and SAP notification fields (for the first drop-down value ['1' in additional mapping key], use the value from [additional mapping value]).
Extension possibilities
Currently, the following BAdI definitions are provided (enhancement spot /PACG/ECM_CHKL_PREFILLER):
/PACG/ECM_CHKL_TO_GEN_LOOP - perform additional validation actions in generation loop
/PACG/ECM_FILL_COMM_STRUCT - fill communication structure with custom data
/PACG/ECM_FILL_COMM_STR_ACT_EQ - determine equipment used for measuring points/documents retrieval
Add a custom communication structure
To add your own communication structure, the following steps should be performed:
1. Add a new component to structure /PACG/ECM_STR_CHKL_COMM:
...
After this action the new structure will be visible in the configuration’s search helps.
2. Implement BAdI /PACG/ECM_FILL_COMM_STRUCT. The implementation should contain database retrieval logic - based on which SAP tables and fields the structure should be filled.
...
Learn more about setup steps of the prefilled checklist customizing transaction: Maintenance steps to follow (/PACG/ECM_CL_PREF)