Data maintenance in a table of delivery class S

Hi,
If i have to maintain en entry in a table with delivery class S (System table, maint. only by SAP) , can i do it in any client
or only system maintenance client.
Regards,
sushant

hi
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.
Hope this information is useful to you.
Regards
Vinodh A

Similar Messages

Customer table with delivery class 'A' asking for a request

Hello.
I've built an customer table and defined the delivery class 'A' ... Application table (master and transaction data).
Data Browser/Table View Maint. 'X' ... Display/Maintenance Allowed.
Why is this type of table definition asking for a change request to store table entries?
Please, provide some help.
Mário Semedo

Thanks ... how did i let it pass?
Thanks alot!

Data Maintenance For Pooled Table

Hi,
I have to make table maintenance for pooled table T052S , Can I make table maintenace , if I have access key, is it feaseable, as I have some requirement , which is to be done. or is there any other method by which user can maintain this table except through SPRO.
thanks
bobby

We're on ECC 5.0 here and this table already has a maintenance transaction defined - OBB9.
This is how SAP sets up maintenance for a lot of the config tables:
     Define a Maintenance View - e.g. V_T052S
     Define a Maintenance Dialog
     Define a transaction variant on SM30
A user can be given maintenance access for only OBB9

Delivery Class Changed To A

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.

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.
Reward points for useful Answers
Regards
Anji

About Delivery class

HI All,
In DDIC,in tables the Delivery class 'L' is for what purpose.Explain me about this delivery class
Thanks In Advance

Hi,
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.
Regards,
Jagadish

Delivery class

which purpose we use DELIVER CLASS plz tell me in
general terminalogy.not in technical

Hi,
Delivery class is the one which controls the table, while upgrading, maintaining and copying.
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.
Regards,
Satish

Can I TRansport a table entry of LTDX, which DELIVERY CLASS is E, ALLOWED?

Hi Experts,
se16> LTDX->specified the prog. name as RFITEMGL>selected my 3 entries of the alv lay out varinats--->MENU> TRANSPORT ENTRIES--> system asking me the TRansport #--
> created a TR #
So, pls. let me know that, R they transport as normal TRansports? coz, the table LTDX DELIVERY CLASS is "E" type & DIAPLY & MAINTAINANACE ALLOWED??????? and there is NO SM30 for this table!!!!!!!!
thanq

I have already parsed the HTML and checked all the closing of tags and corrected the indent using Tidy and then I have applied this code so some other suggestions please

Custom table - delivery class?

I need to create a z-table to list the email-ids that I want to notify to, in case of program errors. Should I make the delivery class of this table 'C'? And is best practise to make the data transportable? Or should my users just enter data in each system.
I am kind of confused...Could any of you please clear me on this concept of Deliver class please. Your help is very much appreciated.
thanks!

Vishnu,
Did you try? I tried these things long back and documented the behavior
May be you tried it very long back, indeed. Atleast for releases > ECC6.0 EhP3 client-independent customizing tables prompt for WB requests.
... C, G, and E will only trigger customizing requests ....
Unfortunately you're wrong! Did you check the transaction FILE? All the tables involved are of Delv. Class 'G'; but still when you try to save a logical file it asks for a WB request, ever wondered why?
Still not convinced, check [this|https://picasaweb.google.com/lh/photo/kBwoENEIkUTsGuJUTn9Q5tMTjNZETYmyPJy0liipFm0?feat=directlink]!
Suhas Saha wrote. "Customizing TRs are raised for client-dependent tables & workbench for client-independent ones!"
This was w.r.t customizing tables & not application tables, as you were talking about customizing tables in your previous response.
I can create a table with MANDT assign delivery class A or S and can trigger workbench requests on it.
I know it does. IMHO type 'A' tables are for storing master and/or transational data & it does not make sense to transport these data. For e.g., BKPF is type 'A' & not transportable, but T001 is type 'C' & transportable.
If i want to transport the data across my landscape i would make it 'C' & not 'A'.
BR,
Suhas

Data class and Delivery class in ABAP Dictionary

Hi all,
I want to know the exact information about Data class and Delivery class in ABAP Dictionary
Moderator message : Search for available information. Thread locked.
Edited by: Vinod Kumar on Aug 3, 2011 1:35 PM

As your name Suggests, there were exactly 21 rajapandian already who wanted exact information about Data class and Delivery class. Fortunately some has found the information by own and some were dumped by SAP Police.
Cheers
Amit

Difference between Data Class and Delivery Class

What is the Difference between Data Class and Delivery Class , what happens Phisically to the Data .
Moderator message: what is the difference between your question and a question that we'd welcome here in the forums?
[Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
Edited by: Thomas Zloch on Nov 22, 2010 1:17 PM

What is the Difference between Data Class and Delivery Class , what happens Phisically to the Data .
Moderator message: what is the difference between your question and a question that we'd welcome here in the forums?
[Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
Edited by: Thomas Zloch on Nov 22, 2010 1:17 PM

Data base tables for delivery & post goods issue

Hi,
can u plz tell me which database tables are going to update after the delivery is completed?
which database tables are going to update after post goods issue.
Thanks for ur help.
Regards
pabitra

Hi,
Check the folowing tables:
LIKP : Delivery header
LIPS : Delivery items
VTTP : Shipment item
VTTK : Shipment header
VBFA : Document flow
VBUK : Header status
VBUP : Item status
Regards,
Santhosh

Change Delivery Class of ZTable

We currently have a ZTABLE that is defined as Delivery Class 'A'. In each system (DEV, QAS, PRD) we modify the table using a Table Maintenance View and SM30. We now have a requirement to enforce promotion of the Data in the table from DEV to QAS to PRD. In my experiments, Delivery Class 'C' will provide this functionality; however, I am not sure if it is possible (or advisable) to change the Delivery Class of a Table already promoted to Production.
Has anyone had any experience with changing the Delivery Class of an existing table?
I've checked online documentation for Delivery Classes; so far this has explained how to initially choose a Delivery Class, but there has been no information on changing a Delivery Class or statements stating not to change the Delivery Class of a table. In addition I have Googled "SAP Change Delivery Class", "SAP Table Class" and "SAP Delivery Class"; these searches have yielded no results that answer this question.
The other option I am looking at involves building a new table with an identical structure of the Delivery Class 'C', then changing each application to read the new table instead of the existing table.
Any help and/or opinions will be appreciated.
Thank you,
Steven Coolbaugh

>
Steven Coolbaugh wrote:
> We currently have a ZTABLE that is defined as Delivery Class 'A'. In each system (DEV, QAS, PRD) we modify the table using a Table Maintenance View and SM30. We now have a requirement to enforce promotion of the Data in the table from DEV to QAS to PRD.
Hello Steven,
Whether or not table entries can be transported does not depend upon the "delivery class".
In my experiments, Delivery Class 'C' will provide this functionality
AFAIK this won't help. If the delivery class of the table is 'C', then you have to use a customizing request to transport the entries. To make the entries transportable you have to activate the "standard recording routine" radio-button in the table maintenance generator.
Hope this helps.
BR,
Suhas

Maintenance view problem "No data maintenance Authorization; Display only"

Maintenance view problem
Question 1>>>>
> I have created a table with Display/maintenance allowed and technical setting Data class - APPL0 (master data, transparent tables).
>> Then I have created a maintenance view thought utilities->table maintenance generator where i have specified the Authorization group as &NC& (w/o auth. group)
->and also created a function group and specified in the maintenance screen-> I have selected maintenance type as one step-> i have given the overview screen number->and in Recording routine i have selected - no, or user ,recording routine.
>>> Now when i go to transaction SM30 and put the table name and press on maintain button I get a information box saying "No data maintenance Authorization; Display only".... and it only displays the data.
my problem is I want to enter data through maintenance view (SM30).
2nd Question >>>> once i create a function group for maintenance view how can i assign a transaction for this. (as if i do it as we do for a module pool program it gives me error)Thank you.
kailash

SE93. Enter a transaction name. Create. In the pop up enter a title and select 'Transaction with parameters'.
Next screen fill the following;
Transaction 'SM30'
Check 'Skip first screen'
In the table control at the bottom of the screen
Name of screen field 'VIEWNAME'
Value <your table name>
Name of screen field 'SHOW'
Value 'X'
Save.
Job done.

Data Maintenance view exist - but unable to modify data in SM30.

Dear all,
Had created a customized table, with "Display/Maintenance Allowed". Table maintenance is also generated. So data in the customized table can now be maintained via SM30 in the Development server.
However, when the customized table is transported into Testing server -- when attempting to modify the table in SM30,
an info message pop up stating "Client 003 has status not modifiable". With that, could not maintain the table directly.
Kindly shed so light on the matter above.
Thanks in advance.

Your table maintenace generated is flaggedas 'Standard recording routine' - check in - table maintenance -> 'Dialog data transport details'.
If you want to allow to maintain in QA or in Prod box please set the flag to 'no, or user, recording routine' .

What is the field and Table for "Batch Class" and "Class Type" in QM.

Hi All,
What is the field and Table for "Batch Class" and "Class Type" in QM.
Thanks,

Hi,
For batch class the class type value is '023' . This you can find from KLAH table and the fileld for class type is KLART..
And also all the data related to batch class are found in tables INOB, KLAH,KKSK and for the characeteristics of batch materials you can refer AUSP table.
In INOB table, for batch class, you need to give 023 in KLART field and value MCH1 in OBTAB filed.
Please check this and let me know if this you need any more details?

Data maintenance in a table of delivery class S

Similar Messages

Maybe you are looking for