Delivery Class 

Use

You use the delivery class to control the transport of table data for an installation, upgrade, or client copy and transports between customer systems. The delivery class is also used in the extended table maintenance.

Features

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 can insert new data records but cannot 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 Maintain Customer Namespace on the Delivery and Maintenance 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 Maintain Customer Namespace on the Delivery and Maintenance tab.

●      S- System table, data changes have the status of program changes.

●      W- System table (for example table of the development environment) whose data is transported with its own transport objects (such as R3TR PROG, R3TR TABL and so on).

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 is not sensible to transport such data, but this is supported nevertheless to allow 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. The system overwrites the existing data records.

●      Class E, S and W- Data is imported into all clients. The system overwrites the existing data records.

●      Class G- The system overwrites the existing data records in client 000. In all other clients, the system inserts new data records, 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. The system overwrites the existing data records with the same key.

●      Class G- The system inserts non-existent data records, but does not overwrite existing data records.

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 (transaction code SM30). The maintenance interface generated for a table performs 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 system rejects the input.