Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-CSC (Application Component) Country-Specific Objects⤷
ID-DMEEA (Package) INTDEV: ABA services of Data Medium Exchange Engine
Basic Data
| Data Element | DMEE_LEVEL_ABA |
| Short Description | DMEE: hierarchy level of a format tree node |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DMEE_LEVEL_ABA | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Level |
| Medium | 15 | Level |
| Long | 20 | Level |
| Heading | 5 | Level |
Documentation
Definition
The level of a format tree node describes the position of the node in the file hierarchy.
Outgoing Files
Levels must be assigned to all nodes that represent the hierarchy structure, for example segments and segment groups in flat files.
If the file format contains a 1:N relation between records A and B (i.e., for one record A there could be several records B in the file), the segments for A and B must have the levels X and X+1, respectively.
Level 1 represents the top hierarchy level. It is usually assigned to a segment representing the header record of a file.
For each level, one or several key fields have to be defined.
Incoming Files
The level information of the segment describes the hierarchy position of the record in the source file.
Level 1 represents the top hierarchy level and is usually assigned to the segment which represents the header record of the source file. The next segments in the hierarchy are assigned consecutive levels (2, 3, and so on).
Note
The segment with the highest level L_max (i.e. the most detailed level in source file hierarchy) must represent an obligatory record in the source file. Segments for optional records on even more detailed levels must be defined as 'optional supplementary segments'; the same level L_max must be assigned to them.
Example: Segments 'Payment Record' and 'Note to payee' in tree SAP_EXAMPLE for tree type MCSH.
Example
The following flat file has 3 levels (cf. format tree SAP_EXAMPLE for tree type PAYM)
HD Company 1
BP Partner 1 123456
PY 2000 EUR
PY 2000 EUR
BP Partner 2 88888
PY 4000 EUR
PY 5000 EUR
PY 2000 EUR
SU 15000 EUR
For one header record, there are one or more business partner records. In turn, for one business partner record, there are one or more payment records. For each header record, there is exactly one total record at the end.
The header record ('HD') and the total record ('SU') have level 1 , the business partner record ('BP') has level 2 and the payment document record ('PY') has level 3.
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 640 |
