Delivery Class?

[Former Member]

When I created table in SAP, There are several options for Delivery Class field, what's the Difference:

A - Application table (mastr and transaction data)

c - Customizing table, maintenace only by cust.not SAP import)

[Former Member]

When I created table in SAP, There are several options for Delivery Class field, what's the Difference:

A - Application table (mastr and transaction data)

c - Customizing table, maintenace only by cust.not SAP import)

[Former Member]

A is for Application table which holds master and transaction data. The system (thru SM30)

won't ask for a request.

2. It will only ask in case of C

check this link

http://help.sap.com/saphelp_nw04/helpdata/en/43/45860774b711d2959700a0c929b3c3/content.htm

[Former Member]

Hi

See the documentation provided by SAP for delivery class.

Regards,

Raj

<b>Delivery class</b>

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:

A: Application table (master and transaction data).

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

L: Table for storing temporary data.

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).

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.).

<b>Behavior during client copy</b>

Only 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.

<b>Behavior during installation, upgrade and language import</b>

The behavior differs here for client-specific and cross-client tables.

Client-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

Classes A, L and C: No data is imported.

Classes E, S, and W: Data is imported. Exisitng data records with the same key are overwritten.

Classe G: Data records that do not exist are inserted, but existing data records are not overwritten.

<b>Behavior during transport between customer systems</b>

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).

<b>Use of the delivery class in the extended table maintenance</b>

The delivery class is also analyzed in the extended table maintenance (SM30). The maintenance interface generated for a table makes the following checks:

You cannot transport the entered data with the transport link of the generated maintenance interface for tables of delivery classes W and L.

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.

Message was edited by: Rajasekhar Dinavahi

[Former Member]

Hi Rajesekhar

Noted that for Client-specific tables

Classes A and C: Data is only imported into client 000. Existing data records are overwritten.

how can I then copy from client 000 to client 100 which is my Production client?

Can you please advice urgently.

Thanks.

[Former Member]

hi,

Help from SAP

<b>Delivery Class</b>

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.

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</b>

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>Behavior during Installation, Upgrade and Language Import</b>

The behavior of client-dependent tables differs from that of cross-client tables.

Client-Dependent Tables

Class A and C: Data is only imported into client 000. Existing data records are

overwritten.

Class 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

Classes A, L and C: No data is imported.

Classes E, S, and W: Data is imported. Existing data records with the same key are

overwritten.

Class G: Non-existent data records are inserted, but no existing data records are

overwritten.

<b>Behavior during Transport between Customer Systems</b>

Data records of tables having delivery class L are not imported into the target system. Data

records of tables having delivery classes A, C, E, G, S and W are imported into the target system

(for client-dependent tables this is done for the target clients specified in the transport).

<b>Use of the Delivery Class in the Extended Table Maintenance</b>

The delivery class is also used in the Extended Table Maintenance (SM30). The maintenance interface generated for a table makes the following checks:

It is not possible to transport the entered data using the transport connection of the

generated maintenance interface for tables having delivery classes W and L.

Data that is entered is checked to see if it violates the namespace defined in table

TRESC. If the data violates the namespace, the input is rejected.

Regards,

Sailaja

[Former Member]

C- Customized table option will be selected when the data is maintained by the enduser/Functional guys in the table. For this we are going to create a table maintainace and then the data will be updated through SM30.

Where as in Appilcation table data will be maintained through the programs or Online transaction codes.