Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PT (Application Component) Personnel Time Management⤷
PTIM (Package) HR Time Management Application Development
Basic Data
| Data Element | D2OBL |
| Short Description | Indicates whether a second date is required |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | 1 | D |
| Medium | 15 | 2nd date req. |
| Long | 20 | Second date required |
| Heading | 1 | D |
Documentation
Definition
The validity period of a data record can be determined in the initial screen for time data or master data.
If you activate the End date obligatory field, you must
specify the end date of an attendance or absence record in create and copy mode.
Use
Certain attendance and absence data has a great influence on the further processing of employee data. An incorrect validity period, for example, can have far-reaching consequences.
The validity period is usually generated automatically for SAP infotypes. If you activate this field, you ensure that validity periods are always modified accordingly. The administrator must enter the end date of the attendance or absence record on the Time data or master data menu.
If the field is not activated, the values are taken from the Infotypes view (V_T582A).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19950403 |
| SAP Release Created in |
