Structure OverviewThe structure overview displays all fields (elements and attributes) in the source and target structures. In the structure overview, you can assign source and target fields to each other or include them in the data-flow editor (see Assigning a Field). The structure overview also contains a variety of additional functions that are described below.
The name of the loaded schema is displayed in the header area of the structure overview. You can call a context menu with the following functions for this name:
● New:
Creates a new message type.
● Open:
Displays the message type or the imported schema for an RFC, an IDoc, or an external definition on a new tab page.
● Copy Object:
Copies the name to the clipboard for input fields of other objects.
● Expand:
In the default setting, the header area of the structure overview only shows the name of the loaded schema due to space restrictions. You can also display the namespace and the software component version of the object by choosing the Expand function.
On both the Design and Test tab pages, you can choose how you want to display the source and target structures:
Structure Overview Display Options
View |
Use |
(only on Definition tab page) |
Only displays nodes for fields (elements and attributes) and their names. |
|
When you select
this view, the field attributes or their type are displayed in addition to the
tree view on the Design tab page. In the
|
|
Displays the structure as text in the editor. You can edit the text document directly in the test environment. |
(only on the Test tab page in the source document view) |
Makes the XML document more readable by using indentations. |
|
Shows or hides the input help to search for fields in the structure. The search function does not support wildcard characters. To search for a node, you only need to enter the first letter of the node name. |
|
Saves the structure as an XML file. |
(only in Tree View or Tabular Tree View) |
Hides all fields in the structure that are not used in any target-field mapping. |
(only in the Tree View or the Tabular Tree View on the Test tab page) |
Removes all fields from the structure of a test instance that are not used in any target-field mapping. |
The field names of the source and target structure must be unique. The mapping editor supports identical field names on the same hierarchy level in the following way:
● Fields of the source and target structure can be qualified by namespaces
● Attributes are differentiated from elements by a preceding at sign (@) in the mapping editor.
For fields in the structure overview (on the Design and Test tab pages), you can copy the path for a field to the clipboard by choosing Copy Path in the context menu. This also applies to fields in the data-flow editor.
The mapping editor
does not fully support the mapping of recursive structures (data types that
reference themselves). In the structure overview, elements of this type are
indicated by means of an icon (
).
Due to their recursive nature, the substructures of these elements can theoretically be infinitely long. It is possible to map these elements in the mapping editor in a rudimentary fashion by using the context menu to expand a specific number of subnodes and then use them in target-field mappings.
● You can display the fields of the source structure in a where-used list:
● Position the cursor on a field to display a quick info that contains information about the target fields this particular field is assigned to by means of a target-field mapping.
● To display a where-used list for a particular field, choose Where-Used List in the context menu. You can navigate directly to the target fields that a particular field is assigned to.
If a field in the target structure is green or yellow, this indicates that an incomplete target-field mapping already exists. Double-click a field to display it in the data-flow editor.
To define
target-field mappings for different positions of a target element that occurs
frequently, the context menu for the target structure has the function
Duplicate Subtree (see:
Duplicating
Subtrees). You have the option of deleting any duplicates that you
create.
A mapping is complete when there is a target-field mapping for all obligatory target fields. In cross-system scenarios where the values for such fields are not entered during mapping, but at a later point in time, this specification is too restrictive. To disable a target field and all its subnodes, choose Disable Field in the context menu in the structure overview. The mapping editor shows disabled fields crossed out. The check and the mapping runtime ignore disabled fields.