A work schedule defines the employee´s working pattern, for example, they days and hours that an employee is to work. This helps SAP SuccessFactors Time Off to accurately calculate time off, identify working/non-working days and to calculate leave entitlements.
Work schedules usually apply to groups of employees. However, if, for example, an employee has an extraordinary schedule for which HR doesn't want to create a generally applicable schedule, you can create an individual work schedule, applying only to that employee.
To create a work schedule,
- Navigate to the Manage Time Off Structures app and then choose Create New→Work Schedule.
Work Schedule Models
You can choose from three models for setting up your work schedule. You make your choice from the options offered in the Model field of the work schedule object. Your options are the following:
Simple
Period
Schedule
Note
With a work schedule day model, you can define how the number of hours worked on a particular day should look. You can then use the day models in your work schedule if you choose the period or schedule models.
Whichever option you choose, you enter a starting date. This date acts as the reference point for day 1 of the work schedule.
Work Schedule - Simple Model

You can use this model if you are working only with work schedules that always start on the same day of the week, as with, for example, a Monday to Friday work week.
If you select the simple model, you can enter, for example, a schedule consisting of 5 working days of 8 hours, plus 2 non-work days, like in the figure, work schedule - simple model. It is important to include both working days and non-working days. You can enter in as many days as necessary to cover the work pattern.
Enter the planned working time for each day directly in the Work Schedule Days section.
You need to enter the planned working time for each day separately.
Work Schedule - Period Model
A day model contains the number of hours for a day. You can combine the day models you create to make a period model work schedule. You should include one day model with no working hours to cover non-work days.
If you have a lot of work schedules, you can create different work schedule day models and reuse the work schedule day models to create period models.
For each day of a period model, select one of the following categories in the Work Schedule Days section: Day Model / Panned Hours / Non-Working Day.

In the period model, you enter a start date and a list of day models, along with the number of days. A period schedule can be used if workers work different shifts, such as the early shift or late shift, from week to week and the schedule is repeated. Period work schedules must also include non-working days.
Work Schedule - Schedule Model
If you have shift term workers, you can create a period model with the appropriate shift and create schedule models out of this period model with different start dates, for example, employee A starts with early shift and employee B starts the same day, but on the late shift. Employee C starts the same day, but works on the night shift.
You need to define the time recording variant because period models are supported for both duration-based and clock time-based time recording.

In the schedule model, you enter a start date and a period model. If the start dates for the period model and schedule model are different, the start date for the schedule model overrides that for the period model.
For all three workers, the same 3 Week Shift (3WeekShifts) can be applied, just with different start dates. Take a look at the example in the preceding figure.
The same 3 Week Period model is applied to all three shift groups. The start date for the period model is January 5, 2015 and it includes the first week as an early shift, the second week as the late shift, and the third week as the night shift. You can apply this same period to three different "schedules", only changing the start dates of each schedule. By having the start date as 12/29 (as seen in ShiftGroup1) this date starts employees that are assigned to this schedule with the late shift for the first week, since the start date of the period is still January 5, 2015. For employees assigned the schedule as the same start date as the period start date (January 5, 2015) as in ShiftGroup2, those employees will start out with the early shift. Finally, the third shift group will start the week of January 5th with the night shift, due to the schedule starting date being 01/12/2015.
Work Schedule - Clock Times
You need to define the time recording variant because period models are supported for both duration-based and clock time-based time recording.
The work schedule examples mentioned previously have all used the Duration time recording variant.
As we said, you can choose Clock Times as the time recording variant in the period work schedules and in the schedule work schedules. To configure these, you need to create and maintain segments in your work schedule.

Cross-Midnight Work Schedule
Cross-midnight shifts are not supported within simple work schedules.
Only clock time-based time recording supports cross-midnight shifts.
For employees who work night shift, it is now possible to enter a continuous planned working time segment from one day to the next. For example, you can configure a work schedule with a working time segment from 10:00pm the first day to 6:00am the second day, instead of having to add one segment up to midnight and another starting after midnight. To configure cross midnight work schedules, in the work schedule day model and the work schedule there is a field titled "Cross Midnight Allowed" that enables the ability to record time segments across midnight when you select "Yes". Additionally, for night shift workers who's shift might end at midnight, working time can be recorded to end directly at midnight as well.
You can even set a non-working day to "cross midnight allowed" and also assign a nightshift bandwidth. This option is for those cases, where an employee performs overtime on a regular non-working day, and this overtime is during the night and across midnight. In order that the logical day assignment of this records are the same as if he would work his normal nightshift it is necessary to set the cross midnight flag and the nightshift bandwidth.
You can define a cross-midnight day model for a non-working day. When creating a work schedule day model object, you can set the values for both Cross Midnight Allowed and Non-Working Day as Yes with the Time Recording Variant set to Clock Times. This makes it possible to define a cross-midnight day model for a non-working day. For example, an employee takes over a night shift from a colleague on their non-working day. For this employee, it's still a non-working day without planned working time, but the employee works in a night shift.
Work schedules always represent a rotating working pattern. For example, if you maintain seven work schedule days, the same pattern repeats every week, meaning that day 7 is always followed by day 1 again. So, you need to ensure that the end time of the last work schedule day and the start time of the first work schedule day don’t overlap. Otherwise, you will not be able to save the work schedule. For example, you have a weekly working pattern from Monday (day 1) to Sunday (day 7). The end time on day 7 is at 6am (+1 day), that is, the shift starts on Sunday, but ends on Monday. This option means that the shift on day 1 can’t start earlier than 6am.











