Mileage
Business context
The travel cost of the technician to the customer repair site needs to be recorded by the technician. Submission of distance (mileage) and duration of travel is required by the technician.
Functionality
Within FSM, the standard T&M submission supports mileage entry for both the distance and duration. This is recorded as one single transfer per submission of mileage to the SAP VSS backend. SAP VSS-FSM connector will perform the split of the travel duration and distance as separate item position within the order. Example below shows an entry for a mileage entry from SAP FSM windows mobile client.
From here, an inbound IDoc for mileage is triggered from SAP FSM to SAP VSS.
The following information master data is read to create item positions within the SAP VSS order.
Item position for travel duration picks up the material number from “/DBE/FSM_MIMA - General Master Data”
Note: Material number used here is type DIEN (Service).
For mileage object, the activity type to be used are found in “/DBE/FSM_LCM_TSP - Time Split determination” under criteria table /DBE/FSM_TSP03.
For the labour number (LV) to use for creating the item position of mileage travel duration, we look at “/DBE/FSM_LCM_LVA - Labor Value determination (Travel Time)” under the criteria table “/DBE/FSM_LVA03” where the default LV no. to use is ‘900001’
Next, to find the item category for creating the item position from “/DBE/FSM_LCM_LVI - Item Category determination (Travel Time)” under the table “/DBE/FSM_LV2”.
Finally, as can be seen in the SAP VSS order itself, two(2) item position was created for travel duration and travel distance.
