Transporting Table Data

Method 1:
Display the entries that you need to transport in se11.YOu will find an option Table Entry-> Transport Entries in the menu.The changes to the structure are anyway captured in a transport request as and when you activate the change to the structure.
Method 2:
Delivery class
The delivery class controls the transport of table data when installingor upgrading, in a client copy and when transporting between customersystems. The delivery class is also used in the extended tablemaintenance.
There are the following delivery classes:
o A: Application table (master and transaction data).
o C: Customer table, data is maintained by the customer only.
o L: Table for storing temporary data.
o G: Customer table, SAP may insert new data records, but may notoverwrite or delete existing data records. The customer namespacemust be defined in table TRESC. (Use Report RDDKOR54 here).
o E: System table with its own namespaces for customer entries. Thecustomer namespace must be defined in table TRESC. (Use ReportRDDKOR54 here.)
S: System table, data changes have the same status as programchanges.
W: System table (e.g. table of the development environment) whosedata is transported with its own transport objects (e.g. R3TR PROG,R3TR TABL, etc.).
or during client copy
the data of client-specific tables is copied.
Classes C, G, E, S: The data records of the table are copied to thetarget client.
Classes W, L: The data records of the table are not copied to thetarget client.
Class A: Data records are only copied to the target client ifexplicitly requested (parameter option). Normally it does not makesense to transport such data, but is supported to permit you to copyan entire client environment.
or during installation, upgrade and language import
behavior differs here for client-specific and cross-client tables.
nt-specific tables
Classes A and C: Data is only imported into client 000. Existingdata records are overwritten.
Classes E, S and W: Data is imported into all clients. Existing datarecords are overwritten.
Class G: Existing data records are overwritten in client 000. In allother clients, new data records are inserted, but existing datarecords are not overwritten.
Class L: No data is imported.Cross-client tables
o Classes A, L and C: No data is imported.
o Classes E, S, and W: Data is imported. Exisitng data records withthe same key are overwritten.
o Classe G: Data records that do not exist are inserted, but existingdata records are not overwritten.
ehavior during transport between customer systems
Data records of tables of delivery class L are not imported into thetarget system. Data records of tables of delivery classes A, C, E, G, Sand W are imported into the target system (this is done for the targetclient specified in the transport for client-specific tables).
se of the delivery class in the extended table maintenance
The delivery class is also analyzed in the extended table maintenance(SM30). The maintenance interface generated for a table makes thefollowing checks:
o You cannot transport the entered data with the transport link of thegenerated maintenance interface for tables of delivery classes W andL.
o When you enter data, there is a check if this data violates thenamespace defined for the table in table TRESC. If the data violatesthe namespace, the input is rejected.
Method 3:
In se11->table maintainence ->check radio button standard recording routine .
Above procedure will ask for request and data can be transported to QA.
Method 4:
Go to SE10. Press F5. Enter your transport number. Put cursor on the Task(second number not the higher one). Click on the icon 'Display Object List'. Switch from display mode to change mode. Click on 'New Entries'. Enter R3TR, TABU, ZTABLENAME in the three columns.
In the menu, go to 'Extras-->Change Object Function'. Select the radiobutton for 'Entire table'. Save and exit.