Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SE54 - SM30

Former Member
0 Kudos

What is the diff. between SE54 and SM30?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

1 If a maintenance dialog exists, it is called.

2 If generation of a table maintenance dialog (SE54) is possible, the generated dialog can be included in view clusters (data maintenance using transaction SM34) or be called within a program using function module VIEW_MAINTENANCE_CALL, similar to the call of transaction SM30.

For maintenance views and maintenance view variants only the options Display/Maintenance allowed and Display/Maintenance allowed with restrictions are offered. The option Display/Maintenance not allowed is not offered since the only purpose of the view types is to generate an interface. The option Display/Maintenance not allowed would not allow this.

the maintenance view allows a user to easily enter values into a table, e.g. the administrator enters values into a customising table.

SE54 is the developer tool to generate / change the maintenance view, which is a set of function modules and screens.

SM30 is the user / administrator tool to use the maintenance view. It internally calls the generated function modules and screens, but those details are hidden from the user.

One advantage is that if you use the maintenance view to enter values into a customising table and press SAVE, you will automatically get a popup asking for a customising transport.

When you create a table maintenance generator the system will automatically create the underlying code. The system generates screens for the user to create or edit the entries. This screen can be accessed from SM30 or SM31 transaction.

SE54 is the transaction to display/edit the genreated objects when a table maintenance generator is created.

6 REPLIES 6

Former Member
0 Kudos

Data Browser/Table View Maintenance

You can use the flag for database views, projection views, maintenance views, maintenance view variants, and tables in the Dictionary maintenance (SE11).

The flag is not provided for help views, because help views are mainly used for search purposes.

The options provided in the dropdown list box Data Browser/Table View Maintenance have the following effects:

Display in Data Browser (SE16)

Maintenance in Data Browser

Maintenance and Display in Table View Maintenance (SM30)

Generation of a Table Maintenance Dialog (SE54)

1 If a maintenance dialog exists, it is called.

2 If generation of a table maintenance dialog (SE54) is possible, the generated dialog can be included in view clusters (data maintenance using transaction SM34) or be called within a program using function module VIEW_MAINTENANCE_CALL, similar to the call of transaction SM30.

For maintenance views and maintenance view variants only the options Display/Maintenance allowed and Display/Maintenance allowed with restrictions are offered. The option Display/Maintenance not allowed is not offered since the only purpose of the view types is to generate an interface. The option Display/Maintenance not allowed would not allow this.

________________________________________________________________________________________

The regeneration processes the structure-specific form routines of all maintenance dialogs which have been generated in this function group. This also applies if the regeneration is called via a different path in the Generate Table Maintenance Dialog (SE54) transaction for one maintenance dialog.

Procedure

Choose the function group name from the list from the report RSVIMT_NON_UC_VIM_AREAS. You go to the transaction SE54.

Choose the Edit Function Group pushbutton in the initial screen.

Enter the name of the function group in the field if it is not already displayed.

Set the Regenerate Group-Spec. Programs flag.

Choose the Change pushbutton.

Set the Renew Structure-Specific Form Routines flag in the following screen.

Former Member
0 Kudos

Hello,

the maintenance view allows a user to easily enter values into a table, e.g. the administrator enters values into a customising table.

SE54 is the developer tool to generate / change the maintenance view, which is a set of function modules and screens.

SM30 is the user / administrator tool to use the maintenance view. It internally calls the generated function modules and screens, but those details are hidden from the user.

One advantage is that if you use the maintenance view to enter values into a customising table and press SAVE, you will automatically get a popup asking for a customising transport.

Former Member
0 Kudos

hi

When you create a table maintenance generator the system will automatically create the underlying code. The system generates screens for the user to create or edit the entries. This screen can be accessed from SM30 or SM31 transaction.

SE54 is the transaction to display/edit the genreated objects when a table maintenance generator is created.

regards.

0 Kudos

Can i get the screenshots of SM30 and SE54 please. Thank u.

0 Kudos

Hi,

Please check this link

Table Maintenance (SE54 Screenshots)

http://www.saptechnical.com/Tutorials/ABAP/TableMaintenance/demo.htm

( SE30 )

http://www.saptechnical.com/Tutorials/ABAP/ParameterID/custom.htm

Best regards,

raam

Former Member
0 Kudos

1 If a maintenance dialog exists, it is called.

2 If generation of a table maintenance dialog (SE54) is possible, the generated dialog can be included in view clusters (data maintenance using transaction SM34) or be called within a program using function module VIEW_MAINTENANCE_CALL, similar to the call of transaction SM30.

For maintenance views and maintenance view variants only the options Display/Maintenance allowed and Display/Maintenance allowed with restrictions are offered. The option Display/Maintenance not allowed is not offered since the only purpose of the view types is to generate an interface. The option Display/Maintenance not allowed would not allow this.

the maintenance view allows a user to easily enter values into a table, e.g. the administrator enters values into a customising table.

SE54 is the developer tool to generate / change the maintenance view, which is a set of function modules and screens.

SM30 is the user / administrator tool to use the maintenance view. It internally calls the generated function modules and screens, but those details are hidden from the user.

One advantage is that if you use the maintenance view to enter values into a customising table and press SAVE, you will automatically get a popup asking for a customising transport.

When you create a table maintenance generator the system will automatically create the underlying code. The system generates screens for the user to create or edit the entries. This screen can be accessed from SM30 or SM31 transaction.

SE54 is the transaction to display/edit the genreated objects when a table maintenance generator is created.