Show TOC

Creating Maintenance DialogsLocate this document in the navigation structure

Use

The creation of table/view maintenance dialogs is described here. Maintenance dialogs can be created for SAP or customer tables or views.

There are two steps:

  1. Define table/view

    This step is not required if the table or view does not yet exist.

  2. Define maintenance dialog

Process

Define table/view

The table/view is defined in the Dictionary. A view comprises a primary table and secondary tables which have a foreign key relationship to the primary table. Secondary tables can be

  • Dependent Tables: These tables are extending tables to primar tables and have the same key structure as the primary table. All fields can be maintained directly. The secondary tables are connected using a foreign key with the depdendency degree 'ID' and the cardinality 1 or C. The text table represent an exception that must be defined with the dependency degree TEXT. The logon language is assigned to the language key when you save.

  • Referred Tables: The primary table contains fields which belong to the referred secondary table. The secondary table can have other key fields which are not known to the primary table. The secondary table fields cannot be maintained, they can only be displayed. The referred secondary tables are connected using a foreign key with the depdendency degree OBL or OPT and the cardinality CN or N. All further secondary tables that depend on the referencing table are merely referenced tables for the primary tables.

You can display the view structure graphically with the View Hierarchy Struct. function in the Utilities menu.

To create a table/view:

  • Choose view type Maintenance View.

  • All primary table key fields must be in the view definition.

  • The client field must be included for client-dependent tables/views. The field is not displayed in the maintenance dialog.

  • The language key must not be included for secondary text tables. The logon language is automatically used in maintenance.

  • The key fields must be defined before the function fields. Function fields and key fields must not be mixed.

  • Fields of a referred table cannot be maintained and have the maintenance attribute 'R'.

  • Each field can have a maintenance attribute.

  • You can specify the maintenance status of the entire table/view with the Maintenance Status option. You have the following options:

    • Read only

    • Read, change, delete and create (default setting)

    • Read and change

    • Read and change (time-dependent views)

    Note

    In time-dependent views, the key comprises a time-independent part and the validity range. Choosing read and change (time-dependent views) restricts maintenance to changing and creating the validity range of existing keys.

Define maintenance dialog

You must specify the following parameters in the maintenance dialog definition:

  • Function group: Here you define in which the tables/view-specific maintenance dialog components are generated. The function group is created if necessary.

  • Authorization Group: The users who are authorized to maintain the table/view contents.

  • Maintenance Type: Here you define if the dialog is structured with one step or two. One-step dialogs comprise only an overview screen containing all fields. In two-step dialogs, only the key and text fields with a length of more than 20 characters are displayed in the overview screen. All fields are offered in the detail screen.

  • Maintenance Screens: The internal number of each maintenance screen. You can get possible values in a search function.

  • Recording Routines: Specify whether and how the table/view contents maintained with the dialog are put in a transport.

Result

The maintenance dialog is generated after all values have been entered. If there are no errors, the dialog can be used immediately to maintain table/view contents.