The standard system supplies three schemas, which cover many requirements. You can use them as templates and customize them to suit your customer-specific requirements. The three schemas require different forms of time data for evaluation and pursue different strategies in evaluating the time data.
The schema you decide to use depends on several factors. However, when you opt for one particular schema, you are not committing yourself to one particular method of processing the time data. You can copy functions that are provided by another standard time evaluation schema to your chosen schema and modify the processing accordingly.
The SAP standard schema you choose to use as a template to customize to suit your user-specific requirements generally depends on the method of time recording you use and the requirements you make of time evaluation:
Which time evaluation results are required
How the time data is recorded
The context in which the time data is recorded
The format in which the time data is recorded
How the planned specifications from the daily work schedule are checked
How overtime is determined and approved
The TM01 schema assumes the following prerequisites and goals:
TM01 is used to form time wage types and time accounts. It is processed by the time evaluation driver RPTIME00.
The TM01 schema is used to import and process time data recorded online (that is, in the Time Management infotypes).
It was developed for evaluating time data, where only the deviations from the work schedule are recorded. In this case, the actual working times are not recorded.
All the time data recorded online must be clock times and must be full-day records.
In the TM01 schema, before day processing (initialization block of the schema) the MOD function determines that, depending on the employee grouping, only certain time wage types and time types are formed, and that absences are valuated differently. It determines the groupings with which the time evaluation driver accesses the corresponding tables during processing.
To do this, the MOD function calls the TMON personnel calculation rule.
A personnel calculation subrule is called in the TMON rule according to the employee's employee subgroup grouping for the personnel calculation rule. The groupings for table access are defined here.
Groupings for accessing tables are generally determined in relation to other organizational assignments, such as the personnel subarea, employee subgroup, and so on.
Processing can also be determined individually via the employee grouping for the time evaluation rule in the Time Recording Information infotype (0050); the organizational assignments in the standard system are not relevant in this case. This is done using PAYTP S. Note the effects on table access (for example, in time wage type selection for hourly wage earners, salaried employees, and so on) in time wage type selection.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation Without Clock Times→Initial Steps→Define Groupings.
To enable the planned pair formed by function P2000 to be overwritten by attendances/absences in the TIP table, parameter 2 of functions P2001 and P2002 must have the value 1.
In time evaluation for work schedule deviations, the time type determination group is set to 02 in the initialization block. All times within the planned working time are assigned the processing type S (excluding the breaks). All attendances outside the planned working time (time identifier 01) are assigned the processing type M.
The following processing types are used for time wage type selection:
| S | The TIP entry is included in the daily calculation of planned time, without a maximum daily working time. |
| M | The TIP entry is valuated as overtime; the time is not included in the daily planned working time. |
| – | The TIP entry is deleted later. |
| BLANK | The TIP entry is not valuated as productive time. |
| K | Core night work (Germany only) |
You can also use the TO13 personnel calculation rule to check the daily maximum working time in TM01. If it is exceeded, the processing type of the relevant TIP entries are set to blank. This means that no time wage types are selected for these TIP entries.
The principal differences in comparison with TM00 are in the following processing steps:
Data collection
Error checks
Classification of planned hours and overtime
The DEFTP function is not required in the TM01 schema, since planned hours and overtime are classified completely in Customizing for time type determination.
The TM04 schema assumes the following prerequisites and goals:
The TM04 schema forms time wage types and time accounts. It is processed by the time evaluation driver RPTIME00.
It is used to import and process time data recorded online. The employee's working time is recorded in the Attendances infotype (2002).
It can be used if you record work schedule deviations and if you record all actual working times.
You do not use clock times for evaluating time data. The clock times in the daily work schedule are therefore irrelevant.
All recorded times are counted as working times for the purposes of determining overtime. The following types of overtime regulations are possible:
Overtime starts after x hours per day
Overtime starts after y hours per week
Overtime starts after z consecutive days worked
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation Without Clock Times.
The P2001 function generates an entry in the internal table TIP for each recorded absence (infotype 2001). The P2002 function enters the attendances from infotype 2002 in the internal table TIP. For full-day absences and attendances, a time pair is generated according to the planned working times from the daily work schedule.
Depending on how attendances and absences are recorded and how the HRSIF feature is set, the clock times are stored in the TIP table.
When loading full-day attendances or absences, time evaluation generates the times according to the planned working times. (When full-day attendances and absences are recorded, the attendance or absence hours are not entered manually, but instead are imported automatically from the daily work schedule.)
If employees' times are recorded as a number of hours, the time data cannot be valuated using the planned specifications from the daily work schedule. In this case, the processing type/time type class enables the time data to be classified.
You can use the processing type/time type class to group attendance and absence types into categories, for example, all absences that concern a period of leave or all absences that relate to a period of illness.
The TYPES function is used to assign a time type and a processing type to each TIP entry depending on the pair type and the processing type/time type class. If there is a TIP entry or time pair from time postings where the processing type/time type class is not filled, the system applies the value 00.
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation Without Clock Times→Time Data Processing→Assign Time Types and Processing Types.
The personnel subarea grouping for time recording is a grouping of personnel subareas that use the same
Time types
Time transfer specifications
Access control groups
Error descriptions
For more information, see the Implementation Guide for Personnel Time Management and choose Time Evaluation→Time Evaluation Settings→Set Personnel Subarea Groupings for Time Recording..
You set the time type determination group in the TMON personnel calculation rule, using the MODIF T operation. The time type determination group 02 (MODIF T=02) is used in the standard system for time evaluation without clock times.
The TYPES function assigns a time type to the TIP entries. The TR11 personnel calculation rule then cumulates the number of hours in the TIP entries in various comprehensive time types (time balances). You can read the entries in the Processing Type and Time Type acc. to Attendance/Absence Class (V_T555Y) view in the following ways:
Horizontally, to determine balances that are based on the classifications of the attendances and absences by the processing type/time type class
Vertically to determine balances that relate to employees’ attendance and absence statuses