TMG

Introduction
Table Maintenance Generator (TMG) is a tool which is used to create equipment by which customized tables created
by end users can be changed as required, such as making an entry to that table, deleting an entry, modifying an
existing entry etc.
Table Maintenance generator can be created using transaction SE54 or SE11.
A table maintenance generator is used to create table maintenance program to add, modify or delete records in the
database tables. It is generated to maintain customizing data with these maintenance dialogs.
We can check the table maintenance dialog in SM30 or SE16. In SM30, We have display and maintain options. Display
option is used to view the table contents and maintain option is used to maintain the entries in the table.

Reasons to use Table Maintenance Generator

There are different reasons due to which table maintenance generator is used.
1. In the production system, end-users will not be having access to transaction codes like SE11 and
SE16. Therefore, developers will not be having access to many transaction codes including the above SE11 and SE16.
So in order to edit or create the contents of a database table, we should go for table maintenance generator.
2. With the help of table maintenance generator, we can edit or create multiple entries at a time.
3. Various events can be added to the table maintenance generator to maintain the entries. These events get
triggered while maintaining the entries in the table. They help in enhancing the functionality of the table
maintenance.

Modify your SAP database table maintenance events, screen, interface and code.

Once you have created your basic SAP database table and then added a standard table maintenance to it you may
find that you want to change the functionality of it slightly. I.e. you may want to display a message when the data is
saved or prevent users from saving certain combinations of data.

If you required to have custom logic/custom validations in your already created table maintenance, you can use
events to implement custom requirements. Events in table maintenance allow developers to access and modify
predefined positions in the maintenance dialog which couldn’t be access using user flow logic modules. These event
modules are dynamically executed at table maintenance runtime. There are different types of events which executes
at different sections of the maintenence PAI and PBO runtime. For example, before saving the data, after saving the
data, before deleting, after deleting are few of the event types available.

Transaction Codes

SE54: Generate Table Maintenance Dialog

SE55: Table view maintenance DDIC call
SE56: Table view display DDIC call
SE57: Deletion of Table Maintenance

Table Maintenance Events

The value to be displayed on the maintenance screen for any field can also be altered as per the requirement like
for every new entry in the table one of the field should have the constant value appearing automatically. For this
purpose, the event needs to be chosen which performs the action. In this case event "05 creating a new entry".

List of Events available in Table maintenance

01 Before saving the data in the database

02 After saving the data in the database

03 Before deleting the data displayed

04 After deleting the data displayed

05 Creating a new entry

06 After completely performing the function 'Get original'

07 Before correcting the contents of a selected field

08 After correcting the contents of a selected field

09 After getting the original of an entry

10 After creating the header entries for the change task (E071)

11 After changing a key entry for the change task (E071K)

12 After changing the key entries for the change task (E071K)