Data Class
The data class determines the physical area of the database (tablespace) in which the table is created.
You set the data class in the technical settings for the table.
There are 5 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 - Customer Data class
· USR1 – Customer data class - Intended for customer’s own developments.
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.
There are the following development classes: A, S, C, L
* 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.)
The data class determines the physical area of the database (tablespace) in which the table is created.
You set the data class in the technical settings for the table.
There are 5 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 - Customer Data class
· USR1 – Customer data class - Intended for customer’s own developments.
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.
There are the following development classes: A, S, C, L
* 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.)
No comments:
Post a Comment