SAP ABAP Data Element ASR_EFFECTIVE_DATE (Effective Date)
Hierarchy
☛
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
⤷
PA-AS (Application Component) HR Administrative Services
⤷
PAOC_ASR_CONTROLLER (Package) Controller
⤷
⤷
Basic Data
| Data Element | ASR_EFFECTIVE_DATE |
| Short Description | Effective Date |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATS | |
| 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 | Date |
| Medium | 15 | Date |
| Long | 20 | Effective Date |
| Heading | 20 | Effective Date |
Documentation
Definition
Determines the key date on which the changes to the form scenario become active.
Use
Dependencies
The effective date must be defined as a form field with the name EFFECTIVE_DATE and data element ASR_EFFECTIVE_DATE. It is passed on as a so-called mandatory field to the backend services used in the form scenario. The backend services execute their operations on the basis of this effective date.
Example
- Date on which an employee is to be hired
- Date on which an employee is to be transferred
- Date of a bonus payment
History
| Last changed by/on | SAP | 20110901 |
| SAP Release Created in | 600 |