Hierarchy
⤷ PY-DE (Application Component) Germany
⤷ P01C (Package) HR Customizing: Germany
IMG Activity
ID | OHADBLM200 | Modify Personnel Calculation Rule |
Transaction Code | S_AHR_61004013 | IMG Activity: OHADBLM200 |
Created on | 19981221 | |
Customizing Attributes | OHADBLM200 | Modify Personnel Calculation Rule |
Customizing Activity | OHADBLM200 | Modify Personnel Calculation Rule |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHADBLM200 |
- Monthly overtime calculation
The PZL function processes the personnel calculation rule DBM6. Overtime hours are calculated as the difference between the hours worked and the minimum hours for remuneration. The IT table is sorted for this purpose.
The hours before retention are stored using function DBAU FLEX in variable /BEM.
Overtime is only calculated if the retained hours exceed the limits of the working time model. The exceeded part is stored in the /BEL variable, using the DBAU FLEX function.
- Daily calculation of overtime
The Personnel calculation rule DBM0 is processed by function PZL. This rule creates overtime hours for each day as difference between the hours worked and planned hours, and stores the result in Daily statement, construction indsutry.
The overtime is only calculated in rule DBM0 when the retained hours exceed the limit from the working time model.
The exceeded part is stored in variable /BEL using the DBAU FLEX function.
This limit is formed by the personnel calculation rule DBM2 by hours that exceed the planned working hours.
The limit is also formed when the daily planned working time is not reached. This takes place using calculation rule DBM4.
The first overtime hours are also formed if the /BEL variable is zero.
Standard settings
The overtime indicator is determined from the flexibility model using the DBAU MA operation.
The wage type for overtime is determined by the DBAU ML operation.
Recommendation
Activities
If you want to use various overtime wage types, you can determine them with the WGTYP operation.
In this case, copy the DBM3 rule to your own rule, and enter your wage types for overtime.
If necessary, enhance the rule.
ADDITIONAL_HINTS&
The overtime calculation in the standard system does not copy the BRTV 97/98 as regards the determination of overtime.
This applies to the bi-weekly comparison period according to §3, regulation 5.11, as well as regulation 5.12.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHADBLM200 | DE | Germany |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHADBLM200 | 0 | HLA0003774 | Construction Industry |
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 |
PCYC | L - Logical transport object | PE00 | DBM3 | HR: Transport Customer Cycles |
History
Last changed by/on | SAP | 19981221 |
SAP Release Created in |