Tree Structures Tree Structures

Selecting The Right Display for the Right Purpose

Data can be displayed using many different methods other than the classic "tree structure". Options range from simple list-like displays to complex presentation in ALV grids or the use of so-called shufflers. By answering the following questions, you can help decide which method is the best for displaying the required data:

  • What does the presentation of the data have to achieve?
  • What is supposed to happen to the data itself?
  • Which technique is best suited to this purpose?

To answer these questions and decide on a possible design, we recommend using a decision table that contains the following criteria:

Usage

The user's activities and objectives in a certain concept determine the basic interaction and display forms.

Examples: Display or selection of objects, entering data for complex interactions such as reassignment, re-sorting items

(Data) Structure

In many cases, the data is already present in a logical structure. This structure and the resulting dependencies affect the type of display and how the data is used.

Examples: Lists, tables, outlines, hierarchical tables, hierarchical/sequential lists, tree structures

Hierarchy Depth and Delimitation

Categories or levels are created depending on the type and division of the data. These categories can be indigenous to the data itself or applied externally to clearly sort a large number of elements. The more levels are introduced, the more difficult the manipulation of the overall structure becomes. As a result, your design objective should be to get by with as few levels as possible.

Examples: No hierarchy, one level, two to three levels, many levels, fixed or variable number of levels.

Number of Columns

The user's information requirements determine the amount of data that is displayed. Columns are generally used to display additional information for a specific object. The number of required columns determines the type of suitable presentation and interaction.

Examples: One, two to three, three - n

Overview

The above criteria cannot be considered independently of one another. The following table supplies a rough overview of the possible combinations. However, you should also consider the exact description and analysis of the scenario, as well as the technical and other framework conditions for using the various display forms, for your individual case at hand.

Structure Hierarchy Levels Number of Columns Usage (Scenario) Recommended Display
List 1 1 Browsing through information List
Table
ALV grid
Table 1 2-n ALV grid
Table control
Outline 2 1
Hierarchical/sequential list 2 2-n ALV grid
Regular hier. table 2-10 2-n ALV grid
Irregular hier. table 2-3 2-n ALV grid
Tree 3 or more 1 -> Navigation and search
-> Re-sorting and copying
-> Browsing through information
2 or more -> Navigation and search
-> Re-sorting and copying Simple tree with one column
->Browsing through information ALV tree as full-screen display

Table 1: Basic interaction and diplay forms

Always remember the general rule: Hierarchical structures are difficult to comprehend and use. Therefore, they should be as simple as possible. You should use every possible option for reducing hierarchy levels.

 

top top

Source:  SAP R/3 Style Guide