about delivery class

[Former Member]

please can u explain me details regarding delievery class

we normally accept A Application

When to use other and wat they conprise off

A Application table (master and transaction data)

C Customizing table, maintenance only by cust., not SAP import

L Table for storing temporary data, delivered empty

G Customizing table, protected against SAP Upd., only INS all.

E Control table, SAP and customer have separate key areas

S System table, maint. only by SAP, change = modification

W System table, contents transportable via separate TR objects

waiting friends

With Best Regards

Ruby

[Former Member]

Hi Ruby,

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.

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. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

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

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.

Behavior during Installation, Upgrade and Language Import

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.

Behavior during Transport between Customer Systems

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

Use of the Delivery Class in the Extended Table Maintenance

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.

Hope this helps u..

****Reward points if helpful.

Regards,

Pavithra

[Former Member]

Hi Ruby,

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.

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. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

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

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.

Behavior during Installation, Upgrade and Language Import

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.

Behavior during Transport between Customer Systems

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

Use of the Delivery Class in the Extended Table Maintenance

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.

Hope this helps u..

****Reward points if helpful.

Regards,

Pavithra

[Former Member]

Friends

Do u people practically use other delevery classes except A Application

and if practically u could explain me

i got the theory part

With Best Regards

Ruby

[Former Member]

Hi Ruby...

Yes v do use other delivery classes too.

A is used when ur table is application table to hold master data.

When u are asked to create a ztable for a specific client requirement, they wud b Customizing table "C".Thats bcoz, the clinet mite b doing some updation in the later stages of the SAP implementation.

I have used only A and C tables in the real time projects i worked.

Hope this helps u

***Reward points if useful.

All the best.

Regards,

Pavithra

[Former Member]

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

Regards

Prax

Generally we use type A and C...

[Former Member]

hi ruby,

Delivery class tells who is the owner of the table, A as application table likewise remaining are self explanatory. Like S sytem table.

[Former Member]

The delivery class controls the transport of table data for installation, upgrade, client copy and when transporting between customer systems.

<b>we normally accept A Application becuase</b>

<b>1.Behavior during Client Copy</b>

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

<b>A.Client-Dependent Tables</b>

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

<b>B.Cross-Client Tables</b>

Classes A : No data is imported.

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

reward points if it is usefull....

Girish

[Former Member]

Hi,

<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. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC. To define the customer namespace use report RDDKOR54. You can start it directly from the table maintenance by choosing Customer namespace definition on the Attributes tab.

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.

Pls reward points.

Regards,

Ameet