Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Delivery Class Changed To A

Former Member
0 Kudos

Hi All,

I have changed The Delivery Class for one of My custom Table from C to A .

Table Maintnance Gen is also availabole for this ..

Please inform , if i need to regenerate the TMG if yes what reason should i use for the regeneration .

Praveen.

2 REPLIES 2

Former Member
0 Kudos

Hi,

If a customer table ('Z' table) was originally assigned delivery class 'C' but later it is determined that the table must be modifiable (via SM30 for example) in the source system (e.g. production) without a transport, then the delivery class 'A' is needed.

Refer below theard and check the answer given by amit

https://forums.sdn.sap.com/click.jspa?searchID=4270923&messageID=2403752

Regards

Former Member
0 Kudos

Hi

see the doc of the delivery class

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.

We generally use C for customer to enter data into the table

when you change it to Application table (A) you have to regeenrate and to give the access for entering the data

see the table maintenance generator doc

table maintanance Generator is used to manually

input values using transaction sm30

follow below steps

1) go to se11 check table maintanance check box under

attributes tab

2) utilities-table maintanance Generator->

create function group and assign it under

function group input box.

also assign authorization group default &NC& .

3)

select standard recording routine radio in table

table mainitainence generator to move table

contents to quality and production by assigning

it to request.

4) select maintaience type as single step.

5) maintainence screen as system generated numbers

this dialog box appears when you click on create

button

6) save and activate table

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

http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm

/message/2831202#2831202 [original link is broken]

One step, two step in Table Maintenance Generator

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

<b>Reward points for useful Answers</b>

Regards

Anji