Maintenance Views
Maintenance views offer easy ways to maintain complex application objects.
Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The
maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for maintenance views are always derived from the foreign key (see
Foreign Key Relationship and Join Condition). You cannot directly enter the join conditions as for database views.There are some restrictions for the attributes of the foreign keys with which the tables in a maintenance view can be linked (see
Restrictions for Maintenance and Help Views).A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data from the base tables of a maintenance view together.
Maintenance mechanisms, like screens and processing programs, must be created from the view definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-use maintenance interfaces in a simple manner.
You can find out how to create such maintenance mechanisms in the documentation
BC - Generate Table Maintenance Dialog.
See also:
Creating Maintenance ViewsMaintenance Status
