delivery class

[prasanth_kasturi]

wht is meant by delivery class. plz dont give the definition in help library.....

[Former Member]

Hi,

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.

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

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.

Activation Type

The activation type defines whether the table can be activated directly from the ABAP Dictionary,

or whether the runtime object of the table must first be generated with a C program. This entry is

optional and only important for tables of the runtime environment.

The following entries are possible for the activation type:

Tables having activation type 01 cannot be activated from the ABAP Dictionary. The

runtime object must be generated using a C program. The table can then be activated

from the ABAP Dictionary. This activation type ensures that important system tables

cannot be changed and activated directly.

Tables having activation type 02 are also used in C programs. The data structure in the

C program must therefore be adjusted manually when the table is changed. There is a

relevant comment in the activation log for such tables.

Tables having activation type 10 are needed before R3TRANS runs. Such tables must

exist before all other tables when upgrading.

Tables having activation type 00 can be activated directly from the ABAP Dictionary. This

is the default setting for the activation type.

Reward points if useful.

Regards,

Keerthi vasan.M

[Former Member]

Delivery class means it decides what type of table you are going to create.ex:is it a master table or transaction table.

what type of data it is going to store in it?

what is the frequency of data change in that table?

is it needed to delete the data or overwrite the data?

depending on all these criteria tables are categorized and while designing table considering these criterias we choose delivery class.

[Former Member]

Hi,

It defines copying data between clients..........

if it is of some delivery classes, while entering data in that table thro se11...no TR is generated......normal client copy not allowed.

[Former Member]

Hi,

it will identify the owner of the table.

it will indicate which type of table is going to be created in the database i.e master or transactional

reward if usefful

rgdds

Umakanth

[Former Member]

hi prasanth,

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:

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. The customer namespace must be defined in table TRESC. (Use

Report RDDKOR54 here).

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

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

Reward if helpful.

Thank you,

Regards.