The delivery class is basically responsible for the correct execution of the following three administration activities:
Certain tables should be delivered empty (for example, spool requests)
Upgrade (with the customer)
Ensure customer objects are not overwritten. Conversely, the system table contents should reach all customer clients using client cascade.
Provide warning if application data or class L tables (for example spool requests) should be transported.
Choose tables worth copying (see below)
The delivery classes are significant for the installation, transports between systems and for client copy. They must, therefore, always be set correctly.
An incorrect allocation of delivery class can lead to a loss of data during upgrades, transports and client copy. Incorrectly set delivery classes should be corrected as soon as possible:
-> Dictionary maintenance -> Tables -> Techn.Settings .
A compact overview of table delivery classes is provided by Transaction SE16 (Data Browser) that should be used on the directory table DD02L with the following selection:
Selection value 'TRANSP' in the 'Table Type' field, as well as with additonal selections, if required.
The following matrix-type presentations explain the effects of the classes on the following functions:
Transaction: Copies clients within a local installation
SCC0 / SCC2 (only client-dependent tables)
SCCR - Remote client copy
SCC2 / SCC8 - Client export
Language import : imports foreign language texts
SAP -> customer transports: Transport from SAP Systems to customer systems
Customer -> customer transports: Transport within customer system networks