PLA D’ACCIONS COMERCIAL I DE MÀRQUETING

Lesson Duration: 120 Minutes

Lesson Overview

In this lesson, you learn about the various methods for determining overtime.

Lesson Objectives

After completing this lesson, you will be able to:

• Explain the various methods for determining overtime

• Describe the process of determining overtime

• Describe how the overtime determined is used

Explain to the participants that they will learn about various methods for determining overtime in the TM04 schema, each of which is based on different periods for analyzing potential overtime.

If required, point out that a method of determining overtime where the times have to be approved, for example, using the Attendance Quotas infotype (2007), is covered in the Time Evaluation With Clock Times unit.

Business Example

In your enterprise, you determine overtime on a weekly basis. You want time evaluation to determine the overtime automatically on the basis of the number of hours each employee has worked.

Determining Overtime

Figure 87: Determining Overtime

Point out that it is only now, once the employee’s planned working times have been determined, that any times over and above the employee’s planned working time can be counted as overtime.

Figure 88: Overtime Determination

xplain the concept behind overtime determination in schema TM04. Only mention the special methods for determining overtime and the business requirements that are catered to in the individual subschemas.

The TW15 and TW30 subschemas are explained on the slides that follow.

The TW10 subschema is not as important, and can be explained in SAP R/3 if required.

It is important that the participants have a general understanding of overtime processing:

– Determining times that constitute overtime – Time wage type selection

– Compensating overtime wage types

If participants ask about it, explain about the Overtime infotype (2005).

Point out that using this infotype is no longer recommended. It is still being maintained but will not be developed any more. It is not supported in the Time Manager’s Workplace. The Attendances infotype now covers all of the functions of the Overtime infotype.

The times that qualify as overtime are determined and assigned the processing type M. Processing type M is used so that special time wage types (basic remuneration for overtime, bonuses) can be selected for these times in a later processing step.

Overtime can also be recorded online in the Attendances infotype (2002) instead of being determined automatically in time evaluation. If the attendances meet the following criteria, they are assigned processing type M in time evaluation:

Hint: The TW10, TW15, and TW30 schemas in the standard SAP system are compliant with the requirements of the United States FLSA (Fair Labor Standards Act) for determining overtime.

• They are grouped in their own processing type/time type class (V_554S_F).

• They are assigned the processing type M in view T555Y for processing type for pair type 1 or processing type for pair type 3.

Figure 89: Determining Overtime on a Daily Basis: Subschema TW15

Subschema TW15 determines overtime on the basis of the hours worked on each day.

• Personnel calculation rule TO01 is used to set valid limits on the number of hours.

In the 0900 time type (Daily overtime after x hours) you define in the rule the limit after which overtime begins for each day. You can define different value limits in the decision tree of the PC rule, depending on the properties of a day. If you do not want overtime analysis to run in a particular situation (such as on a workday), you set the value limit to 99.00.

• Personnel calculation rule TO02 is used to evaluate the daily overtime limits. Once the limit is reached, the attendance times are assigned processing type M.

Hint:

• In the standard system, absence times are not included when overtime is determined.

• You can also use the TW15 subschema in conjunction with weekly overtime determination in the TW30 schema.

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 Days Worked.

Figure 90: Determining Overtime on the Basis of a Working Week: Subschema TW30

Revise the concept of the working week. Show the Customizing settings in SAP R/3.

You can use constant OVERT to set a number of hours after which overtime is calculated.

You can define the length, start date and start time (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 and you only want to define the start day of a 7-day working week for the whole of your enterprise.

Hint:

• Note: In the standard system, absence times are not included when overtime is determined.

• If you use subschema TW20, the assignment for individual employees in the Planned Working Time infotype (0007) is no longer used.

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.

Figure 91: Schema TW30: Working Week With and Without Clock Times

Demonstrate how a working week with and one without clock times affects the determination of overtime. Use an example, in SAP R/3 if required, to explain the concept.

You can define the working week with or without clock times, however you can only evaluate a working week with clock times if you record employees’

time data with clock times.

Different bases are used for calculating overtime depending on whether you define the working week with or without clock times:

• With clock times:

Only times that lie within the specified time frame are included in the overtime calculation.

• Without clock times:

All times whose start time lies within the working week are included in the calculation of overtime.

Figure 92: Schema TW30: 9x80 Flex Schedule

The work schedule 9x80 FLEX is an example of a working week based on clock times (starting on Friday at 12:00). This means that overtime can be determine weekly, even if employees’ weekly planned working hours change periodically.

Example: 1 week 36 hrs + 1 week 44 hrs = 40 hours average weekly working time.

To represent the working time model 9x80 Flex Schedule, the working week is defined over a period of 7 days.

Figure 93: Significance of the Processing Type and the Time Type

Point out that only now does TIP contain all information (time type and processing type) required to trigger time wage type selection and balance formation. Only now are all times in TIP classified.

After overtime has been determined, all the information is available for valuating the times. The TIP entries can now be used to:

• Select time wage types for Payroll according to the processing types

• Form balances according to the time types. The balances are then used for managing time accounts.

Time evaluation saves the results determined in further processing in internal tables:

• Balances in TES (daily balances)

• Time wage types in tables DZL (hourly wage and bonuses) and ZML (overtime). After overtime determination, the overtime wage types are transferred to table DZL.

At the end of time evaluation, the results determined are saved to the database:

• Balances in ZES (daily balances, cluster B2) and SALDO (period balances, cluster B2). The Attendance Quotas (2007) and Absence Quotas (2006) infotypes are updated, if necessary.

• Time wage types are entered in the ZL table at the end of time evaluation.

Table ZL acts as the interface to R/3 Payroll.