Show TOC

Managing Maintenance ObjectsLocate this document in the navigation structure

Use

Maintenance objects defined in the ABAP Dictionary (as tables or views) or elsewhere as view clusters are automatically in the maintenance object management. They are assigned attributes centrally. If the table maintenance dialogs have been extended by user exits, the objects must also be manually modified.

Dynamic objects such as logically related data maintained by an individual transaction must be created manually. Logical transport objects can also be included in maintenance object management.

How you maintain maintenance objects depends on the object type. The basic values for some object types are stored in the ABAP Dictionary, but the values for other object types must be maintained in maintenance object management.

Tables (object type S) and views (object type V)

All tables and (maintenance or help) views must have table maintenance dialogs, and you must be able to maintain them with extended table maintenance.

  • Tables and views created before Release 3.0.

    The maintenance object definitions for these tables and views are automatically converted - the system creates a header entry with the necessary attributes and fills the table object list with values.

  • New tables and views.

    Basic information (table data) for new tables and views is maintained in the ABAP Dictionary. The header entry is created when the standard table maintenance dialog is generated.

You must also:

  • Add any tables which are also used in user exits from the table maintenance dialog, to the object list.

View clusters (object type C)

For new objects of type C, the basic information is maintained in the view cluster definition (transaction Start of the navigation path SM54 Next navigation step Edit View Cluster End of the navigation path). This includes the header entry and the object list for the central maintenance object definition. The object liste of a view cluster is the views and tables in the cluster. You cannot maintain this object list manually.

Individual transactions (object type T)

For type T objects, you must:

  • Generate a header entry.

  • Maintain the table object list.

Logical transport objects (object type L)

Logical transport objects dynamically define new transport objects that consist of one or more table entries. Besides the table names, the object list of a logical transport object contains macro definitions to create the table keys for the object.

The option to define new logical transport objects is reserved by SAP for internal purposes.

Dummy objects (object type D)

For type D objects, you must:

  • Generate a header entry.