Hierarchy
MDG_FND (Software Component) MDG Foundation⤷
CA-MDG-AF (Application Component) Application Framework⤷
USMD1 (Package) Master Data: Data Modeling
Basic Data
| Data Element | USMD_HRY |
| Short Description | Hierarchies |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | USMD_HRY | |
| 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 | 0 | |
| Medium | 15 | Hierarchies |
| Long | 20 | Hierarchies |
| Heading | 0 |
Documentation
Definition
Determines whether you can set up a hierarchy for an entity type and which properties each hierarchy is to have.
A hierarchy determines the hierarchical dependencies between entities of certain entity types. It can have the following properties:
- Version-dependent
A version-dependent hierarchy allows for multiple hierarchy versions. They enable different views of the hierarchical dependencies. You define hierarchy versions in Customizing under Financial Master Data Management -> Create Hierarchy Versions.
- Cross-name
In a cross-name hierarchy, the structure of the hierarchy's substructures is the same throughout. This means that when an entity of a certain entity type has one or more lower-level entities (in a specific order), this structure is used for all other hierarchies. In this case, you cannot define a different structure for the entity within the same hierarchy or in another hierarchy.
You can combine the properties described here as you see fit. This results in the following selectable options:
- No Hierarchy - You cannot set up a hierarchy.
- Not Version-Dependent/Cross-Name - You can set up cross-name hierarchies only. Defining hierarchy versions is not permitted.
- Version-Dependent/Cross-Name - You can only define cross-name hierarchies. In addition, you can define different hierarchy versions.
- Not Version-Dependent/Not Cross-Name - You can set up hierarchies that are not cross-name only. Defining hierarchy versions is not permitted.
- Version-Dependent/Not Cross-Name - You can set up hierarchies that are not cross-name only. In addition, you can define different hierarchy versions.
Use
If a hierarchy can be set up for an entity type, the system generates the database tables for storing the hierarchies automatically.
Dependencies
You can allow a hierarchy to be set up only for entity types with storage and use type 1 with a data element.
In the subdialog Additional Entity Types in Hierarchies, you specify which entity type should be used as the root node (hierarchy name) of the hierarchies. This entry is required for all entity types for which a hierarchy can be set up.
In the hierarchy of an entity type in the standard system, only nodes of the same entity type are allowed in addition to the root node. If you want to allow other entity types (you can only do this for storage and use types 1, 2, and 3), you must specify these in the subdialog Additional Entity Types in Hierarchies.
See also
For more information about hierarchies, see SAP Library under SAP ERP Central Component -> Accounting -> Financial Master Data Management -> Configuration -> Structure of the Data Model and Database Tables.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 604 |
