You can find the view at a later time using this short text, for example.
You can include in the maintenance view only those tables that are linked with the primary table (indirectly) with a foreign key.
In a maintenance view you can insert only tables that are linked to one another with foreign keys.
All existing foreign key relationships of the primary table are displayed.
The secondary table used in such a foreign key is included in the view. The system displays the join conditions derived from the foreign keys. For more information, see Foreign Key Relationship and Join Condition .
You can also (optionally) insert tables that are linked by foreign key with one of the secondary tables that was already inserted. To do this, proceed as follows:
All existing foreign key relationships of the secondary table are displayed.
The system displays the join conditions derived from the foreign keys.
For maintenance and help views, there are certain restrictions on the foreign keys with which the tables can be included in the view (see Restrictions for Maintenance and Help Views ). The system displays the foreign keys that violate these conditions at the end of the list under the header Relationships with unsuitable cardinality.
All the tables contained in the view are displayed in a dialog box.
The fields of the table are now displayed in a dialog box.
All key fields of the primary table must be included in a maintenance view.
All key fields of secondary tables that are not involved in the foreign key (that is, which are not linked via a join condition to a key field already included in the view) must be included in the view.
This ensures that the records inserted with a maintenance view can be written correctly in the tables contained in the view.
The selection conditions define the data records that can be selected with the view.
The maintenance status defines how you can access the view data with the standard maintenance transaction (transaction code SM30).
You are asked to assign the view a package. You can change this package later by choosing Goto → Object Directory Entry
At activation, a log is written. It can be displayed with Utilities → Activation log. If errors or warnings occur when the view is activated, the system automatically displays the activation log.
From the view definition, you can generate maintenance modules and maintenance interfaces that distribute the data entered with the view to the base tables of the view. For more information, see Creating a Maintenance Dialog .
You can create information about using the view by choosing Goto → Documentation. This documentation is output when you print the view, for example.
Select the indicator in column Mod (modification) for the view field. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
On the Maintenance status tab page, select the delivery class of the maintenance view. If you assign the delivery class G or E to the view, you must also maintain a customer namespace (key block) for the view entries. To maintain the customer namespace, choose Customer Namespace Definition.
On the View fields tab page you can define the Maintenance Attributes of the view field in column P.
By choosing Utilities → Runtime object → Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the definitions in the runtime object of the view. By choosing Utilities → Runtime object → Display you can display the runtime object of the view.