Table maintenance in production

Hello Folks,
We have setup SM30 access to users to update Z tables in production. How do we get them to update it without the need for a transport request in Production each time they maintain it?
Is there some setting in SE06 that we need to setup for all custom tables?
Thanks
Prakash

Hi Prakash,
You will require to change the properties of Table Maintainance Generator:
1) Go to SE11, Display table
2) Click on "Utilities" -> "Table Maintainance Generator"
3) For Recording Routine select 2nd radio button i.e. "no, or user, recording routine"
and Activate the Maintainace.
Now if you add the table entry it will not ask for transport. You have to move these changes to Production to take effect.
Hope this answers your query.
Regards
Shital

Similar Messages

Table Maintenance(SM30) not working for a custom View..

Hi,
I have the below case which is not working at the moment.
we have standard table T024 and the requirement is to update the table directly in production. To update the standard table i have created a custom maintenance view on this table and created a table maintenance generator for custom view.
In maintenace status tab of view i have maintened below information:
Access                                                 read, change, delete and insert
Delivery class                                       A
Data Browser/Table View Maint.         Display/ Maintenance allowed
The table maintenace generator has been also created but when trying to modify it is giving below message
"Client 210 has status 'not modifiable"
We have two clients in dev server 200 -for development
                                                        210 - for development testing
In development it is working but in development testing client and in quality it is not working.
Can you please help me as to why we are getting the above message?
Best Regards,
Rajesh

Hi Rajesh,
That is coming because of the Table Maintainance Generator Settings. You have to chose no, or user, recording routine then system will not generate any request and you can update the data. This is actually a BASIS settings in SCC4, so that for customizing tables system should not generate any request.
Thanks & Regards,
Faheem.

Table maintenance view - tcode

Hi experts,
We have a tcode (already in production) created for table maintenace view of z-table.
Everything is working fine.
Now I added one new field to the z-table and changed the table maintenance view accordingly. In SM30 I can maintain the table without difficulties - the new field is visible and maintenable. However, when I call the transaction code created for this view, it doesn't have the new field yet. I tried a lot but without success to update the tcode accordingly.
How can I get the tcode adjusted with the new field?
Thanks for your advise and help in advance!
Your feedback will be << appreciated >>.
Regards,
Sally
Please do not offer rewards.
Edited by: Rob Burbank on Dec 6, 2009 5:22 PM

It's about one week you asked the question, but I answer in case you didn't understand what happened:
First, screens 1000-1010 can't be used in a table maintenance dialog (an error is mentioned by SAP when you try to use these numbers). So, I really don't understand how you can get 1000 in your table view!
So, I think that your transaction is linked to a custom program (not the SM30 view). So you just need to adapt manually the custom program. Note: maybe the program is a partial copy of the SM30 function group, so maybe you may just copy the dynpro 1000 of the SM30 function group to the dynpro 1001 of your custom program...
Note: when you want to create a transaction which is linked to a table maintenance view (SM30), you must define a Z* transaction of type parameter, with reference to SM30 transaction, select "skip initial screen", do not choose any dynpro, and choose VIEWNAME = your view and UPDATE = X as parameter values.

Purpose of table maintenance generator

wht is the purpose of table maintenance generator

Hi Pavan,
The purpose of table maintainence generator is to enable the table maintenance through SM30, and to implement and validation etc on table field inputs.
SE11->Utillities->table maintainence generator
You need to enter the values of following fields:
1. Table name
2. Authorization group , and authorization object (select the suitable one )
3. Function group and package
4. Maintainence type : single or double screen maintainence view depending on the option selected.
5. Maintain screen number : you may specify a value or let the system generate one for you.
The validation code for the table entry is written in the flow logic of this screen. Even some of the fields may be made display only , by adding suitable code in the logic or directly disabling the input in table control in the layout.
Table maintanance is for creating,adding datas to an existing table.
it is for adding muiltiple records at a time in the table
A table can be manipulated by a program or manually.
When creating table, you will find a check box 'Table maintenance allowed'. If we
check that option, we can manually enter entries using SE16 or table
maintenance generator screen.
SE16 is for data browser.
Go to SE11, give the table name and click on change. Then Go to utilities--> Table
maintenance generator.
In the table maintenance generator screen, we should give Authorization Group,
Function Group name (Function Group name can be same as table name),
Maintenance type can be one step or two step, usually we will create with one
step. we should give maintenance screen number. After clicking on create button,
a table maintenance generator will be created.
To check it go to SM30 . In SM30, we find display, Maintain options.
We can view the table contents by choosing Display and we can create table
entries by choosing Maintain.
In the production system, end-users will not be having access to transaction
codes like SE11 and SE16. Developers will not be having access to many
transaction codes including the above two.
To view the contents of the database table, we will use SE16n in Production
system. Please find out the difference between SE16 and SE16n.
All these authorizations will be maintained by BASIS team, by creating access
profiles.
So in order to edit or create the contents of a database table, we should go for
table maintenance generator. In real time, authorizations will be maintained in
production system. (even in development and Test systems to some extent).
There is an audit like Sarbanes-Oxley Act for American clients, where every thing
will be audited by government agency. To know more about SOX, use the links on
the right hand side of this page.
The second reason is, we can edit or create multiple entries at a time, using table
maintenance generator.
Apart from that we have options like 'Enter conditions' in table maintenance
screen SM30. Please try to find out the use of those, by creating an example.
Table Maintenance generator: Difference between one step and two steps.
While creating table maintenance generator, we find below options:
When we choose one step, we have to give the screen number in Overview Screen field.
When we choose two step, we have to give both overview screen number and single screen number.
You can give any number for screen. Dont give 1000 screen number. As this
number is reserved for selection screen.
When we choose two step, two screens will be created for table maintenance. For
single step only one screen will be created.
When we choose two step, table maintenance will work as follows
Go to SM30, give the table name for which you have created table maintenance-
Overview screen will be displayed. To create entries, when you click on new
entries. Another screen will be displayed, where you give input and save. You can
enter one record at a time.
Go to SM30; give table name for which you have created table maintenance-
Overview screen will be displayed; To create entries click on new entries, you can
enter the records on the same screen. You can enter multiple records at a time.
We use single step generally, as it is user friendly.
To completely understand the difference and above points please do exercise by
creating table maintenance generator in both ways (using single step and two
step).
Link: [http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm]
Link: [http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm]
Link: [/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.

Error in creating Table Maintenance for TABLES: J_2IRG1BAL ,Dump error show

Dear Gurus
I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
*Dump Error Shows in Production*
Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
What happened?
|    Error in ABAP application program.
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
rigger Location of Runtime Error                                                                 |
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
|    Module Name                             VIEW_MAINTENANCE
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
| 110|            USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.

I have send you all the details regarding the table maintenance generator
error is shown below
                                       I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No.    Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
                                                                                Runtime Errors         SYNTAX_ERROR
Date and Time          11.12.2008 09:26:30
ShrtText
Syntax error in program "SAPLJ1I5 ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Trigger Location of Runtime Error
Program                                 SAPLSVIM
Include                                 LSVIMU01
Row                                     107
Module type                             (FUNCTION)
Module Name                             VIEW_MAINTENANCE
Source Code Extract
Line
SourceCde
77
TRANSPORTING NO FIELDS.
78
IF sy-subrc NE 0.
79
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
80
IF sy-subrc NE 0.
81
RAISE no_editor_function.
82
ELSE.
83
length = strlen( function_name1 ).
84
ASSIGN function_name1(length) TO <function_name>.
85
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
86
IF sy-subrc NE 0.
87
RAISE no_database_function.
88
ENDIF.
89
ENDIF.
90
INSERT x_header-viewname INTO alr_checked_views INDEX sy-tabix.
91
ELSE.
92
length = strlen( function_name1 ).
93
ASSIGN function_name1(length) TO <function_name>.
94
ENDIF.
95
96
Initialisierung der RFC-Destination zum View                        *
97
98
FPOOL+4 = X_HEADER-AREA.
99
fpool   = x_header-fpoolname.
100
vim_default_rfc_dest-viewname = x_header-viewname.
101
vim_default_rfc_dest-rfcdest = rfc_destination_for_upgrade.
102
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
103
USING 'VIM_DEFAULT_RFC_DEST' 'C' vim_default_rfc_dest rc.
104
105
Initialisierung des Abgleichsmandanten zum View                     *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client   = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
110
USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.
111
112
set flag if complex selection conditions in sellist                  *
113
114
IF complex_selconds_used NE space.
115
READ TABLE dba_sellist INDEX 1.
116
IF sy-subrc EQ 0 AND dba_sellist-cond_kind EQ space.
117
dba_sellist-cond_kind = 'C'. MODIFY dba_sellist INDEX 1.
118
ENDIF.
119
ENDIF.
120
121
direkter Vergleich: Flagge setzen usw.                              *
122
123
IF view_action EQ vim_direct_upgrade.
124
view_action = aendern.
125
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
126
USING 'VIM_SPECIAL_MODE' 'C' vim_direct_upgrade rc.

Problem in Table Maintenance Generator

Hi All,
We have a TMG which have 11 fields with below fields as primary key.
CONTRACT_NO
ITEM_NO
PRODUCT
WAREHOUSE
VALIDITY_START
VALIDITY_END
As per standard , during Change Mode these keys will be disable.
My requirment is to enable the VALIDITY_END in change mode also. I have done that by changing the attribute in SE51(Input Possible).
Now Problem is When I change the VALIDITY_END and saves it, In TMG it shows message "Data Saved" but when I check the
database table , Changes not reflected.
Please help.
Thanks
Jitendra

Hi Jitu,
I agree this is not the right way to do this. You should keep the following in your key fields. And validity_end as normal field. Use the table maintenance events to make validity_end as a mandatory field. Using this events you can pass error messages to user if they keep it blank.
CONTRACT_NO
ITEM_NO
PRODUCT
WAREHOUSE
VALIDITY_START
Best Regards,
Tapodipta Khan.

Help required on table maintenance generator

Hi all,
Would any one tell me what is the difference between one step and two step while creating a table maintenace generator for a table.
one more question is i would like to know which search the following code follows while it is executed.
select single vbeln
from vbak into l_vbeln
where vbeln in s_vbeln.
and
select vbeln
from vbak
into l_vbeln
up to 1 rows
where vbeln in s_vbeln.
please do reply soon for the questions.

Hi
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.
Difference Between Select Single and Select UpTo One Rows
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Reward points for useful Answers
Regards
Anji

Table entry in production asking to create a transport number

Hello,
I have created on transparent table with delivery class A and data class DATA0. created its table maintenance and created a tcode of that. and moved all this to production.
Now, when I am creating entries in that table through tcode, its asking me to create a transport number.
What is the problem?
thanks and regards,
Madhuri Sonawane

Hi
This is bit strange since when I check the settings in my systems I am able to maintain in production without any transport number.
Just check in SCC4 of your production
client role - Production
No changes allowed
Last chance is to try to change the delivery class as 'C' and then check in Q. Also if possible change the client settings in SCC4 of you Q as in P and try.
Regards,
Vijay V

Customizing table in quality & production

Hi all,
Here's a simple question.
In the Development environment:
I have a customizing table ZPWCFG_INC with the following attributes:
Delivery Class C Customizing table, maintenance only by cust., no
Data Browser/Table View Maint. Display/Maintenance Allowed
I also have a table maintenance dialog for ZPWCFG_INC with the same name, generated with "no, or user, recording routine"
This means that in Dev it does not prompt me for transport request when i maintain the table entries in SM31.
Am I guaranteed to be able to maintain the table entries in QA and Production since now the table entries are not transportable?
Thanks,
Kevin

Hi kevin,
1. Am I guaranteed to be able to maintain the table entries in QA and Production since now the table entries are not transportable?
No, it will not allow to maintain in QA and PRD. (unless the client is opened by basis team)
2. Bcos the table is having delivery class as C = customizing table.
regards,
amit m.

About table maintenance generator

hi,
1. why we have to give a function group name while creating table maintenance generator for a ztable.
2. while creating tmg we have to check one of the radio button under recording routine. wht does recording routine means?

Hi,
Function Group - this will create a default main program where you can store the
events for the table maintainence.( where you can write the code for the table
maitainece)
standard recording - when the changes in the table maitainence automatically it will create request for the data to transport.
no recording - this will not create request(when you don't require the data in
Development server to transported to testing or Testing - to -Production.
atthat time you can select the radio button foe NO RECORDING.
Madhavi

Table maintenance

Hi,
There are two ways to maintain Data records in a table :
1. By program : using insert/delete/modify or update statement.
2. By table maintenance
What is the advantage or disadvantage of one process to another.
Thanks & Regards,
Abhishek Sarkar

Hi,
Table maintenance is used to maintain data in the tables created (ZTABLE)
Generally for inserting new records into custom table thru transaction SM30, we need to enter all the values manually and save the record.
When certain data for the key fields needs to be populated automatically while creating entries, the steps involved are:
Maintaining the subroutine in view V_TVIMF for a particular custom table.
Logic for extracting relevant data for the fields entered, when user press enter button.
Check this blog for more information on extracting data in table maintenance.
/people/sudheer.cheedella/blog/2006/02/20/extracting-data-in-table-maintenance
With the help of the table maintenance generator, you are able to maintain the ENTRIES of the table in SM30 transaction.
It can be set in transaction SE11 - Tools - Table maintenance generator.
Table maintenance Generator is used to manually input values using transaction sm30
follow below steps
1) go to se11 check table maintenance check box under attributes tab
2) utilities-table maintenance 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 maintenance generator to move table
contents to quality and production by assigning it to request.
4) Select maintenance type as single step.
5) maintenance screen as system generated numbers this dialog box appears when you click on create button
6) save and activate table
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.
SM30 is used for table maintenance(addition or deletion of records),
For all the tables in SE11 for which Table maintenance is selected , they can be maintained in SM30
Sm30 is used to maintain the table ,i.e. to delete ,insert or modify the field values and all..
It creates the maintenance screen for u for the particular table as the maintenance is not allowed for the table..
In the SE11 delivery and maintenance tab, keep the maintenance allowed..
Then come to the SM30 and then enter the table name and press maintain..,
Give the authorization group if necessary and give the function group and then select maintenance type as one step and give the screen numbers as system specified..
Then create,,,
Then u will able to see the maintenance view for the table in which u can able to insert and delete the table values...
We use SM30 transaction for entering values into any DB table.
First we create a table in SE11 and create the table maintenance generator for that Table using (utilities-> table maintenance generator) and create it.
Then it will create a View.
After that from SM30, enter the table name and Maintain, create new entries, change the existing entries for that table.
check these links --
http://help.sap.com//saphelp_470/helpdata/EN/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/how%20to%20implement%20events%20in%20table%20maintenance.doc
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]
Re: Regarding Table Mainantance Generator
Re: table maintenance
table maintenance generator
Re: Table maintenance generator
Regards
Sudheer

Problem in table maintenance

Hi Gurus.
I created one ztable and also table mainenance .
but in sm30 the table is not showed blank screen is showing. here I am not able to create entries.
please give me the reply.
Regards,
Shashikumar.G

hi
good
SM30 is the tcode used to input the values/User Entries in the dictionary object (table) cretaed in SE11 after creating the tables maintenance generator
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
thanks
mrutyun^

Product Configuration - How to relate a z-table to a product characteristic

Hi All,
We have generated different z-tables for different types of products. Every table has more than 200 entry, we want to relate a characteristic to this table, so that we won't enter these characteristics manually and it will be automatically feed by the table that we have generated.
Do you have any opinions for this issue?
Thanks
Ozge

This question had been asked millions of times...you just need to search the forums...
Quick hint...goto SE11...the utilities menu and then Table Maintenance Generator.
Greetings,
Blag.

New field not reflecting in Table maintenance generator

Hi Experts,
I have added a new field in a ztable.I regenerated the table maintenance generator,so that the new field is reflecting in devlopment system , also a TR got created.When i moved this TR to pre-production system new fields are reflecting in the structure of table but not in table maintenance generator.
Please suggest solutions.
Regards,
Niranjan

Hi Experts ,
I have gone through the steps which is mentioned.But still issue is pending,the changes in TR are not reflecting in pre prod.
Error after moving the TR with "Definition of a Maintenance and Transport Object".
The current ABAP program "SAPLSVIM" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLZFGL " in include "LZFGL$03
" in
line 13:
"Field "ZCHAR_FIXED_WIDTH" is unknown. It is neither in one of the spec"
"ified tables nor defined by a "DATA" statement. ."

What is the purpose of TABLE MAINTENANCE GENERATOR IN ABAP DDIC

CAN ANY EXPLAIN ME
1.what is the purpose of TABLE MAINTENANCE GENERATOR IN ABAP DDIC?
2. AND THE CONTENTS IN ITS TABS.
KINDLY LET ME KNOW.IT IS URGENT
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 28, 2008 11:42 AM

Go to SE11, give the table name and click on change. Then Go to utilities--> Table maintenance generator.
In the table maintenance generator screen, we should give Authorization Group, Function Group name (Function Group name can be same as table name), Maintenance type can be one step or two step, usually we will create with one step. we should give maintenance screen number. After clicking on create button, a table maintenance generator will be created.
To check it go to SM30 . In SM30, we find display, Maintain options.
We can view the table contents by choosing Display and we can create table entries by choosing Maintain.
Why we have to go for Table maintenance generator, when we can edit the table by SE16 or SE11, utilities->create entries?
In the production system, end-users will not be having access to transaction codes like SE11 and SE16. Developers will not be having access to many transaction codes including the above two.
To view the contents of the database table, we will use SE16n in Production system. Please find out the difference between SE16 and SE16n.All these authorizations will be maintained by BASIS team, by creating access profiles.
So in order to edit or create the contents of a database table, we should go for table maintenance generator. In real time, authorizations will be maintained in production system. (even in development and Test systems to some extent).
There is an audit like Sarbanes-Oxley Act for American clients, where every thing will be audited by government agency. To know more about SOX, use the links on the right hand side of this page.
The second reason is, we can edit or create multiple entries at a time, using table maintenance generator.
Apart from that we have options like 'Enter conditions' in table maintenance screen SM30. Please try to find out the use of those, by creating an example.Table Maintenance generator: Difference between one step and two steps.
While creating table maintenance generator, we find below options:
1. When we choose one step, we have to give the screen number in Overview Screen field.
2. When we choose two step, we have to give both overview screen number and single screen number.
You can give any number for screen. Dont give 1000 screen number. As this number is reserved for selection screen.
When we choose two step, two screens will be created for table maintenance. For single step only one screen will be created.
When we choose two step, table maintenance will work as follows:
Go to SM30, give the table name for which you have created table maintenance-
Overview screen will be displayed. To create entries, when you click on new entries.
Another screen will be displayed, where you give input and save.
You can enter one record at a time.
We use single step generally, as it is user friendly.
To completely understand the difference and above points please do exercise by creating table maintenance generator in both ways (using single step and two step).
<REMOVED BY MODERATOR>
regards,
Balaji
Edited by: Alvaro Tejada Galindo on Feb 28, 2008 11:42 AM

Table maintenance in production

Similar Messages

Maybe you are looking for