Hierarchy

⤷

⤷

Basic Data
Data Element | PAU_LCODE |
Short Description | Master leave code |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PAU_LCODE | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | T5QPBS2C |
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 | Leave code |
Medium | 15 | Leave code |
Long | 27 | Leave code for PS infotype |
Heading | 27 | Leave code for PS infotype |
Documentation
Definition
Leave code for Absence infotype for Australia PS (0573). This leave code will be mapped to single or multiple absence types in Absences infotype (2001).
Due to complex requirement for leave administration and payroll from Public Sector in Australia, the current international leave booking solution via P2001 is not sufficient. It requires a solution that provides possibility for having priority handling on absence level as well as priority deduction of quotas for each absence. Following example shows a more complex scenario (there are more complex scenarios, for example in combination with parallel deduction for sick leave without MC etc.):
Leave code in P0573 Absence type in P2001 Quotas
(table V_T5QPBS2C) (table T554S)
100 has multiple absences --> 700 has multiple quotas --> 65
100 has multiple absences --> 700 has multiple quotas --> 70
100 has multiple absences --> 710 has single quota --> 71
This scenario can be customized in table Mapping business rules between PS Infotype 0573 and 2001 (V_T5QPBS2D): Under key entries master leave code 100 and mapping absence type 700, you can define the next absence that should be created if not enough entitlements under 700 exist for the required leave booking of master leave code 100. The relationship between absence types and quotas can be customized via tables T554S, T554C and T554R etc. (see IMG of international time management).
System procedure: System tries to find the mapping absence 700 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 under Seq. handling on absences in table V_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 or simulation etc.
History
Last changed by/on | SAP | 20010720 |
SAP Release Created in |