Delivery Class in ABAP Tables

Delivery Class in ABAP Tables

In Data Class we have specified the Type of Data we will be using for our table, in Size Category we have declared the expected Volume of Data we will be saving. Now, we need to define the way the Data in the table behaves. It means whether data can be moved from one Landscape/system to other or not. It is achieved using Delivery Class in ABAP Tables.

*NOTE: Although the Delivery Class is declared before Data Class and Size Category, still it is advisable to read about it after them.

Definition

A delivery class defines:

  • Transport control of Data within Landscapes and customer systems
  • Transport control of Data for an installation or upgrade
  • Transport control of Data of client copy
  • Data can be maintained in Extended Table Maintenance [SM30] or not.

In short we can say a delivery class determines whether data of the table can be maintained & transported or not.

Delivery Class

Types of Delivery Class

TYPETABLE TYPEDESCRIPTIONTABLE BEHAVIOUR DURING CLIENT COPYTABLE BEHAVIOUR During Installation, Upgrade and Language Import
AApplication table (Master and Transaction data)Master and Transaction data is maintained by SAPData is copied only if requested

·         Cross-Client Tables : No Data Imported

·         Client-Dependent Tables: Data Imported into Client 000.

CCustomer tableData is only maintained only  by CustomerData is copied to the target client

·         Cross-Client Tables : No Data Imported

·         Client-Dependent Tables: Data Imported into Client 000.

GCustomer tableSAP can only Insert data & cannot modify/DeleteData is copied to the target client

·         Cross-Client Tables : Imported and cannot be overwritten

·         Client-Dependent Tables: Imported and can be overwritten only for CLIENT 000.

LTemporary tableTable to story only temporary dataData are not copied to the target client

·         Cross-Client Tables : No Data Imported

·         Client-Dependent Tables: No Data Imported.

ESystem tableTable with own namespace(in table TRESC) for customer entriesData is copied to the target client

·         Cross-Client Tables: Imported and can be overwritten with same key.

·         Client-Dependent Tables: Imported and can be overwritten.

SSystem tableTable with status of Data changesData is copied to the target client

·         Cross-Client Tables: Imported and can be overwritten with same key.

·         Client-Dependent Tables: Imported and can be overwritten.

WSystem tableTable whose Data is Transported via its own Transport ObjectsData are not copied to the target client

·         Cross-Client Tables: Imported and can be overwritten with same key.

·         Client-Dependent Tables: Imported and can be overwritten.

*NOTE: Client Dependent Tables are tables with MANDT field and any changes in the table will impact only one Client while Client Independent Tables are also called Cross Client Table which does not have MANDT field and hence any changes will impact all the clients in the server.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.