The Work Schedule Infotype (1011)
The Work Schedule infotype allows you to define a work schedule – the average number of hours worked – for organizational units, work centers, or positions.
You can also define work schedule groups (which are based on employee groups and employee subgroups). It is not mandatory to maintain this infotype.
In Organizational Management, work schedules are for reference purposes. They are not used to calculate payroll, for example. So work schedules can be considered as a policy statement, or as a guideline for work hours.
You can plan for and implement complex work schedules using the Workforce Planning component.
Default scheduling information is maintained in Customizing, so the Work Schedule infotype is used to identify exceptions to the default information. For example, work times might be uniform at your company, except for one organizational unit. In this case, the easiest approach is to define a work schedule just for that one organizational unit.
You can maintain this infotype using Detail Maintenance, by creating infotype records one object at a time. Or, you can work in Simple Maintenance, where procedures are streamlined. See Setting Attributes in Simple Maintenance.
You can request a report that documents work schedules. The report shows work schedules of organizational units, and possibly positions, and employees, depending on the options you select. The report is RHXSBES0, or RHSBES00 (Staffing Schedule). (If integration is active with Personnel Administration, the report also shows absentee statistics, as well as other personal data.)
Default scheduling information is maintained in Customizing, so the Work Schedule infotype is used to identify exceptions to the default information.
If you need to use work schedules, begin by getting an overview of the different work times at your company. Then, consider the objects you should use to apply the schedules.
Because the inheritance principle applies to work schedules, you must be careful about the objects to which you apply work schedules. You might unintentionally apply a work schedule to an entire branch of your company, when you only intended to apply it to one organizational unit.
It is best to apply work schedules upwards from the bottom of a hierarchical structure.
If you choose to maintain this infotype, you can set up the system so that work schedule records are compared with the planned working times of a employee (defined in Personnel Administration, in the Planned Working Time infotype). This helps ensure stated work hours are consistent. Refer to the Personnel Planning and Development section of the Implementation Guide (IMG).
About Work Schedule Groups
Work schedule groups are based on employee groups and subgroups. You can designate a set of different employee groups and subgroups as a work schedule group. Work schedule groups are maintained in Customizing. Refer to the Personnel Planning and Development section of the IMG.
You cannot apply work schedules directly to work schedule groups, since work schedule groups are not objects – such as a position, or organizational unit. Instead, you must create an infotype record for the organizational unit where the work schedule group exists. In the infotype record, you must ensure that you:
If there is more than one work schedule group in the organizational unit, then there might be multiple infotype records for a single unit.
The inheritance principle applies to the Work Schedule infotype. Lower-level objects automatically receive the work schedules of higher-level objects, unless you specify otherwise.
Consequently, when the system determines the work schedule that applies to each object, it starts with the most specific information and progresses to the most general. The system checks the objects in this order:
If your company uses Personnel Cost Planning, the system may use the work schedule information, together with the information stored in the Cost Planning infotype, to perform calculations. See Personnel Cost Planning