...
...
...
...
...
...
...
...
...
...
...
| panelIconId | 1f3d7 |
|---|---|
| panelIcon | :construction_site: |
| panelIconText | 🏗️ |
| bgColor | #FFFAE6 |
...
WARNING: This page as well as the hereby described integration approach are under construction.
Standard service process description
...
...
A released service order is replicated into the FSM planning board
...
Using advanced scheduling the best matching technician(s) can be assigned to the service order
...
Releasing the assignment will push a notification to the technician’s mobile app
...
On the offline mobile app, the technician can confirm planned and unplanned effort, parts and expenses. The technician can also generate a PDF summary and capture the customer’s signature
...
FSM Cloud Connector is prepared for ID sharing with Service and Asset Manager - this accelerates the FSM planning to be consumed from SaAM mobile via SAP backend. Implementation of BadIs in customer system is required (with minimal efforts). Documented Support is limited currently for CS & PM orders, further integrations could derive adjusted logic
...
1:1 relationship of activities and operations
When FSM Cloud Connector is used in parallel with the Service & Asset Manager, the mobile integration logic of SAM must be followed. SAM uses the responsible person and dates from operations. Planning results in update of one operation per one activity. The scenario where multiple activities are assigned to a single operation cannot be supported by SAM.
Customizing prerequisites
The following customizing ensures correct 1:1 relationship of activities and operations:
Customizing transaction | Field | Required value |
|---|---|---|
Use req. ass. | disabled | |
MRS active | disabled | |
No new oper. | disabled | |
Act. operation | enabled | |
No technician | disabled |