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 | OHTY019 | Determine Overtime on a Daily Basis |
| Transaction Code | S_AHR_61010211 | IMG Activity: OHTY019 |
| Created on | 19981221 | |
| Customizing Attributes | OHTY019 | Determine overtime on a daily basis |
| Customizing Activity | OHTY019 | Determine Overtime on a Daily Basis |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHTY019 |
The following section is concerned with daily overtime calculation.
Typical formulations are as follows:
'Overtime commences once x number of hours have been worked per day'.
The objective is to record periods of overtime in the system and then to use a special processing type to indicate that they are actually recognized as overtime.
Example
Typical daily overtime regulations are as follows:
- If the employee works on a paid public holiday, ie. a day on which the employee is not actually required to work, the entire attendance is valuated as overtime (for which a bonus must be paid).
- If the employee works on a day off (daily work schedule with 0 target hours), overtime commences after 8 hours. The first 8 hours of working time are recorded as planned working time and included in a weekly overtime analysis.
- On a working day, overtime commences after x hours where x is a maximum value that results from 8.00 and the target hours stored in the daily work schedule.
A precise analysis is required of exactly which hours can be credited to the x hours threshold. Consider the following examples: - Only work that has actually been carried out counts towards the x number of hours that must be worked. Absences, including paid absences, do not count towards the overtime hours threshold (x = 8):
An employee has 4 hours leave and is then at work for 9 hours. 1 hour of overtime is performed on this day. - Your company considers overtime to have been performed once an employee has worked 8 'target hours' on one day. The absences recorded in infotype 2001 also count towards the target hours.
This means that 5 hours of overtime have been performed in the above example. - All actual times and some absence times (such as leave, but not sickness) can be credited to the x hours threshold.
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 TW15 on the basis of the number of working hours performed per day.
Daily overtime calculation is carried out in two steps:
- In personnel calculation rule TO01, the hours threshold is calculated for the day to be accounted and then stored in utility time type 0900. In the standard system, the following daily overtime thresholds are calculated:
- on a paid public holiday : after 0 hours
- on a day off : after 8 hours
- on a workday : no daily overtime calculationThe system includes a deactivated alternative, whereby the maximum resulting from 8 hours and the target hours specified in the daily work schedule is suggested as an hour-based threshold.
- In personnel calculation rule TO02, the daily overtime threshold stored in utility time type 0900 is evaluated. The working time that has actually been performed is credited to the hours threshold (ie. absences are ignored). Once the daily overtime threshold has been reached, actual times are assigned processing type 'M' and overtime time type 0040.
Activities
- If you do not want to use a daily overtime regulation, change the schema so that it no longer accesses subschema TW15.
- If you use daily overtime regulations, decide which overtime thresholds must be used on which days. If you do not want to use the standard settings described above, make a copy of personnel calculation rule TO01, rename it ZO01, and then change the rule that is accessed by schema TW15 accordingly. Now adjust rule ZO01. If you want overtime to be calculated on a normal workday once the target number of hours specified in the daily work schedule, or a fixed hours threshold (eg. 8.00), have been reached, activate the line
0 N HRS=S HRS>8,00 ADDDB0900Z "WORKING DAY
and delete the line
0 N HRS=99,00 ADDDB0900Z "WORKING DAY. - Apart from hours that are specified explicitly (eg. 10.00), any value can be used that is made available by the parameter settings for operation HRS. Typical examples are as follows:
- via Cxxxxx the value xxxxx from the table of constants
- via S the planned target hours of the daily work schedule.
Unlike hours that are specified explicitly, constants can be adapted dependent on time. Please ensure that you choose constant names within the customer name range. Further options are described in the documentation on operation HRS.
- The hours threshold is evaluated in personnel calculation rule TO02. If (certain) absences can be credited to the hours threshold, as described in the second example, ADDDB0904 must be added to increase time type 0904 for times with processing type 'S' (target time), pair type '2' (recorded absence), and any other restrictions. Operation VARAB can be used to query information on the absence, such as the absence type or time evaluation class. If you need to adjust the personnel calculation rule, make a copy of rule TO02, rename it ZO02, and change schema TW15 so that it accesses this rule instead.
Further notes
If the target hours determined by the daily work schedule are not chosen as the hours threshold for the calculation of overtime, or if certain times are paid but do not count towards the calculation of overtime, an excess of creditable target hours could be recorded for one day. In the first example, 4 excess hours would be recorded if 8 target hours were stored in the daily work schedule.
This difference from the target hours is recorded within time evaluation in time type 0005. If there are no hourly wage earners, please note that the excess is not included in basic pay and must be settled by Time in lieu or remuneration.
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 | OHTY019 | 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 10 | Modify Schema: COPY TW15 | ||
| PCYC | L - Logical transport object | PE00 | TO01 01 | Modify Personnel Calculation Rule TO01 | ||
| PSCC | L - Logical transport object | PE00 | TW15 01 | Modify Subschema ACTIO TO01 | ||
| V_T511K | V - View | SM30 | Define Constant for Overtime Determination | |||
| PCYC | L - Logical transport object | PE00 | TO02 01 | Modify Personnel Calculation Rule TO02 | ||
| PSCC | L - Logical transport object | PE00 | TW15 02 | Modify Subschema PTIP TO02 GEN |
History
| Last changed by/on | SAP | 19990616 |
| SAP Release Created in |
