Time effort

Business context

The work time effort of the technician on field service needs to be recorded as part of the service/repair cost of labour.

Open

Figure 56 Typical process for time effort submission from FSM to SAP VSS order

Functionality

Submission of technician time effort (work hours) from SAP FSM to create item position within SAP VSS order.  As time effort charges could be based on duration of work or based on time of the day/night, lean condition management in SAP VSS-FSM connector supports the correct posting of time effort per technician.

Example 1 of 2 (Duration based split)

In this first example, we have 10 hours worked by the technician.

Open

Figure 57 Time effort submission by technician from SAP FSM Windows mobile client

On submission of the time effort from SAP FSM, we have the following inbound IDoc from SAP FSM.

Note: Technician is located in UTC+8 and time recording from the cloud is using UTC, hence ‘Z’ at the end of the time.  CATS timesheet entry will be adjusted according to the geographical time zone.

To create the item position the program needs to know first, the item category for the activity type for labour.  It gets it from the lean table condition “/DBE/FSM_LVI2” from transaction “/DBE/FSM_LCM_LVI - Item category determination” like as shown below.

Then, the program needs to check in lean conditions “/DBE/FSM_LVA04” or “/DBE/FSM_LVA03” (in our example) from transaction “/DBE/FSM_LCM_LVA - Labor value determination” for the correct LV No. to use when creating the item position for labour.

Next, the splitting condition matches, then the split will be done according to the lean condition stipulated below from transaction “/DBE/FSM_LCM_TSP - Time Split determination”.

Note: Lean condition (criteria tables) that are logically valid for labour are “/DBE/FSM_TSP01”, “/DBE/FSM_TSP02” and “/DBE/FSM_TSP99”.

Below is the final result of the example for time effort submission for 10 hours.

Example 2 of 2 (Time based split)

In the second example, we first have the settings for the splitting condition like below from transaction “/DBE/FSM_LCM_TSP - Time Split determination” that is set to time based instead of duration.

Now, when we submit the time effort from SAP FSM mobile client for work time from 06:00 to 10:00, the time will be split between over time from 06:00 to 08:00 and then standard hours from 08:00 to 10:00.

As seen in the final outcome of the SAP VSS order, two(2) item positions were created, 2 hours for standard and 2 hours for overtime as expected.