Data class - Delivery class

[Former Member]

What are the types of Data class and Delivery class in Data dictionary?

What exactly is the Delivery class?

[Former Member]

HI,

Types of data class

APPL0 Master data, transparent tables

APPL1 Transaction data, transparent tables

APPL2 Organization and customizing

USER Customer data class

USER1 Customer data class

USER6 Customer data class, generated by SAPDBA

USER7 Customer data class, generated by SAPDBA

Delivery Class categorize the table. That means it defines what kind of table you are going to create.

If the delivery class is C then it means the table is a Customizing table. If the delivery class is A then it means its transaction data.

So delivery class defines what kind of table or what kind of information is going to be stored.

[prasanth_kasturi]

Hi,

we can say Delivery class gives the owner of the table,

i.e one who maintains data in it

if you want the list in the corresponding fields pres f4 or f1

delivery class

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

dataclass

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_nw04/helpdata/en/cf/21eac5446011d189700000e8322d00/content.htm

regards

prasanth

[Former Member]

Hi,

Delivery Class categorize the table. That means it defines what kind of table you are going to create.If the delivery class is C then it means the table is a Customizing table. If the delivery class is A then it means its transaction data. So delivery class defines what kind of table or what kind of information is going to be stored.

[Former Member]

Hi,

We have 3 types of Data Classes

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

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

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

Delivery class:

The delivery class of a maintenance view is used in the Extended Table Maintenance (SM30). If a maintenance interface is generated for the maintenance view, the following information is analyzed when view data is entered for this interface:

For maintenance views having delivery class E or G, there is a check if the entered data satisfies the namespace defined in table TRESC for the view.

There is a check if the transport connection built into the generated table maintenance makes sense. For example, there is no transport for maintenance views with delivery classes L and W.

I hope it is help for you

Thanks,

Murali

[Former Member]

Hi,

Delivery class

The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.

There are the following delivery classes:

A: Application table (master and transaction data).

C: Customer table, data is maintained by the customer only.

L: Table for storing temporary data.

G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here).

E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.)

S: System table, data changes have the same status as 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.).

Behavior during client copy

Only the data of client-specific tables is copied.

Classes C, G, E, S: The data records of the table are copied to the target client.

Classes 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). Normally it does not make sense to transport such data, but is supported to permit you to copy an entire client environment.

Behavior during installation, upgrade and language import

The behavior differs here for client-specific and cross-client tables.

Client-specific tables

Classes A and C: Data is only imported into client 000. Existing data records are overwritten.

Classes E, S and W: Data is imported into all clients. Existing data records are overwritten.

Class G: Existing data records are overwritten in client 000. In all other clients, new data records are inserted, 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. Exisitng data records with the same key are overwritten.

Classe G: Data records that do not exist are inserted, but existing data records are not overwritten.

Behavior during transport between customer systems

Data records of tables of delivery class L are not imported into the target system. Data records of tables of delivery classes A, C, E, G, S and W are imported into the target system (this is done for the target client specified in the transport for client-specific tables).

Use of the delivery class in the extended table maintenance

The delivery class is also analyzed in the extended table maintenance (SM30). The maintenance interface generated for a table makes the following checks:

You cannot transport the entered data with the transport link of the generated maintenance interface for tables of delivery classes W and L.

When you enter data, there is a check if this data violates the namespace defined for the table in table TRESC. If the data violates the namespace, the input is rejected.

Data class

The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the correct area when it is created on the database.

The most important data classes are (other than the system data):

APPL0 Master data

APPL1 Transaction data

APPL2 Organizational and customizing data

Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently updated.Organizational und customizing data is data which is defined when the system is initialized and then rarely changed.

There are two more data classes available, USR and USR1. These are reserved for user developments. The tables assigned to these data classes are stored in a tablespace for user developments.

Note:The data class only has an effect on table storage for the database systems ORACLE and INFORMIX.

Rgds

Yogesh

[GauthamV]

hi,

Data class in technical settings

The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the correct area when it is created on the database.

The most important data classes are (other than the system data):

APPL0 Master data

APPL1 Transaction data

APPL2 Organizational and customizing data

Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently updated. Organizational und customizing data is data which is defined when the system is initialized and then rarely changed.

There are two more data classes available, USR and USR1. These are reserved for user developments. The tables assigned to these data classes are stored in a tablespace for user developments.

Delivery class

The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.

There are the following delivery classes:

A: Application table (master and transaction data).

C: Customer table, data is maintained by the customer only.

L: Table for storing temporary data.

G: Customer table, SAP may insert new data records, but may not overwrite or delete existing data records. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here).

E: System table with its own namespaces for customer entries. The customer namespace must be defined in table TRESC. (Use Report RDDKOR54 here.)

S: System table, data changes have the same status as 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.).

[Former Member]

Hi

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.

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.

E: System table with its own namespace for customer entries. The customer namespace must be defined in table TRESC.

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

W: System table .

The delivery class is used in the Extended Table Maintenance (SM30). The maintenance interface generated for a table makes 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 input is rejected.

Hope it helps you

Regards

Indu

[avinash_s2]

Delivery class: A, C, L, G, E, S, W

DataClass: APPL0, APPL1, APPL2