Reg - Data class & 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.

http://help.sap.com/saphelp_nw04/helpdata/en/43/45860774b711d2959700a0c929b3c3/content.htm

If you choose the data class correctly, your table is automatically assigned to the correct area (tablespace or DBspace) of the database when it is created. Each data class corresponds to a physical area in which all the tables assigned to this data class are stored.

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eac5446011d189700000e8322d00/content.htm

hi

Data Class

If you choose the data class correctly, your table is automatically assigned to the correct area (tablespace or DBspace) of the database when it is created. Each data class corresponds to a physical area in which all the tables assigned to this data class are stored. There are the following data classes:

APPL0 (master data): Data which is seldomly changed. An example of master data is the data contained in an address file, such as the name, address and telephone number.

APPL1 (transaction data): Data that is frequently changed. An example of transaction data is the goods in a warehouse, which change after each purchase order.

APPL2 (organizational data): Customizing data that is defined when the system is installed and seldomly changed. An example is the table with country codes.

Two further data classes, USR and USR1, are provided for the customer. These are for user developments. The tables assigned to these data classes are stored in a tablespace for user developments.

http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/054d3c2ec42c01e10000000a114084/content.htm

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. 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 Customer namespace definition on the Attributes 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 Customer namespace definition on the Attributes tab.

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

http://help.sap.com/saphelp_nw04/helpdata/en/43/45860774b711d2959700a0c929b3c3/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/80/808b5ae12511d295f300a0c929b3c3/content.htm

<b>rEWARD IF USEFULL</b>