Hierarchy
⤷
⤷
Basic Data
| Data Element | IWP_HIENMTFL |
| Short Description | Entire Hierarchy IsTime-Dependent |
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 | 10 | Hier. TD |
| Medium | 20 | EntireHier. TimeDep. |
| Long | 34 | Entire Hierarchy Is Time-Dependent |
| Heading | 4 | HiTD |
Documentation
Definition
Use
If you select this indicator, the system interprets the entire hierarchy as a time-dependent hierarchy.
Dependencies
Example
You can make the hierarchy time-dependent for the characteristic 'chief district' within the framework of your enterprise. In this way, you can compare the structures in a query at different times.
Hierarchy from 01/01/99 to 05/31/99 Hierarchy from 06/01/99 to 12/31/99
Chief district NORTH Chief district NORTH
District 1 District 2
District 2
Chief district SOUTH Chief district SOUTH
District 3 District 1
District 4 District 3
District 4
The valid hierarchy is uniquely identified by the technical name and the validity period. The time-dependent hierarchies that are created are displayed in the InfoObject tree below the respective InfoObject, together with the end date.
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in | 720 |