Here you have to define how SAP should proceed with Checklists and Reporting. The Checklist and Report handling in the App itself is not affected by these settings.
-
A-L
-
M-Q
-
R-T
-
U-Z
-
0-9
- checklists
- upd_4_2202
- tilelinkwidget
- teams
- time_effort
- crowd
- project_network_order
- reserved_material
- time_tasks
- msgbroker30
- regions
- countlinkwidget
- person_reservation
- tools
- customrazorview
- gridlist
- msgbroker
- sap_notes
- project_wbs
- upd_4_2108
- equipment
- msgbroker3x
- organization
- work_time
- work_in_progress
- contact_person
- gos
- service_pack
- time_zone
- udf
- 2111
- 2202
- 4-ls-retrospective
- activate_deactivate_bp
- announcementtilelinkwidget
- attachments
- automated_data_deletion
- badi
- bp_api_vss
- bp_groups
- btp
- business_partner
- business_partner_audit
- create_business_partner
- dashboards
- driver_sponsor
- duplication_check
- enterprise_search
- fullgridlist
- is-u
- msgbroker20
- msgbroker4x
- office_365_add_in
- overview_retail_process
- quick_search
- service_workflow
- sticky_menu
- vehicle_features
- vehicle_photos
- vehicle_print_out
- vehicle_reservation
- work-pattern
- work_pattern
-
Service order statuses for checklists (FSM Cloud Connector) —
/PACG/ECM_CLSSC - Checklist: User Status for Order - If specified field of a checklist identified by template’s Id and version contains a value that meets defined conditions the specified status is set in the header of related service order. The point is that right now it is possible to define set of conditions (all of them must be met - logical conjunction) and furthermore they can be defined as range.
-
Unfinished checklist explanation visible in SAP (FSM Cloud Connector) —
General concept of the FSM feature
When a technician closes a checklist leaving obligatory fields empty, an explanation must be added.
FSM Cloud Connector features
-
Notification tasks parameters for checklists (FSM Cloud Connector) —
Transaction /PACG/ECM_CLCTN - Notification tasks parameters for checklist implements a new inbound processing logic for checklists. It is possible to maintain notifications’ tasks depending on the checklists’ values. The solution is analogical to other customisings so basicaly a content of specified checklist’s element identified by the template’s Id and version is compared to a value defined in the configutaion table and if the condition is met a notification and its tasks can be managed. Possible actions include: notifcation closing, notification tasks creation or deletion. If the notification does not exist it is created and linked to related service order.
-
-
/PACG/ECM_CHECKL_MON - Checklists Monitoring (FSM Cloud Connector) —
(S4)PACG 200 SP 08 The transaction requires authorization object /PACG/E009.
This is used to monitor the inbound checklist with detail information and status regarding the related service call/order.
Learn more about checklists: Checklists
-
/PACG/ECM_CHECKL_SHW - Checklists Display (FSM Cloud Connector) —
(S4)PACG 200 SP 08 The transaction requires authorization object /PACG/E009.
Up to 50 fields are displayed.
This is a report showing the content of the submitted checklist from FSM into SAP ERP backend. The information shows the content of the checklist and the relationship to the related activity number (indicated by the "Reference Object" column).
-
/PACG/ECM_CLCTN - Notification tasks parameters for checklist (FSM Cloud Connector) —
A new transaction has been created based on the one described on this page - /PACG/ECM_NOTIF - Notification Configuration for Checklist. The purpose of this redesign was to enhance user experience by creating a view cluster and refining condition creation. To avoid data duplication, please make sure to maintain data in only one of the mentioned transactions.
-
Creating Checklists in SAP (FSM Cloud Connector) —
In the typical scenario the checklists are created in the Cloud and sent back to SAP. In the SAP they can be mainly read, some additional activities could be performed as well once the checklist is created in SAP.
However, the opposite scenario is possible as well:The checklist is created in SAP.
-
/PACG/ECM_VCLCNY - Checklists mapping customizing (FSM Cloud Connector) —
The hereby described transaction requires additional customer development. Basic checklist instances can be easily created without additional development using the new transaction /PACG/ECM_CL_PREF - Checklist prefilling configuration. It is recommended to use the new transaction whenever possible.
-
/PACG/ECM_CLGRW - Goods receipt - Storage locations (FSM Cloud Connector) —
This is used to define default plant and storage location per company ID for goods receipt.
-
/PACG/ECM_CLGR - Goods receipt - General settings (FSM Cloud Connector) —
This is used to define the goods receipt based on purchase order identified per company ID.
-
/PACG/ECM_CLASS - Checklist Assignment (FSM Cloud Connector) —
Prefilled or empty checklist instances can be properly generated (automatically) with /PACG/ECM_CL_PREF - Checklist prefilling configuration, it’s recommended to use that transaction instead.
This table is automatically pre-filled by the connector per activity that have been assigned to a checklist.
-
/PACG/ECM_VCLCNX – Checklists’ assignment conditions (FSM Cloud Connector) —
Prefilled or empty checklist instances can be properly generated (automatically) with /PACG/ECM_CL_PREF - Checklist prefilling configuration, it’s recommended to use that transaction instead.
Create automatic checklist assignments for activities created in SAP ECC/S4, based on the specified conditions. Object ChecklistAssignment is created in SAP FSM.
-
/PACG/ECM_CLEPV - Create Pur. Order out of Checklist (FSM Cloud Connector) —
From the entered checklist a transfer purchase order can be created
SLocation Pos. – The storage location is found in this position of the checklist
-
/PACG/ECM_CLESV - Create Sales Order out of Checklist (FSM Cloud Connector) —
From the entered checklist a customer order can be created
Contact Pos. – Contact partner is found in this position of the checklist