Hierarchy

⤷

⤷

Basic Data
Data Element | CFC_HIER_LEVEL |
Short Description | CFC: Level/step in the application hierarchy |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CFC_HIER_LEVEL | |
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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.level |
Medium | 15 | Hier.level |
Long | 20 | Hierarchy level |
Heading | 6 | H.levl |
Documentation
Definition
Each application is assigned to an application level. An application can only be assigned to one application level.
The order in the hierarchy determines the selection and the order in which the event function modules are executed:
Selection of the function modules:
If the event has process interface characteristic (see interface type), only the function module of the highest or most specific application level (for example, customer) is executed.
If the interface is defined as an open interface, the highest/most specific application level determines whether the function module of the lower application should also be executed (see meaning of the SUPER indicator ).
Order of execution
The function modules are executed in order per application hierarchy level. The lowest or most general application levels are carried out first (for example, basis), and the most specifice last (for example, customer).
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |