Hierarchy
SAP_HRCBE (Software Component) Sub component SAP_HRCBE of SAP_HR⤷
PY-BE (Application Component) Belgium⤷
P12C (Package) HR customizing: Belgium
IMG Activity
| ID | OHABPERCAL04 | Manage Absence Collisions |
| Transaction Code | S_L9C_94001421 | IMG-Aktivität: OHABPERCAL04 |
| Created on | 20030509 | |
| Customizing Attributes | OHABPERCAL04 | Manage Absence Collisions |
| Customizing Activity | OHABPERCAL04 | Manage Absence Collisions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHABPERCAL04 |
Use
In this Customizing activity, you define which absence is considered when two absences overlap.
Requirements
Standard settings
In this activity, you define values for the Rules for absence collision (V_T5BP6) maintenance view.
If a second absence (absence 2) overlaps with an initial absence (absence 1), then the system interprets the overlapping parts of the absences as a third virtual absence (absence 3). The system generates an absence category character for this third absence. (In most cases, this is the character of absence 1 or absence 2) plus the sequence number of this absence category.) The Absence splitting (T5BP4) table generates the correct valuation code based on the absence category and the sequence number.
The rules can be further refined with reference to the record, as follows:
- You can deactivate the neighboring settings (applicable in many cases)
- You can assign the absence category for absence 3 and whether you want to have the days of the initial absence (absence 1) counted in absence 3
For example, an initial employee absence (absence 1) starts on the 1st and a second absence (absence 2) starts on the 3rd of the month. If you select the Count abs.1 in abs.2 checkbox, then counting for absence 3 starts from 2 not from 0. For more information regarding these settings and behavior, consult the documentation for the corresponding fields.
Note: If both (absence 1 and absence 2) start at the same time and date, the system uses the order in which they were entered in the system. So, for colliding absences that are completely overlapping or that have the same begin date, you should consider defining settings as follows:
- Absence 1 as absence 1 and absence 2 as absence 2, and
- The previously absence 1 being absence 2 and the previously absence 2 being absence 1
Activities
Example
An employee plans a vacation on Wednesday one week in advance; his absence request is accepted and the absence is entered (absence 0100, category V). However, the employee is ill for five days, from Monday until Friday (absence 0200, category Z). On Wednesday, both absences have been entered, but only V is taken into account. Note that absence V is generated as the resulting absence (absence 3).
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 |
|---|---|---|
| OHABPERCAL04 | BE | Belgium |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHABPERCAL04 | 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_T5BP6 | V - View | SM30 |
History
| Last changed by/on | SAP | 20110912 |
| SAP Release Created in | 46C |
