Retrieve the Details of Table or View Maintenance Generators in a Single Screen
- by Qazi Wasif Ali, SAP ABAP Consultant, Descon Engineering Limited
- May 2, 2012
Use ABAP code to create a utility that provides you the details of having more than one table or view maintenance generator in a single screen. With it, you can view all the table and view maintenance generator details that you have created in your system or that are already available in the standard system.
Maintenance generators are normally used for maintaining the tables and views in your system. They enable users to create new entries, change and edit existing entries, and delete and remove existing entries from the tables.
As an ABAP programmer, you sometimes want to know whether a table or view has a maintenance generator and what the attributes of that maintenance generator are (e.g., one step, two step). Suppose you want to maintain the data of a table. Instead of making an application for the data maintenance, you can simply create a table maintenance generator for that particular table, and it fulfills all your needs, such as creating, updating, or deleting data.
Consider this example. Say you have created custom tables in your SAP system, and you want to check that the table maintenance generator exists for them. You also want to know the characteristics of every table. The usual process involves checking every table individually, resulting in a repetitive, time-consuming process.
I developed a utility with ABAP code that allows you to view the details of all custom or standard table and view maintenance generators in a single screen. There is no third-party tool involved; it is completely based on the SAP system. To run it, you need some basic knowledge of ABAP. I show you first the usual process of viewing the table maintenance generators, and then I show you the code involved in my process.
Not every table has a generator. If it does not, you can’t maintain it using transaction SM30 and instead must enter the data in the table using transaction SE11 or SE16. In these cases, no separate transaction code exists for maintaining the table data.
Would you like to see this full item?