SAP ABAP IMG Activity OHTY020 (Determine Overtime According to the Working Week)
Hierarchy
☛ SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR
   ⤷ PT (Application Component) Personnel Time Management
     ⤷ PTIC (Package) HR Time Data: Customizing
IMG Activity
ID OHTY020 Determine Overtime According to the Working Week  
Transaction Code S_AHR_61009985   IMG Activity: OHTY020 
Created on 19981221    
Customizing Attributes OHTY020   Determine overtime according to the working week 
Customizing Activity OHTY020   Determine Overtime According to the Working Week 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHTY020    

The following section describes how overtime is calculated once y target hours have been worked during a working week.

The term "working week" can be given a flexible definition and is characterized as follows:

  • The starting point can be on any weekday and at any time.
  • The length is determined by specifying a number of days.

Example

An employee works as follows:

Weekday: Su Mo Tu We Th Fr Sa
Attendance hours: - 6 12 12 12 8 -
Absence hours: - 2 - - -

Your company considers overtime to have been performed once an employee has worked 40 hours in a working week. Only work that has actually been performed counts towards these 40 hours. Absences, including paid absences, do not count towards the 40 hours threshold.

The working week on which this example is based starts each Sunday at midnight and is 7 days long.

In this example, 2 hours of overtime are performed on Thursday and 8 on Friday.

Requirements

The times that are recognized as planned working time must be assigned a special processing type.

Standard settings

In the standard system, overtime is calculated by subschema TW30 on the basis of the weekly working hours performed. The weekly hours threshold is stored in the constant OVERT.

Activities

  1. If you do not use a regulation for the week-based calculation of overtime, change the schema by deactivating or deleting the line that accesses subschema TW30.
  2. If you want to use overtime regulation TW30, you must first define the working weeks that are required:
    1. Assign a two-character key of your choice to enable you to identify the working week.
    2. Define the periodicity in days.
    3. Set the date on which the working week commences.
    4. Determine the start time.
  3. Infotype 0007 Planned Working Time is used to assign a working week to an employee. The appropriate field is not, however, displayed in the standard delivery system and must be activated using infotype screen control. Once you have accessed the detail screen, change the characteristic of the field P0007-WWEEK to Standard setting.
  4. When you create infotype 0007 Planned Working Time, you can create a default value for the working week automatically. You can alter this value depending on your employee's organizational assignment. Feature WWEEK, which you must adapt to meet your requirements, is responsible for this.
  5. If you want to perform further adjustments to the overtime regulation in TW30, make a copy of the TWxx personnel calculation rule in question, and rename it ZWxx. Then change subschema TW30 so that it accesses the appropriate rules.
  6. If a different hours threshold must be used to calculate overtime instead of the number of hours stored in constant OVERT, the value COVERT in personnel calculation rule ZW04 must be replaced. As well as numbers of hours that are explicitly determined, such as 50.00, any value can be used that is made available by the parameter settings of operation HRS. Typical examples are as follows:
    • via Cxxxxx the value xxxxx from the table of constants
    • via TWEHRS the average number of weekly hours to be worked in accordance with the work schedule.

      Further options are described in the documentation on operation HRS.

  7. If (certain) absences can be credited to the hours threshold, ADDDB0903 must be added to increase time type 0903 for times with processing type 'S' (target time), pair type '2' (recorded absence), and any other restrictions. This adjustment must be made in personnel calculation rule ZW06. Operation VARAB can be used to query information on the absence, such as the absence type or time evaluation class.

Further notes

  • If you want all your working weeks to be based on the start day rather than the start time, you can either use the procedure described above by defining the working weeks without times, or you can replace subschema TW30 with subschema TW20. The latter is an example for a working week that commences on a Sunday. The advantage of using schema TW20 is that you do not have to explicitly assign a working week to your employees via infotype 0007 Planned Working Time.
  • The further notes included in Calculate overtime on a daily basis are also valid when applied to the weekly situation described in this step.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OHTY020 0 HLA0003736 Time Evaluation Without Clock Times 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
PSCC L - Logical transport object PE00 TM04 28 Modify Schema: COPY TW30 
T559A S - Table (with text table) SM30 01 Define Working Weeks 
T588M S - Table (with text table) SM30 09 Activate 'Working Week' Entry Field 
PMKC L - Logical transport object PE00 WWEEK 01 Set Default Values for Working Weeks 
V_T511K V - View SM30 Define Constant for Overtime Determination 
History
Last changed by/on SAP  19990616 
SAP Release Created in