This transaction is summarizing two approaches for managing creating work time patterns in FSM by managing work schedules in SAP ERP backend.
...
Periodic work schedules customizing along with sending transaction - a new approach compatible with bank holiday management
Calendar work schedules customizing along with sending transaction - a functionality which has been previously included in transaction 2105| /PACG/ECM_WSCHD_CONF - Configuration of Work Schedule - obsolete
Sending transaction for person’s work schedule assignment (covering both periodic and calendar work schedule customizing)
| Info |
|---|
Please decide and complete the set up for one approach only - periodic or calendar work schedule. For new implementations it is recommended to use periodic work schedules approach as it is more flexible and compatible with bank holiday management. |
Periodic work schedules customizing is presented in the first part of the cockpit.
...
Only weekly pattern is displayed. The pattern will not be repeated for the while whole time period for which the schedule has been set up but will only display the schedule definition for the number of weeks defined in the pattern.
...
After sending the work schedule maintained in SAP ERP backend will appear in the FSM in Setting and Configurations → Master data under "→ Work time patterns". It will display the schedule pattern for imposed on the whole period set up in the work schedule length in the first level of customizing.
The naming convention for such a schedule includes all grouping information: Employee subgroup grouping (eg 02), Holiday calendar (eg 01), Personnel subarea grouping eg (01), Work scheudule schedule rule (eg NORM)
...
| Info |
|---|
Please note that daily work schedules that finish at midnight in SAP will be sent to FSM as 23.59 due to restrictions related to time formatting in FSM. |
Sending transaction for person’s work schedule assignment is included in the lowest part of the cockpit.
...
| Info |
|---|
It is important to remember that SAP ERP backend should be the only source of work time schedule. The schedules patterns 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 in FSM are not possible. Please refer to the example of restriction set up below: |
Background/ pre-requisites:
Note the link in HR records for infotype 0007
Note the the EE group and EE subgroup defined in PA30 and check the Employee Subgroup Grouping for Work schedule for the combination of EE group and EE subgroup in order to retrieve ES grouping which needed for determination of Work schedule rule.
...