Get Example source ABAP code based on a different SAP table
ABAP_DDIC - Delivery Class of Database Tables The delivery class of a DDIC database table controls the transport of table data in installations, upgrades, or client copies, and in transports between customer systems. BEGIN_SECTION VERSION 5 OUT The delivery class is also respected in extended table maintenance (transaction code SM30). END_SECTION VERSION 5 OUT
Delivery class A Application table for master data and transaction data. The data is written by application programs.
An application table is delivered as an empty table or with a template for real data in client 000.
In client copies, the data in client-dependent tables is copied only if the corresponding flag is set in the client copy profile. Any client-independent data is not copied.
In installations, updates, and language imports, the data in client-dependent tables is only imported into the system client with the client ID 000, overwriting any existing data. Any client-independent data is not imported.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected. BEGIN_SECTION VERSION 5 OUT
Delivery class C END_SECTION VERSION 5 OUT BEGIN_SECTION VERSION 5 ONLY
Delivery classes C and G END_SECTION VERSION 5 ONLY Customizing table for data maintained exclusively by the customer.
Client-dependent customizing tables can be delivered with patterns for real data.
In client copies, the data of client-dependent tables is copied. Any client-independent data is not copied.
In installations, updates, and language imports, the data in client-dependent tables is only imported into the system client with the client ID 000, overwriting any existing data. Any client-independent data is not imported.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected. BEGIN_SECTION VERSION 5 ONLY The delivery class G is obsolete and occurs only for existing tables. It can no longer be specified. Tables with delivery class G are handled like delivery class C implicitly. END_SECTION VERSION 5 ONLY
Delivery class L Table for local data of each ABAP system. SAP delivers tables in the delivery class L as empty tables.
These tables are delivered as empty tables.
No data is copied in client copies.
No data is imported in installations, updates, and language imports.
No data is transported in transports between customer systems. BEGIN_SECTION VERSION 5 OUT
Data entered using extended table maintenance (transaction code SM30) cannot be transported. END_SECTION VERSION 5 OUT Global temporary tables always have the delivery class L. BEGIN_SECTION VERSION 5 OUT
Obsolete delivery class G Customizing table where SAP can add data but not modify or delete it. A customizing table in the delivery class G must be assigned a customer namespace in the DDIC database table TRESC using the program RDDKOR54. The delivery class G can no longer be specified for new DDIC database tables and when changing the delivery class of an existing table. The delivery class C can be used instead. On an AS ABAP used in an SAP Cloud solution, tables with delivery class G are handled like delivery class C implicitly.
Customer tables can be delivered with patterns for real data.
In client copies, the data of client-dependent tables is copied. Any client-independent data is not copied.
In installations, updates, and language imports, the data in client-dependent tables is imported as follows: in system clients with the client ID 000, all data is imported, and existing data is overwritten. In other clients, only new data is imported, and no existing data is overwritten. Any client-independent data is inserted without overwriting existing data.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected.
Data entered using extended table maintenance (transaction code SM30) is checked for any violations of the namespace assigned in the DDIC database table TRESC. The delivery class G can no longer be specified for new DDIC database tables and when changing the delivery class of an existing table. The delivery class C can be used instead. On an AS ABAP used in an SAP Cloud solution, tables with delivery class G are handled like delivery class C implicitly. END_SECTION VERSION 5 OUT
Delivery class E System table in which customers can make entries. A system table in the delivery class E must be assigned a customer namespace in the database table TRESC using the program RDDKOR54.
These system tables are delivered with prefilled entries.
In client copies, the data of client-dependent tables is copied. Any client-independent data is not copied.
In installations, updates, and language imports, all data is imported, and existing data is overwritten.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected. BEGIN_SECTION VERSION 5 OUT
Data entered using extended table maintenance (transaction code SM30) is checked for violations of the namespace assigned in the DDIC database table TRESC. END_SECTION VERSION 5 OUT
Delivery class S System table delivered by SAP as part of the system. Contains predefined data. An example is the table ABAPDOCU_NODES with the read-only tree of the ABAP keyword documentation. In the Change and Transport Systems (CTS), the data is handled like repository objects, which means that they have an original system and any changes in other systems are modifications or repairs.
These system tables are delivered with prefilled data.
In client copies, the data of client-dependent tables is copied. Any client-independent data is not copied.
In installations, updates, and language imports, all data is imported and existing data is overwritten.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected.
Delivery class W System table for system administration data, such as TFDIR as a directory of all function modules. A system table in the delivery class W is usually delivered with prefilled data by SAP and can be modified by customer modifications. The content is transported using transport objects assigned to the managed objects, such as R3TR FUNC for function modules.
These system tables are delivered with prefilled entries.
No data is copied in client copies.
In installations, updates, and language imports, all data is imported, and existing data is overwritten.
In transports between customer systems, all data is transported. In client-dependent tables, only the data in the specified target client is respected. BEGIN_SECTION VERSION 5 OUT
Data entered using extended table maintenance (transaction code SM30) cannot be transported. END_SECTION VERSION 5 OUT
Latest notes:
For more information about transports and client copies, see the documentation Change and Transport System on SAP Help Portal. NON_V5_HINTS
It is not recommended that table content is transported for which a replacement object is defined. ABAP_HINT_END
