topic Re: tables in Application Development and Automation Discussions

tables

Former Member — Mon, 20 Aug 2007 12:58:38 GMT

when can we use delivery class as customizing / application while table creation

Re: tables

Former Member — Mon, 20 Aug 2007 13:10:41 GMT

Hi shital,

Just go thrugh this u definetly understand.

Delivery class

The delivery class controls the transport of table data when installin

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:

o A: Application table (master and transaction data).

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

o L: Table for storing temporary data.

o G: Customer table, SAP may insert new data records, but may not

overwrite or delete existing data records.

o E: System table with its own namespaces for customer entries. The

customer namespace must be defined in table TRESC.

o S: System table, data changes have the same status as program

changes.

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

ehavior during client copy

Only the data of client-specific tables is copied.

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

target client.

o Classes W, L: The data records of the table are not copied to the

target client.

o 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

o Classes A and C: Data is only imported into client 000. Existing

data records are overwritten.

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

records are overwritten.

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

o Class L: No data is imported.

Cross-client tables

o Classes A, L and C: No data is imported.

o Classes E, S, and W: Data is imported. Exisitng data records with

the same key are overwritten.

o 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:

o You cannot transport the entered data with the transport link of the

generated maintenance interface for tables of delivery classes W and

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

Reward points if helpful.

Thanks

Naveen khan

Re: tables

Former Member — Mon, 20 Aug 2007 13:40:35 GMT

Delivery Class Locate the document in its SAP Library structure

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.

regards,

srinivas

*reward for useful answers*

Re: tables

Former Member — Mon, 20 Aug 2007 14:49:55 GMT

Hi,

Delivery class is used to specify the table type. For example transparent table or cluster table. we will have different types of delivery classes like A ,C, L, G, E, S, W. if we want to do any modification to the existing table then we will use customizing table.

Reward points if it is useful....

Thanks & Regards,

Vasudeva Rao.