
In this form of dynamic assignment of the daily work schedule, the employee's new daily work schedule is determined from a group of daily work schedules as the one that shows an optimum overlap of the planned specifications with the actual times. SAP ERP performs the calculation automatically; you cannot influence the processing.
The dynamic assignment is accessed using the DYNWS function. The assignment is made if the TIP entries for the employee on the day being evaluated come from the following data only:
Time events
Records from the Attendances infotype (2002)
Records from the Overtime infotype (2005)
Records from the Availability infotype (2004)
The advantage this form of processing has over dynamic daily work schedule assignment using the TD30 personnel calculation rule is that you can use the attendance times of the entire day to determine the daily work schedule.
In parameter 3 of the DYNWS function, you determine whether substitutions should be taken into account in the dynamic assignment.
The DYNWS function does not generate a record for the Substitutions infotype (2003). If viewing the assignment of the new daily work schedule using the time evaluation log, time statement, or personal work schedule on cluster B2 is not sufficient for your purposes, you can enter the substitution manually in the infotype.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Providing Time Data→Work Schedule and Time Events→Dynamic Assignment of Daily Work Schedules→Dynamic Assignment Based on Planned/Actual Overlap..

Some working time regulations stipulate that minimum breaks must be observed, depending on the working hours actually performed. The TF20 subschema allows you to:
Check that the minimum break durations have been observed
Report violations of the break duration
Perform an additional break deduction
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Break Processing→Determine Minimum Breaks Based on Hours Worked.

If your company has a guaranteed hours regulation for overtime that is not worked immediately after the planned working time, you can use the personnel calculation schema TG00 to represent this in the system.
You can set the number of guaranteed hours in the GROVT constant in the V_T511K view (Payroll Constants). In the TG00 schema, isolated overtime pairs are extended by a TIP entry of processing type G, until the value defined in the GROVT constant is reached. You can select special wage types for working hours with processing type G in time wage type selection.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Determining Overtime→Process Guaranteed Overtime.

The TOH0 subschema is based on a hypothetical earnings principle: Employees are normally paid for work on a paid public holiday in the same way as for a normal working day. If an employee now works on a paid public holiday, he or she is to be paid for the hours worked within the planned working time at a higher rate than colleagues who have not worked on the public holiday.
In the TOH0 schema, you flag the times that the employee worked within the planned working time with the processing type X. This enables you to define your own time wage type selection rules for these hours of work.
Any hours worked outside of the planned working time are assigned processing type M. You can select special wage types for work on a public holiday for these hours in the conditions for the day in the Time Wage Type Selection view.
If you want to take breaks on a public holiday into consideration, you can use the TOB0 schema.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Determining Overtime→Compensate Overtime Worked on a Public Holiday.


In the TW00 schema, a higher bonus is generated as of the tenth overtime hour per week.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Wage Type Selection and Overtime Compensation→Generate Higher Bonuses on a Weekly Basis.

You can use the TW30 schema to determine overtime pairs per working week, after a certain number of hours is reached. The number of hours is set in the OVERT constant.
You can define the length, start date, and clock times (optional) of the working week. It is stored for each employee in the Planned Working Time infotype (0007). You can define a default value for the working week in the WWEEK feature.
Alternatively, you can use the TW20 subschema. To use it, the following conditions must be met:
You do not need clock times for the working week
You want to define only the start day of a 7-day working week for the whole of your enterprise
If you use the TW20 subschema, the assignment of the working week for individual employees in the Planned Working Time infotype (0007) is no longer used.
Hint
In the standard system, absence times are not included when overtime is determined.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation Without Clock Times→Time Data Processing→Determining Overtime→Determine Overtime According to the Working Week.

The TPOW personnel calculation schema performs weekly overtime analysis on a daily basis. The daily overtime is recognized only after the employee has completed the weekly planned hours.
Information on the weekly overtime analysis is not available until the end of the week. If the employee has not completed the week’s planned working hours, the week is evaluated again in the same evaluation run, and the incorrectly assigned hours of overtime are no longer classed as overtime. To do so, time evaluation reevaluates the week in the same run.
The incorrectly issued hours of overtime are identified in the time balance 0928 OT/Wk:Transfer spec.(wk).
For more information about processing in the TPOW subschema, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Determining Overtime→Analyze Overtime on a Weekly Basis.
The TPOP subschema represents a more general processing method of the TPOW subschema. It determines overtime on the basis of a general period.
For more information about processing in the TPOP subschema, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation With Clock Times→Time Data Processing→Determining Overtime→Calculate Overtime on the Basis of General Periods.

You can use processing instructions for a day to simplify some of the tasks that time administrators carry out frequently. Instead of explicitly entering time data, time administrators simply select a checkbox. SAP ERP then saves a record of the Time Transfer Specifications infotype (2012) in the background. You can define the meaning of each checkbox in Customizing.
You can use processing instructions to:
Issue backdated overtime approvals
Grant general time bonuses
Indicate that the day has been processed, for example
In time evaluation, you can use personnel calculation rules to set up customer-specific processing steps, for example to
Fill time types and wage types
Generate or update infotype records
To do so, call the P2012 function as often as needed in the schema. Enter the required personnel calculation rules in parameter 1 of the function.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Manager's Workplace→Basic Settings→Define Processing Instructions.

Processing instructions for a day are managed in groups. A group of processing instructions can contain up to 7 processing instructions. You organize the groups using a field selection.
You assign thegroup of processing instructions to profiles for the Time Manager's Workplace. Each profile can contain only one group.
Depending on the view in which the checkboxes are to be displayed, the processing instructions appear:
Within the time data table in the Multi-Day View and the Multi-Person view, or
In a line above the time data table in the One-Day View
Hint
If you use the calendar views, no checkboxes are available. You can integrate the time transfer specifications in the list of time data IDs in the calendar, or the time administrators can enter the time transfer specification manually.