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.
Showing results for 
Search instead for 
Did you mean: 

what is the need for TMG?

Former Member
0 Kudos

Hi, iam new to ABAP......


Former Member
0 Kudos


table maintanance Generator is used to manually

input values using transaction sm30

follow below steps

1) go to se11 check table maintanance check box under

attributes tab

2) utilities-table maintanance Generator->

create function group and assign it under

function group input box.

also assign authorization group default &NC& .


select standard recording routine radio in table

table mainitainence generator to move table

contents to quality and production by assigning

it to request.

4) select maintaience type as single step.

5) maintainence screen as system generated numbers

this dialog box appears when you click on create


6) save and activate table

/message/2831202#2831202 [original link is broken]

One step, two step in Table Maintenance Generator

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

<b>Reward points for useful Answers</b>



Former Member
0 Kudos


We can use table maintenance for making the creation,deletion,changing the entries easily.

We can even make use of the validations required for some fields thro' table maintenance,while creating the entry.

If some fields need to be populated automatically while creating an record in a database,we can make use of table maintenance for this purpose.

When the extended table maintenance is called, a work area is fetched from the database into an internal buffer for processing on the screen. Either all entries in the database are fetched into the work area, or the selection can be restricted in a view definition or in the calling program.

Field contents are maintained in an internal buffer, so the database is not automatically accessed after each individual record has been maintaIned. Changes made are only copied from the internal buffer to the database when save is chosen. This buffering gives the maintenance procedure a transaction orientation. This gives you the possibility of discarding changes before the database access (user-controlled "rollback") and allows consistency checks for all changed data, before it is written to the database.




<b>Reward points</b>