This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps for actions performed during activity execution on the FSM mobile app:
| Table of Contents |
|---|
For more detailed descriptions, navigate to links included in each step.
Time reporting
Time efforts reported on the FSM mobile app are reflected in SAP ECC/S4 as CATS entries or order confirmations, depending on customizing.
Configuration Step | Customizing transaction | Corresponding sending transaction |
Specify whether time efforts/work time reported in FSM should be stored as CATS entries or order confirmations. Specify the entry profile and how cost center should be determined. This customizing transaction is relevant for both time efforts and work times. | ||
During inbound time effort processing, time records for confirmation and CATS can be optionally split into two and more postings, each with different activity type and attendance/absence type. | /PACG/ECM_CSPLIT - Time Effort - Time Frames for Activity Type (additionally it must be enabled in transaction |
, field ‘Split conf’ |
Time efforts are reported together with so-called time tasks, which contain information about SAP activity type. Time tasks can be created individually for each service order or once per each technician (recommended).
| /PACG/ECM_SCG - Service call general settings , fields ‘No time task’/
| ||||||||||||||||
Specify activity types relevant for time task generation | |||||||||||||||||
Customize how work time reported in SAP FSM should be processed in SAP ECC/S4, depending on the selected work time task. For work times stored as CATS, specify the activity type and attendance/absence type. Work times can be also posted with reference to orders or WBS elements.
| /PACG/ECM_WRKTTSND - Work Time Task |
Material consumption
Materials consumed on the FSM mobile app are reflected in SAP ECC/S4 as goods movements. Consumption of serialized materials can optionally trigger equipment structure update.
Configuration Step | Customizing transaction |
Make sure that relevant technicians are added as owners to their van stocks/central stock. It’s necessary to consume unplanned materials or take reserved materials to own stock. | /PACG/ECM_WRHSE - FSM warehouse & additional owners, tab ‘Additional owners’ | ||||||||||||
Specify which movement types should be performed for material consumption/stock transfer carried out on the FSM mobile app, depending on a reserved material scenario. | |||||||||||||
During reserved material consumption, a technician can be prompted to enter additional information, such as filling UDFs. This can be enabled for serialized, batch-managed, all or none materials of a given type. | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953976/PACG+ECM+ITYPE+Material+Group+and+Company+assignment-! , field ‘RM TrP’
| ||||||||||||
When consuming a serialized part (a serialized item representing an equipment), it can be installed in equipment structure or replace another equipment (trigger dismantle of an existing part).
| https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953999/PACG+ECM+ICONF+-+Item+Configuration-! , fields ‘UDF Equi Ins./Unins.’, ‘Forced Update’ | ||||||||||||
Specify which user status should be set to an order if a material consumption fails and is put to COGI |
, field ‘SO |
...
User Status for failed GM’ |
Expenses
Expenses reported on the FSM mobile app are reflected in SAP ECC/S4 as Manual Cost Allocation documents, FI documents or travel expense receipts, depending on customizing.
Configuration Step | Customizing transaction | Corresponding sending transaction | |||||||||||
Specify whether expenses reported in SAP FSM should be posted to controlling (KB21N), finance (FB01) or travel/trip. Specify further posting properties, such as activity type or cost element.
| /PACG/ECM_EXPENSESND - Expense Type | ||||||||||||
Specify currencies allowed in a given company. Relevant for expense reporting in SAP FSM. | /PACG/ECM_TRIG_ACUR – Currency | ||||||||||||
Specify if customers should be transferred to FSM with their default currency. As a consequence, only the currency assigned to the customer used in the activity will be allowed in the expense. | /PACG/ECM_CCUST - General customizing for Customer , field ‘No currency’ |
Mileage
Mileages reported on the FSM mobile app can be reflected in SAP ECC/S4 as Direct Activity Allocation documents (for distance posting), CATS/order confirmations (for travel time posting) and additional expenses (lumpsums).
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Learn more about the overall mileage processing: Mileage |
Configuration Step | Customizing transaction | Corresponding sending transaction |
Define how the posting date for mileage-related CO-documents is determined, if CATS entry should be created and if posting CO documents for mileages with empty distance should be skipped. | ||
Determine values used for activity allocation document posting for recorded mileages. Optionally, a fixed mileage expense value can be customized. | ||
Specify which mileage UDF should be treated as source of the mileage type. It is then used in the customizing above, as an additional customizing entry selection criterium. | /PACG/ECM_TRIG_UDF - UDF Definition | |
Specify language-dependent descriptions of the driving route labels which are used in cost document description (the ‘Doc. text’ field in Direct Activity Allocations). | ||
After recording a mileage on the SAP FSM mobile app, apart from a cost document (direct activity allocation) and a CATS entry, an expense can be posted. Its amount will be calculated based on the specified rate. |
Feedback codes
Feedback codes reported on the FSM mobile app are reflected in SAP ECC/S4 as updates in the activity’s order’s notification.
Configuration Step | Customizing transaction | Corresponding sending transaction |
Specify notification code groups which can be used for activity feedback reporting | /PACG/ECM_TRIG_SERCD - Activity Codes from SAP Inspection Catalog Codes | |
Specify which notification fields should be updated after activity feedback reporting on the mobile app | /PACG/ECM_SERFP - Notification update rules for activity feedback | |
Specify if activity feedback codes should be sent to FSM without groups, to reduce the number of necessary clicks. |
Checklists
Checklist reported on the FSM mobile app can trigger user status/notification update or notification/sales order/purchase order generation. The data from checklists is often used for custom actions implementations.
Configuration Step | Customizing transaction |
Corresponding sending transaction
Checklist instances created in SAP FSM can be viewed in SAP ECC/S4 using the checklist display transaction: /PACG/ECM_CHECKL_SHW - Checklists Display. To make checklists visible from transaction IW32/IW33, GOS menu should be updated.
| SM30, table SGOSATTR | |||||||||||
Checklists created in SAP FSM can update service order user status, if the specified conditions are met. | ||||||||||||
Manage notifications and notification tasks based on checklist instance values. | ||||||||||||
Checklists created in SAP FSM can trigger email sending, with a specified content and based on specified conditions. | ||||||||||||
Checklists created in SAP FSM can trigger generation of a service notification in SAP ECC/S4 | ||||||||||||
Checklists created in SAP FSM can trigger generation of a sales order in SAP ECC/S4 | ||||||||||||
Checklists created in SAP FSM can trigger generation of a purchase order in SAP ECC/S4 |
Checkout
Checkout reported on the FSM mobile app can trigger final confirmation and debit memo request creation in SAP ECC/S4.
Configuration Step | Customizing transaction |
Corresponding sending transaction
Specify if automatic billing/debit memo request should be created after checkout. Check if unprocessed idocs exist for a service order before proceeding with final confirmation for operations. |
, fields ‘Create a debit memo req. after checkout’, ‘Check IDOCs’ | |
Optionally review failed service call/activity idocs directly from GOS menu | SM30, table SGOSATTR, learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136054#(s4)PACG200-SP05-Unproc.Idoc-Stat--%5BhardBreak%5D(User-Status-for-Unprocessed-Idocs). See also other FSM Cloud Connector-related GOS options. |
Map the rating levels from SAP FSM with own values |
Explore!
Once you’ve gone through all the aforementioned customizing steps, you can explore other processes supported by FSM Cloud Connector! Continue your journey with Customizing Guides and Processes Overview. If you prefer to explore customizing transactions one by one, navigate to Application Help.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Next chapter: Custom enhancements |