Hierarchy
⤷ PT (Application Component) Personnel Time Management
⤷ PTIM (Package) HR Time Management Application Development
Basic Data
Data Element | PTM_QUALDATE1 |
Short Description | Key date for recalculation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATE | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
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 | Key date |
Medium | 15 | Key date |
Long | 22 | Key date for recalc. |
Heading | 22 | Key date for recalc. |
Documentation
Definition
Report RPTLEACONV requires the key date for recalculation to calculate the validity and deduction intervals of the quotas that receive transferred remaining leave. You define the validity and deduction intervals in Customizing for Time Data Recording and Administration, in the step Determine Validity and Deduction Periods.
The default key date for recalculation is the system date.
The key date for recalculation does not affect the time at which remaining leave is actually transferred to quotas: Remaining leave from the Leave Entitlement infotype (0005) is not transferred to quotas until the batch input session generated by the report is processed.
Use
The validity and deduction intervals are determined from your Customizing settings, according to the key date for recalculation When choosing a key date, please note the following:
- If you want the quotas to be valid in the same leave year as the leave records of 0005, for example, the key date for recalculation should also be in the same leave year.
- If you want the quotas to be valid in the next leave year, the key date for recalculation should also be in the next leave year.
In this case, you should run the batch input session as closely as possible to the valid-from date of the generated quota, since infotype 0005 can no longer be deducted after the transfer (remaining leave = zero), and the new quotas are not valid, and cannot be deducted, until the next leave year.
Examples
For examples on choosing a key date for recalculation and notes on customizing quotas, see the documentation on report RPTLEACONV.
History
Last changed by/on | SAP | 20010222 |
SAP Release Created in | 46C |