Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
another advantage comparing to enter data in SE16N is that you can fill in data which is based on database views, meaning to fill in data relevant for more than one table.
E.g. creating maintenance views for value tables incl. language dependent text tables. That is done automaticly.
Another plus is, that you can control data access via authorization groups. You can also create transaction variants of SM30 to create your own tcodes for displaying/editing the content.
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
The set of data that can be selected with a view greatly depends on whether the view implements an
Its is an effective way of maintaining data in tables. While you can create new records, you can simultaneously modify existing records. You donot have to worry about adding corresponding data records to different tables, rather the data is itself distributed in underlying tables.
another advantage comparing to enter data in SE16N is that you can fill in data which is based on database views, meaning to fill in data relevant for more than one table.
E.g. creating maintenance views for value tables incl. language dependent text tables. That is done automaticly.
Another plus is, that you can control data access via authorization groups. You can also create transaction variants of SM30 to create your own tcodes for displaying/editing the content.
a maintainance view is used with transaction SM30.
most users dont knwo much about the technical side of SAP, and you cant let them maintain tables with the SE16N and "&sap_edit", therefopr maintainance views are created.
Maintainance views also can drill down a very complex structure of one or more tables to a simple view where you can maintain things quite user friendly and dont have to know anything about foreign key relations and such.
Maintanance view permit you to maintain the data distributed on several tables for one application object at one time. data is automatically distributed in the underlying database tables. 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. We cannot directly enter the join conditions as for database views.
Please go through the below link for how the data is entered inthis view.
Bluesky
