Hierarchy
⤷ PT (Application Component) Personnel Time Management
⤷ PTIM (Package) HR Time Management Application Development
IMG Activity
ID | SIMG_OHT068 | Analyze Overtime on a Weekly Basis |
Transaction Code | S_AHR_61018666 | (empty) |
Created on | 19990408 | |
Customizing Attributes | SIMG_OHT068 | Analyze Overtime on a Weekly Basis |
Customizing Activity | SIMG_OHT068 | Analyze Overtime on a Weekly Basis |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_OHT068 |
You can use this special function if the standard functions are not sufficient for your requirements.
In this step you can decide whether you want to analyze overtime on a weekly basis. This is necessary if overtime is not generated until the weekly planned working time has been completed.
Example
An employee has approval to work 2 hours of overtime each day and has a planned working time of 40 hours each week. He or she works for 9 hours on two days of the week, 7 hours on one day, and 8 hours on the remaining days. One hour is deducted from the overtime for the deficient planned working time. The employee is therefore compensated for one hour of overtime.
Requirements
The weekly planned working time must be specified in the work schedule rule.
The time type in which the correction specification is stored and which is processed using operation GOTC must be set up in Customizing. Make sure that the time type is saved as a day balance without prior cancellation.
See also: Store as day balance field in the Time Types view (V_T555A).
Standard settings
In the standard system, subschema TPOW is used for weekly overtime analysis. The subschema is not active in the standard schema TM00.
Recommendation
Activities
Decide whether you want to use overtime to make up for deficient weekly planned working time.
If you do, activate function COPY TPOW.
Further notes
- The overtime analysis is based on a week beginning on a Monday and ending on a Sunday. If you want to choose another framework for the week, you can use feature LDAYW. For information on how to modify schema TPOW to accommodate the change, see Calculate Overtime on the Basis of General Periods.
- For an exact description of overtime generation based on attendance quotas, see Determine Overtime from Attendance Quotas.
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 | SIMG_OHT068 | 0 | HLA0003735 | Time Evaluation with 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 | TM00 45 | Modify Schema: Function COPY TPOW | ||
V_T555A | V - View | SM30 | 10 | Create and Check Time Types |
History
Last changed by/on | SAP | 19990429 |
SAP Release Created in |