SAP SF EC Time Management

[Xavier_Volks]

Hi ,

In the Work Schedule object, we have 3 types of models: simple, period, and schedule. What do they mean, and in what situations do we use them? 

I went through the implementation guide, but it's not detailed there.

Please explain with a suitable example.

Thank you.

[Iulia_Bobaru · Accepted solution]

Hi Xaver,

Here's a more detailed explanation:

1. The simple work schedule  is only used for duration-based time recording (i.e. work schedules based on number of hours worked, without specifying start time and end time).

You can enter the planned working time for each day separately (e.g. day1 - 8 hours; day 2- 8 hours; day 3 - 8 hours; day 4 - 8 hours; day 5 - 8 hours; day 6 -0 hours; day 7 -0 hours).

If starting date of work schedule is 1st Jan 1900, then system checks what day of the week that was because that would be day1 of the work schedule; 1st Jan 1900 was a Monday, so day 1 would be Monday with 8 hours planned, day 2 would be Tuesday with 8 hours planned, day 3 Wednesday with 8 hours, day 4 Thursday with 8 hours, day 5 Friday with 8 hours, day 6 Saturday with 0 hours thus nonworking day, day 7 Sunday with 0 hours thus nonworking day. This setup would continue recurringly, for each week. 

If starting date of work schedule was 2nd Jan 1900, then this would be a Tuesday, so day1 would be Tuesday, and the employees would work Tuesday-Saturday 8 hours daily, and Sun-Mon would be days off.

Hope that makes sense so far.

2. The period work schedule  is much more customizable, and can be either duration based or clocktimes-based (specifying start and end time - such as starting shift at 8am and ending at 5pm).

You will then need to specify the work schedule days setup (day1, day2, day 3 and so on), where instead of inputting just the planned hours (like in the simple model) you will have more categories to choose from:

-  "planned hours" category and if it's duration set the number of planned hours (e.g. 8 hours) or if it's clocktimes set segments (scheduled working time, scheduled unpaid break, flextime bandwidth or nightshift bandwidth - e.g. start time 8am end time 17:00 category scheduled working time)

- "day model" - where you will need to select a previously created day model (either duration-based referencing the planned hours, or clocktimes-based referencing the start time and end time of the shift); the day model can be re-used (for instance let's say day model is named DAYTIME between 9 am and 5pm, then you can set day1 - DAYTIME, day2 - DAYTIME, day 3 - DAYTIME, day 4 - DAYTIME, day 5 - DAYTIME)

- non-working day

3. the schedule work schedule is based on a previously created period work schedule, with a certain start date, and it's normally used to help organize the shifts for different teams, based on different patterns. 

e.g. you've previously created a period work schedule starting on 6th Jan 2025 (Monday) with days 1-5 9am-5pm, days 6-7 nonworking day, days 8-12 9pm-5am, days 13-14 nonworking day

If you create a schedule work schedule where you assign that period work schedule for team A with start date 6th Jan 2025 then they will have the work pattern as described above (dayshift from 6th Jan, night shift from 13th Jan); if you create another schedule work schedule for team B with the same period work schedule but a different start date e.g. 13th Jan then they would be under dayshift from 13th Jan (and night shift from 6th Jan).

Hope this helps.

Iulia

[Xavier_Volks · Accepted solution]

Hi Lulia,

The way you explained the Work Schedule is very good. 

Thank you.