This transaction is summarizing two approaches for managing work time patterns in FSM by managing work schedules in SAP ERP backend.
The available options are:
Periodic work schedules customizing along with sending transaction - a new approach compatible with bank holiday management
Calendar work schedules customizing along with sending transaction - an existing approach
Sending transaction for person’s work schedule assignment (covering both periodic and calendar work schedule customizing)
Periodic work schedules customizing consist of company list and periods configuration. This set up is not depended on calendar. The DWS Group is linked to Periodic Work Schedule. Additionally break indicator is provided in order to define whether the breaks should be included.
The customizing can be sent to FSM using designated transaction linked in the cockpit.
The work schedule maintained in SAP ERP backend will appear in the FSM Master data under "Work time patterns". the naming convention for such a pattern includes Grouping information and Periodi
Calendar work schedules customizing is more complex. The company needs to be linked with Employee subgroup, holiday calendar, personal subarea ad work schedule rule. Additionally the work schedule length for such an assignment needs to be defined. Switching on /off breaks functionality is not included.
The work schedule maintained in SAP ERP backend will appear in the FSM Master data under "Work time patterns". The name convention for such a schedule includes all grouping information.
Sending transaction for person’s work schedule assignment
This transaction covers persons' assignments for both periodic and calendar work schedule customizing.
It is required to enter the company, choose the work schedule type option and provide the date of period’s start.
The work schedule assignment in SAP ERP backend will appear in the FSM Master data under "Work time patterns" in People segment.
It is important to remember that SAP ERP backend should be the only source of work time schedule. The schedules should not be created, edited or deleted on the FSM side. It is recommended to manage CRUD permissions for object types WORKTIMEPATTERN and PERSONWORKTIMEPATTERN for all relevant user groups on the FSM side so that editing actions are not possible. Please refer to the example below:
Background
Note the link in HR records for infotype 0007:
2. The work schedule should be maintained in transaction PT01: