Hierarchy

⤷

⤷

Basic Data
Data Element | RSIOBJCMP |
Short Description | Superior InfoObject (compound) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RSIOBJNM | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | Sup. IObj. |
Medium | 20 | Superior InfoObject |
Long | 40 | Superior InfoObject |
Heading | 30 | Sup. IObject |
Documentation
Definition
In this field, the higher-level InfoObjects for a compounded characteristic appear - meaning the InfoObjects, to which the characteristic is compounded.
By using compound InfoObjects, you can model the dependencies between InfoObjects. You can compound InfoObjects to map the data structure of a source system.
Example
You can only evaluate the characteristic 'storage location' in conjunction with a 'plant'. In this case, you define a characteristic compound 'storage location' to 'plant'.
An special case for compounding is the option to compound characteristics to the source system ID. This can be necessary if there are identical characteristic values for the same characteristic in different source systems that describe different objects. You can switch this compounding on and off with the pushbutton 'local source system on/off', located above the list of the higher-level InfoObjects.
Note
Through the extensive use of compounded InfoObjects, in particular if you include a large number of InfoObjects in a compound, the performance can be affected. Try not to represent hierarchical relationships by compounds; use hierarchies for this instead.
History
Last changed by/on | SAP | 19980116 |
SAP Release Created in |