Hierarchy
⤷ PY-BE (Application Component) Belgium
⤷ P12C (Package) HR customizing: Belgium
IMG Activity
ID | OHABPERCAL03 | Manage Neighboring Absences |
Transaction Code | S_L9C_94001420 | IMG-Aktivität: OHABPERCAL03 |
Created on | 20030509 | |
Customizing Attributes | OHABPERCAL03 | Manage Neighboring Absences |
Customizing Activity | OHABPERCAL03 | Manage Neighboring Absences |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHABPERCAL03 |
Use
In this Customizing activity, you define the criteria that apply to neighboring employee absences. These criteria provide a framework for determining whether neighboring absences are related, and whether the counting of absence days continues from the first to the second absence.
There are various statutory obligations regarding the management of absences, and for calculating pay and sick pay supplements. It is therefore important to identify whether neighboring absences are related to ensure that these obligations are fulfilled.
Note that changing these settings affects absences with or without a recognized partial illness (RPI). However, the neighborhood period applies in both cases.
Requirements
Standard settings
In this Customizing activity, you maintain the Neighboring absences (V_T5BP5) maintenance view.
This maintenance view enables you to define various criteria related to neighboring absences. For example, whether to count the days of a preceding absence (before the currently processed absence), or to determine whether a guaranteed monthly wage should be paid as a consequence of a related neighboring absence.
Note: The Subsequent Illness field of the Absences (2001) infotype is used to logically separate neighboring absences. If this field has different values in neighboring absences , then the absences are considered unrelated and are processed separately. The field selection can be overwritten using the Ignore subsequent illness setting checkbox.
Activities
Example
For example, an employee has an work accident immediately followed by an illness (no days in between); the illness occurs within the customized timeframe. As a result, the counting of absence days for the illness includes the absence days of the preceding work accident. An explanation of the involved fields and possible values is outlined as follows:
- If a work accident is followed by an illness, the illness would normally include (in its count) the number of absence days for the preceding work accident
- For an employee who is no longer on probation, you specify value 1 for the Belgian absence modifier field
- You define absence 1 as a work accident and absence 2 as an illness (for example, values A and Z)
- To indicate that counting should only continue when there are no working days in between the absences, you select the No work day in between checkbox
Alternatively, you could specify a number of days in between value without selecting the No work day in between checkbox - To include the absence days from the first absence in counting for the second absence, select the Take over day count from abs. 1 to abs. 2 checkbox
- As an additional precaution, you can choose to ignore the neighboring absence settings defined in the Subsequent Illness field of the Absences (2001) infotype, by selecting the Ignore subsequent illness setting checkbox
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHABPERCAL03 | BE | Belgium |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHABPERCAL03 | 0 | HLA0008901 | Gross |
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 |
V_T5BP5 | V - View | SM30 |
History
Last changed by/on | SAP | 20110916 |
SAP Release Created in | 46C |