Object Structure

Navigation and view cluster description maintenance (structure table)

Here you enter the dialogs that are to be combined to a view cluster and their relationships to each other. You must maintain the following values for each individual dialog:

• View/Tab: Name of the current object The green arrow next to the dialog goes to the ABAP Dictionary.

• Short text: Context-related text for the current object. The text appears when maintaining the newly created view cluster as navigation text in the navigation subscreen.

• Predecess.: Name of the directly superior object in the object hierarchy. If the current object is on the highest hierarchy level, enter the same name here.

• Dep: Here you define what influence the data selection in the superordinate object has on the maintenance of the contents of the current view. There are the following settings:

  • R: the object is a header entry and has no superior object.

  • S: when navigating to the object specified in View/Table, you may mark only one entry in the superior object (predecessor).

  • M: Dependent entries can be maintained for multiple superordinate entries, that is, any number of entries can be selected in the object for navigation.

• Pos: Here you define the position of the object in the navigation screen. The value must be between 1 and 15. The positions must also be numbered starting with 1.

• Level: Here you define the indentation of the short description of the object in the navigation area. A start dialog always gets level 1, that is, the name appears on the left side of the navigation screen. Level 2 is assigned to the object that is directly dependent on the start dialog. The level must be between 1 and 15.

• Initial: Here you define which dialog is displayed when starting the view cluster.

• Backgr.: Define is the dialog is offered to the user for maintenance. If you select the checkbox, then:

  • The object is not displayed for maintenance.

  • The object does not appear on the navigation screen.

  • Dependent entries in this background dialog box are taken into consideration during deletion, copying, and saving.

N:M: Mark this field if the object and its predecessor have an N:M relationship. The system then takes this relationship into account for hierarchical operations (copy, delete, retrieve, transport).

Field dependency

Use this function to automatically generate field dependencies, provided the corresponding foreign key relationships for these objects exist in the Dictionary. A dialog box confirms generation.