Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BK (Package) CO Cross-application Objects
Basic Data
| Data Element | DATBI |
| Short Description | Valid To Date |
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 | VALID_TO | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | to |
| Medium | 15 | Valid To |
| Long | 20 | Valid To |
| Heading | 10 | to |
Documentation
Definition
Date indicating up to when an entry is valid.
Supplementary Documentation - DATBI 0001
Use
When you create an object, the date to which the object is valid is defined here.
Procedure
Examples
Dependencies
Supplementary Documentation - DATBI 0002
Use
The end of the analysis period is defined in this field.
The analysis period defines the period of validity of time-based master data.
If a field has identical characteristic values for all individual periods in a selected an analysis period, the system displays this. You can maintain these fields as a group, applying changes to all periods within the analysis period.
If a field has different characteristic values in the selected analysis period, the display indicates this with a plus sign (+) in the field. You cannot change the fields for the entire analysis period; instead, you must select the field interval to break it down, and then maintain the individual field values separately.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20000128 |
| SAP Release Created in |
