Send Master Data
Expense Type
Related transaction code(s):
/DBE/FSM_TRIG_M_EXPT - Expense Type”
Business context
Different kinds of expenses in the course of the technician’s work are claimable.
Functionality
To support different expense types, master data for different expense types are set.
Using the transaction /DBE/FSM_TRIG_M_EXPT, we trigger the sending of the expense type to SAP FSM.
Selection area | Field | Description |
User Selection | FSM Company ID | FSM Cloud Company ID |
Expense code | Expense type code. Leave blank if need to send all expense type. | |
Program Parameters | Save Log | Save log. Check log in SLG1. |
Display Log | Default checked to show completion status. | |
Delete Flag | Unchecked by default. This will send a deletion request to SAP FSM for record deletion. |
The list of the expense code is visible in the FSM Windows Mobile client (example) like below. Same list will appear for Android/iOS FSM app.
Service Call Status
Related transaction code(s):
/DBE/FSM_TRIG_M_SCCS - Service Call Status”
Business context
Service call status of SAP FSM.
Functionality
Sending of service call status to SAP FSM. The mapping is configured in menu path “SPRO->Logistics Execution->Vehicle Sales and Service->VSS-FSM Integration->VSS Order (FSM Service Call)->Status of Service Call - FSM Cloud”.
Selection area | Field | Description |
User Selection | FSM Company ID | FSM Cloud Company ID |
Program Parameters | Save Log | Save log. Check log in SLG1. |
Display Log | Default checked to show completion status. | |
Delete Flag | Unchecked by default. This will send a deletion request to SAP FSM for record deletion. |
Note: Service call status for SAP FSM is limited, hence you only see status -1, 0, 1 here. These are mapped towards the SAP VSS order header status in configuration menu path “SPRO->Logistics Execution->Vehicle Sales and Service->VSS-FSM Integration->VSS Order (FSM Service Call)->Status of Service Call”.
This status code (name) is shown in the service call header level. Example like below for status “Released” in SAP FSM Workforce Management (WFM).
In the SAP FSM backend, the status code number is shown below.
Note: This transaction supports deletion requests from SAP VSS to SAP FSM. Default the checkbox “Delete flag” is not checked. If need to use this, be very certain that you don’t create data inconsistency between SAP VSS and SAP FSM.
Service Call Type
Related transaction code(s):
/DBE/FSM_TRIG_M_SCTD - Service Call Type”
Business context
Valid service call type for field service use. This is to differentiate between workshop service order, sales order, etc. compared to the field service order type.
Functionality
This is used to send the valid service call type to FSM. The service call type is maintained in configuration section menu path “SPRO->Logistics Execution->Vehicle Sales and Service->VSS-FSM Integration->VSS Order (FSM Service Call)->Type of Service Call”.
Selection area | Field | Description |
User Selection | FSM Company ID | FSM Cloud Company ID |
Expense code | Expense type code. Leave blank if need to send all expense type. | |
Program Parameters | Save Log | Save log. Check log in SLG1. |
Display Log | Default checked to show completion status. | |
Delete Flag | Unchecked by default. This will send a deletion request to SAP FSM for record deletion. |
On executing the transaction above, it will trigger an outbound IDoc for service call type like below.
As you can see when creating a service call directly from SAP FSM, the mobile service call type is shown after sending.
Note: This transaction supports deletion requests from SAP VSS to SAP FSM. Default the checkbox “Delete flag” is not checked. If need to use this, be very certain that you don’t create data inconsistency between SAP VSS and SAP FSM.
Service Call Problem Type
Related transaction code(s):
/DBE/FSM_TRIG_M_SCPT - Service Call Problem Type”
Business context
For later analytical purposes or use for creating credit/debit memo, the order reason for SAP VSS order could be recorded within it.
Functionality
SAP VSS order reason can be entered when creating the order from VSS backend or from FSM side. This order reason is named differently as “Problem Type” in SAP FSM but it is the same field.
The list in SAP VSS order reason is comprehensive, but there may be a need to limit the reason visible/usable for the technician side using SAP FSM. The “Order Reason” to send to SAP FSM as “Problem Type” is controlled in “SPRO->Logistics Execution->Vehicle Sales and Service->VSS-FSM Integration->VSS Order (FSM Service Call)->Problem Type”
Executing the transaction /DBE/FSM_TRIG_M_SCPT is shown below.
Selection area | Field | Description |
User Selection | FSM Company ID | FSM Cloud Company ID |
Program Parameters | Save Log | Save log. Check log in SLG1. |
Display Log | Default checked to show completion status. | |
Delete Flag | Unchecked by default. This will send a deletion request to SAP FSM for record deletion. |
The outbound IDoc for service call problem type is triggered upon successful transaction run from above.
The service call problem type field only exists in the service call header. As shown below in the service call header, there is the field “Problem Type” with the list that was sent from SAP VSS.
Work Time Task
Related transaction code(s):
/DBE/FSM_TRIG_M_WKTS - Work Time Task”
Business context
This is to send the required work time task in master data to FSM Cloud.
Functionality
Master data created in “/DBE/FSM_LCM_TSP - Time Split determination” (in criteria table /DBE/FSM_TSP04) is sent by the transaction here. Deletion can also be sent from this same transaction. This will cause the automatic deletion from FSM cloud.
Selection area | Field | Description |
User Selection | FSM Company ID | FSM Cloud Company ID |
Work Time Task | Work time task to send to SAP FSM. | |
Program Parameters | Save Log | Save log. Check log in SLG1. |
Display Log | Default checked to show completion status. | |
Delete Flag | Unchecked by default. This will send a deletion request to SAP FSM for record deletion. |
Note: This transaction supports deletion requests from SAP VSS to SAP FSM. Default the checkbox “Delete flag” is not checked. If need to use this, be very certain that you don’t create data inconsistency between SAP VSS and SAP FSM.
The outbound IDoc for work time task is triggered upon successful transaction run from above.
The list of work time task from the defined master data is sent to FSM Cloud and below shows the list.
Note: “Presence” is a standard item within FSM Cloud and not sent from backend VSS. Please refer to SAP FSM manual / guide for more information on this “Presence”.