topic DATA IN TRANSPORT REQUEST in Application Development and Automation Discussions

DATA IN TRANSPORT REQUEST

Former Member — Tue, 22 May 2007 05:34:42 GMT

Hi Friends,

I have created transport request for a particular package, now i want to know that after transporting this request to other production server , my tables and other dictionary objects will contain all the data or i have to manually enter all the data again.

Thanks,

Sunny

Re: DATA IN TRANSPORT REQUEST

Former Member — Tue, 22 May 2007 05:36:14 GMT

HI,

the other system will have all data when u send it with transport request.. u dont need to upload again manually

Reward if it helpful

Regards

SAB

Re: DATA IN TRANSPORT REQUEST

Former Member — Tue, 22 May 2007 05:37:22 GMT

Hi Sunny,

What ever data is transfered using TR will be available in the next system.

Reward points if useful.

Regards,

Atish

Re: DATA IN TRANSPORT REQUEST

Former Member — Tue, 22 May 2007 05:44:23 GMT

DONE

Re: DATA IN TRANSPORT REQUEST

alejandro_bindi — Tue, 22 May 2007 05:47:10 GMT

That actually depends on the Delivery class set for the table.

This is taken from data dictionary help:

<b>Delivery Class

The delivery class controls the transport of table data for installation, upgrade, client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.</b>

There are the following development classes:

A: Application table (master and transaction data).

C: Customer table, data is only maintained by the customer.

L: Table for storing temporary data.

G: Customer table, SAP may insert new data records but may not overwrite or delete

existing ones.

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

must be defined in table TRESC.

S: System table, data changes have the status of 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.).

<b>Behavior during Client Copy

Only the data of client-dependent tables is copied.

Class C, G, E, S: The data records of the table are copied to the target client.

Class 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). It normally does not make sense to transport such data, but this is

supported nevertheless to permit the entire client environment to be copied.

</b>

In general A or C are used.

Please award points if useful.