SAP ABAP Data Element AEGUL (Date from which change is valid)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WART (Package) IS-R: Integrated article maintenance
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WART (Package) IS-R: Integrated article maintenance
Basic Data
Data Element | AEGUL |
Short Description | Date from which change is valid |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
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 | Valid from |
Medium | 15 | Valid from |
Long | 20 | Change valid from |
Heading | 10 | Valid |
Documentation
Definition
Date on which a planned change is to become valid.
Technical documentation:
Table: -
Views:
Screens: change and display / access
Characteristics: DATE
Default value: SY-DATE (however, a SPA/GPA must have been set) in order to set subsequent processing with the same date.
Check: date valid / >= SY-DATE / <= valid_to_MARA (incl. LVORM) / >= access date
For each selected view: if validity delimiters have been set (in connection with possibly selected org. levels, this date must be in the appropriate interval -> check in individual view control).
History
Last changed by/on | SAP | 19950401 |
SAP Release Created in |