Hierarchy
⤷ PY-AT (Application Component) Austria
⤷ PC03 (Package) HR Payroll: Austria
IMG Activity
ID | PAY_AT_ELDA_050 | Define Absence Types for Conversion in Event of Missing Illness Notif. |
Transaction Code | S_L4H_49001783 | (empty) |
Created on | 20110127 | |
Customizing Attributes | PAY_AT_ELDA_050 | Define Absence Types for Conversion in Event of Missing Illness Notif. |
Customizing Activity | PAY_AT_ELDA_050 | Define Absence Types for Conversion in Event of Missing Illness Notificat. |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PAY_AT_ELDA_050 |
Use
In this Customizing activity, you specify how the system is to convert existing absences if no illness notification exists. The system can convert an existing record in the Absences (2001) infotype during the comparison process if the following conditions apply:
- Infotype 2001 contains an absence.
- The absence type in infotype 2011 requires an illness notification.
- The Illness Reporting from EDLA A infotype (3248) does not contain an illness notification.
In the comparison process, the system converts the absence type for the existing record in infotype 2001 into a different absence type. The new absence type depends on the absence type specified to date in infotype 2001.
You can specify a preferred and an alternative absence type. The system first tries to convert the absence into the preferred absence type. If errors occur (for example, because not enough leave days are available for a person), the system uses the alternative absence type instead.
Requirements
Standard settings
Activities
Create an entry for each absence type (infotype 2001) for which you expect an illness notification. These are typically those absence types that you have specified in the Customizing activity Define Absence Types for New Absences Added. For each of these absence types, specify which preferred absence type the system should use in the case of a missing illness notification. You can also specify an alternative absence type.
For the grouping, use the number(s) that you have specified in the Customizing activity Define Grouping for Conflict Resolution Strategies.
Example
In the event of a missing illness notification, the system should convert absences of type Illness (0300) into the preferred absence type Entitled Leave (0100). If this is not possible (because not enough leave days are available, for example), the system should instead convert the absence into the absence type Unpaid Leave at Expense of EE (0700).
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
PAY_AT_ELDA_050 | AT | Austria |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PAY_AT_ELDA_050 | 0 | HLA0001595 | Payroll for Administrations and Institutions |
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_T5AE3 | V - View | SM30 |
History
Last changed by/on | SAP | 20120313 |
SAP Release Created in |