Hierarchy

⤷

⤷

Basic Data
Data Element | PAU_AWASQ |
Short Description | Next Absence to be created for same leave code |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | AWART | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | T554S |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Next Abs. |
Medium | 15 | Next Absence |
Long | 27 | Next Absence for same leave |
Heading | 46 | Next Absence to be created for same leave code |
Documentation
Definition
Multiple handling on absence level for a single leave code.
Due to a complex requirement for leave administration and payroll from Public Sector in Australia, the current international leave booking solution via Absences infotype (2001) is not sufficient. It requires a solution that provides the possibilty for having priority handling on absence level as well as priority deduction of quotas for each absence. Following example shows a complex scenario (there are more complex scenarios, for example in combination with parallel deduction for sick leave without MC):
Leave code in IT 0573 Absence type in IT 2001 Quotas
(table T5QPBS2C) (table T554S)
0100 has multiple absences 0700 has multiple quotas 65
0100 has multiple absences 0700 has multiple quotas 70
0100 has multiple absences 0710 has a single quota 71
This scenario can be customized in table Mapping business rules between PS Infotype 0573 and 2001 (T5QPBS2D): Under key entries master leave code 0100 and mapping absence type 0700, you can define the next absence that should be created if not enough entitlements under 0700 exist for the required leave booking of master leave code 0100. The relationship between absence types and quotas can be customized via tables T554S, T554C and T554R. For more information about this, see Implementation Guide (IMG) of International Time Management.
System procedure: System tries to find the mapping absence 0700 by selected values from infotype 0573. This absence is then the starting point for creating absences. If not enough entitlement exists, then all absences that are maintained in the Seq. handling on absences fields in table T5QPBS2D are evaluated. If there are then still not enough entitlements for the required master leave code, system will propose different options for user decision like creating LWOP, purchased leave, anticipation, simulation and so on.
History
Last changed by/on | SAP | 20010720 |
SAP Release Created in | 462A |