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: 

Transport Table with Data from Development to Quality

Former Member
0 Kudos

Hi

Requirement:

Transporting Table with Values from Development to Quality System.

I have a Z* - table, appended one field at the end.

I need to transport data along with the table structure from Development System to Quality System.

In Development System, I have assigned the Transport request in Client 100(We can't add data to the table in this client).

What needs to be done to migrate the new table structure with Values.

Thanks in Advance

Regards,

Baburaj

*******************************************************

NOTE: the requirement is to transport table and table entries through a transport request.

There should not be any manual update for the table in the target System (Quality System).

1 ACCEPTED SOLUTION

Former Member
0 Kudos

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.

6 REPLIES 6

former_member181962
Active Contributor
0 Kudos

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.

Regards,

ravi

0 Kudos

Check the delivery class assigned to the table. Please see the documentation

Delivery class

The delivery class controls the transport of table data when installing

or upgrading, in a client copy and when transporting between customer

systems. The delivery class is also used in the extended table

maintenance.

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 not

overwrite or delete existing data records. The customer namespace

must be defined in table TRESC. (Use Report RDDKOR54 here).

o E: System table with its own namespaces for customer entries. The

customer namespace must be defined in table TRESC. (Use Report

RDDKOR54 here.)

S: System table, data changes have the same status as program

changes.

W: System table (e.g. table of the development environment) whose

data 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 the

target client.

Classes W, L: The data records of the table are not copied to the

target client.

Class A: Data records are only copied to the target client if

explicitly requested (parameter option). Normally it does not make

sense to transport such data, but is supported to permit you to copy

an 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. Existing

data records are overwritten.

Classes E, S and W: Data is imported into all clients. Existing data

records are overwritten.

Class G: Existing data records are overwritten in client 000. In all

other clients, new data records are inserted, but existing data

records 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 with

the same key are overwritten.

o Classe G: Data records that do not exist are inserted, but existing

data records are not overwritten.

ehavior during transport between customer systems

Data records of tables of delivery class L are not imported into the

target system. Data records of tables of delivery classes A, C, E, G, S

and W are imported into the target system (this is done for the target

client 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 the

following checks:

o You cannot transport the entered data with the transport link of the

generated maintenance interface for tables of delivery classes W and

L.

o When you enter data, there is a check if this data violates the

namespace defined for the table in table TRESC. If the data violates

the namespace, the input is rejected.

Thanks,

Former Member
0 Kudos

HI,

In se11->table maintainence ->check radio button

standard recording routine .

Above procedure will ask for request and data can

be transported to QA.

Regards

Amole

Former Member
0 Kudos

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.

dave_price
Participant
0 Kudos

Thanks, helpful.

Former Member
0 Kudos

is reverse possible with from quality to developement?

if it can be,then please elaborate steps.

because accidentally  the EBAN table being deleted from developement.

Thanks.