topic diff between data class and delivery class in Application Development and Automation Discussions

diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 05:21:44 GMT

diff between data class and delivery class

Re: diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 05:33:15 GMT

Hi,

Based on Delivery class, space will be allocated to the table in number of extents.

Data class is used to determine where the data has to be stored in the allocated TABLE SPACE.

Regards,

Raghavendra

Re: diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 06:43:44 GMT

Hi Karthik,

What is a Data Class?

The Data class determines in which table space the table is stored when it is created in the database.

There are five size categories (0-4) and 11 data classes only three of which are appropriate for application tables:

· APPL0- Master data (data frequently accessed but rarely updated).

· APPL1- Transaction data (data that is changed frequently).

· APPL2- Organizational data (customizing data that is entered when system is configured and then rarely changed).

The other two types are:

· USR

· USR1 – Intended for customer’s own developments.

What is the significance of Delivery Class?

· The delivery class controls the degree to which the SAP or the customer is responsible for table maintenance.

· Whether SAP provides the table with or without contents.

· Determines the table type.

· Determines how the table behaves when it is first installed, at upgrade, when it is transported, and when a client copy is performed.

What is the significance of Technical settings (specified while creating a table in the data dictionary)?

By specifying technical settings we can control how database tables are created in the database. The technical settings allows us to

· Optimize storage space requirements.

· Table access behavior.

· Buffering required.

· Changes to entries logged.

Reward points if useful,

Aleem.

Re: diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 08:30:36 GMT

Hi ,

u can better information from F1 go to the tab press F1.

1)---> Data class

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.

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

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

Thanks

Message was edited by:

Pattan Naveen

Re: diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 10:41:51 GMT

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

Development class is to store a group of objects under single 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.

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

Behavior during Client Copy

Only the data of client-dependent tables is copied.

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

Class 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). It normally does not make sense to transport such data, but this is supported nevertheless to permit the entire client environment to be copied.

Behavior during Installation, Upgrade and Language Import

The behavior of client-dependent tables differs from that of cross-client tables.

Client-Dependent Tables

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

Class 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. Existing data records with the same key are overwritten.

Class G: Non-existent data records are inserted, but no existing data records are overwritten.

Behavior during Transport between Customer Systems

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

Use of the Delivery Class in the Extended Table Maintenance

The delivery class is also 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.

<b>Reward if useful</b>

Re: diff between data class and delivery class

Former Member — Wed, 03 Oct 2007 10:42:57 GMT

1.The Data class determines in which tablespace the table is stored when it is created in the database. What is a Size Category? The Size category describes the probable space requirement of the table in the database. How Many types of size categories and data classes are there? There are five size categories (0-4) and 11 data classes, only three of which are appropriate for application tables:

The delivery class controls the degree to which the SAP or the customer is responsible for table maintenance

- whether SAP provides the table with or without contents.

- determines the table type. - determines how the table behaves when it is first installed, at upgrade, when it is transported, and when a client copy is performed

4 .A work process is where individual dialog steps are actually processed and the work is done. Each work process handles one type of request.

<b>Reward if usefull</b>