Table maintenance generator is not saving entries.

Hi All,
I am facing problem in table maintenance generator.
I created a table maintenance for Z-Table.
In my table last 2 fields are a checkbox.
When we go to Sm30 and check/uncheck the boxes then save , message comes tht data saved , but when we come out and go back to maintenance generator , it's not saved.
while table maintenance in 2 step , then on detail screen it is working perfectly but on primary screen it's not.
when TM is single step , it's show entries saved but not saving in data.
I tried to delete and regenerate table maintenance but still not working .
Please guide me to ractify this.
Thanks in advance,
Ashish Gautam

Hello Friend,
Check with th etechnical settings of the ztable:
see if your buffereing is allowed, and log data chnages is checked.
If so :
Then select buffereing is not allowed and uncheck the Log Data Changes:
Also go to TMG:
Check if standard recording routine is selected, then select the no, or user recording routine.
After making these changes, delete the TMG and create a new one once again. You can check it will work fine now.
Thanks and regards,
Uttam Agrawal
[http://uttambpt.blogspot.com|http://uttambpt.blogspot.com]
Edited by: uttamagrawal on Jan 31, 2011 12:42 PM

Similar Messages

Issue in table maintenance generator

Hi,
We have tranported a new table to Q from devlopement.
But the table maintenance generator is not tranported.
How can we tranport it again form the devlopement.

Hello,
In this case you need to generate table maintenance object for the required table again.
Save that object in new transport request.
Now, You can either directly release this new request and import it in Q system or
merge the new request with existing released request and import new created request into Q system.
Check if this help,
Thanks,
Augustin.

Table Maintenance Generator : Editable Entry after validation fails

Hi,
I have created a Z table and a table maintenance generator to maintain the data.
I have to carry out certain validations when user enters data on Key and Non- key fields.
This is working fine, but the issue is with the key fields.
If validation fails, the table maintenance screen is displayed the date-field is grayed out (non-editable) as it is the key field of the table.
Now the user cannot change the data unlike the non-key fields were the user can modify the non-valid data and save again.
How can make the date field (Key Field) editable after entry in case the validation fail, so that the user can make the changes.
Please suggest the approach to handle the above scenario in events.
Thanks,
Keyur

Thanks Kiran for your inputs.
I have done the same thing what you have explained.
I have used a Form Routine as CIP_SAVE with Event Number as 01, since on event SAVE i need to validate whether dates are
overlapping the inputs dates or not.
Fields are :
Group ID (Key)
Start Date (Key)
End Date (Key)
Value (Non -Key)
Initial value in Table:
Group ID = 12345
Start Date = 01/01/2011
End Date = 01/31/2011
Value = 11.11
Now if i try to enter value:
Group ID = 12345
Start Date = 01/02/2011
End Date = 01/25/2011
Value = 99.99
& SAVE it... validation will fails because Start & End dates overlaps.
Hence, on Table Maintainance Screen all key fields will be in non-editable display mode, whereas non-key field will be in editable mode.
My requirement is that Start Date & End Date key fields must be Editable field.
Thanks.

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

Table Maintenance Generator - Lock of entries from different user

Hi there,
It looks like that there are a lot of threads about table maintenance generators, but none related with this one. The case is when I created a customer table Ztable and using table maintenace generator to get the Tcode Ztcode. My questions is how can 2 different user at the same time running this Ztocde without locking with each other?
Thanks in advance!
Weidong

Hi there,
From what I know it can be done through customer ABAP program transaction code but not from Table maintenance generator generated Tcode.
Any suggestion?
Weidong

Field validation in table maintenance generator and input value grey out.

i have created ztable with 3 fields as em_no,em_no and addrnumber.
first two fields are custom fields but the third custom field need to validate the standard table adrc contains the value of the field addrnumber.
i need the query of field validation query which we write in create entry events in table maintenance generator and also if we give wrong value for addrnumber in sm30 maintain table, the input field need not to be grey out for next entry...
please help.

Hi,
create method -
>before saving data.....write the logic between the method
go to utilities->table maintanance ,,,after creating generator ---go to envirnment->modification->events.
create event -.>.as zsave select event type 1(before saving data to table) write code in include....
consider data for field3 is 10 .
lv_new = ztbr(table name)-field3.
select field3 from ADRC(ZTABLE) into wa_new (TYPE ZTABLE) where field3 = lv_new.
if sy-subrc = 0.
     working fine
     else.
    message i888(sabapdocu) with 'data invalid'.
endform.
This will help u...
Thank u.........

Event code in table maintenance generator

Hi All, Need to call event in Table maintenance generator of the z table. I have to use 1st event (Select ’01’ – Before saving data in the database). Need to do fallowing job: Table cleaning : Delete all records with value year =< 2011 -New rule : No save can be done with value (Pst Var, PA,PSA, Cost = ‘ *,*,*,*’). I am attaching table entry with this mail, I have written the code for this but not sure please suggest me modification if required for this.Because i have never done this before. Thanks and Regards Sankil

hi Sankil
Some variable is not available in your code and you did not modify EXTRACT table.
Try to modify your code as blow:
This event has no standard routine. The following global data is available for the realization of the user routine:
•internal table TOTAL
•field symbols
•field symbols <ACTION> and <ACTION_TEXT>
•<STATUS>-UPD_FLAG
If internal table data are to be changed before saving, t he changes should be made in both the internal table
TOTAL and in the internal table EXTRACT.
FORM abc.
DATA: F_INDEX LIKE SY-TABIX. "Index to note the lines found
LOOP AT TOTAL.
IF <ACTION> = desired constant.
READ TABLE EXTRACT WITH KEY <vim_xtotal_key>.
IF SY-SUBRC EQ 0.
F_INDEX = SY-TABIX.
ELSE.
CLEAR F_INDX.
ENDIF.
(make desired changes to the line TOTAL)
MODIFY TOTAL.
CHECK F_INDX GT 0.
EXTRACT = TOTAL.
MODIFY EXTRACT INDEX F_INDX.
ENDIF.
ENDLOOP.
SY-SUBRC = 0.
ENDFORM
refer event 01: http://help.sap.com/saphelp_nw04/helpdata/en/91/ca9f0ea9d111d1a5690000e82deaaa/frameset.htm
regards,
Archer

Modify Key Field Values of a table through Table Maintenance Generator

Hi All,
   I have created a z table with below structure. In this fields upto Valid To are all key fields. This is to ensure that consistant valid record get stored in the table.
MANDT     MANDT     CLNT     3     0     Client
VKORG     VKORG     CHAR     4     0     Sales Organization
VTWEG     VTWEG     CHAR     2     0     Distribution Channel
SPART     SPART     CHAR     2     0     Division
SKU     MATNR     CHAR     18     0     Material Number
LZONE     LZONE     CHAR     10     0     Transportation zone to or from which the goods are delivered
VALID_FROM     ZVALID_FROM     DATS     8     0     Valid From
VALID_TO     ZVALID_TO     DATS     8     0     Valid To
PLANT     WERKS_D     CHAR     4     0     Plant
SNP_TZONE     ZSNP_TZONE     CHAR     20     0     APO Transportation Zone
ERDAT     ERDAT     DATS     8     0     Date on Which Record Was Created
ERNAM     ERNAM     CHAR     12     0     Name of Person who Created the Object
AEDAT     AEDAT     DATS     8     0     Changed On
AENAME     AENAME     CHAR     12     0     Last changed by
I have created a Table Maintance program through the Table Maintenance Generator. And for that I have assigned a t code.
I can able to create new entires but i can not able to modify Valid_from and Valid_to entries of existing records.
Initially those two fields were in display mode but i went to its module pool program and made then as input enabled. But what the vales I was entering, its not getting saved in database. When we change the values of those fields and save it, the system is saying No Data Change.
Any inputs how to solve this issue. I can not make VALID_FROM and VALID_TO fields as non key.
Regards,

Hi,
As you have already said that the value for valid to is a part of the key so you should not have any issues when this value is changed and the value is saved using the table maintainence generator, but in case you want to save values where the value for valid from has changed but the key is same we would not be able to save as there is already a value for the key, so if you want to save these values there are two ways 1 would either to delete the existing value value and create the new value or to have one more field as the key field like a counter so when the value is saved with a key the value is saved with counter as 1 and then ever next time for the new values increase the value of the counter.
In order to save these values use event 5 and put you code there.
You can also carry out checks for new aithorization in that event also.
Regards,
Himanshu

How to see column in table maintenance generator?

Hi All,
Can we write code in table maintenance generator ? where can we write code?
suppose I have created table maintenance generator but column is not visible what might be reason? How to deal with this?
Can any 1 help me in this regard?
Thanks in advance.

Hi,
column is not visible
This may be because of additioni of a new field in the table after you have generated the TMG.
Delete and re-create the object in TMG again.
writing code in table maintenance generator
Yes, you can write.
SE54 --> Environmnt --> Events --> New Entry
Select the event ..eg.
01 for Before saving the data in the database
02 for After saving the data in the database
Press enter. Click on the editor button and start writing your codes in the routine.
Regards,
Firoz.

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.

Event 03 in table maintenance generator

Hello All,
I have created a event 03 in table maintenance generator. Because I need to check if the deleted key is still referenced in an other table.
I tried the following code, but only if I use the message the entry will not be deleted.
MOVE uebergehen TO <mark>.
MODIFY total INDEX sy-tabix.
<xmark> = <mark>.
MODIFY extract INDEX nextline.
IGNORED_ENTRIES_EXIST = abap_true.
* MESSAGE e000 WITH 'Entry not allowed to delete'.
Thanks in advance.
Marcus

had to put it in a generic form, hope it still works:
FORM event_03.
TYPES: BEGIN OF typ_extract,
           zview TYPE zview,   "or ztable, the one with the maintenance dialog!
           flags TYPE vimtbflags,
         END OF typ_extract.
DATA: ls_extract TYPE typ_extract.
* loop at marked lines
LOOP AT extract INTO ls_extract.
    CHECK ls_extract-flags-vim_mark EQ 'M'.
*   place existence check here!
*   using the values in ls_extract-zview-...
*   if value still being used, send message
    IF sy-dbcnt > 0.
      MESSAGE i...
      ls_extract-flags-vim_mark = '*'.
      MODIFY extract FROM ls_extract.
    ENDIF.
ENDLOOP.
ENDFORM.

'Position' Button in Table Maintenance Generator

Hi,
i am using 'Position' button to navigate to particular entry in the table in table maintenance generator.
as far as i know this will correctly when we provide 'left part' of key in the pop up provided by position button.
however in my case where i changed the column positions in the table maintenance generator which includes key fields.
does it going to affect 'Position' functionality? because position button is not taking me to correct positions now.
please suggest....

Did you change the key field order in the table structure in SE11 or did you manipulate the table maintenance screens by changing the key column order?
In either case, you can regenerate table maintenance by clicking the change button in SE55 and selecting all check boxes. This will correct the issue. However, check if you have any custom events written or modified screens, as those changes will have to be restored after regeneration

Disabling fields in table Maintenance generator

Hi Experts,
I would like to restrict some fields in table maintenance generator dynamically/ statically.
Here is the situation.
I have generated table maintenance for the table ZMARA and I have created three transactions for the above single table maintenance generator.
i.e .. Transaction      ---        Table
          ZT1                  ---         ZMARA
          ZT2                  ---          ZMARA
          ZT3                  ---          ZMARA
I am using above three transactions in my module pool program. Based on the certain conditions I am calling different transactions i.e ZT1, ZT2, etc
Here is my requirement:
Suppose if I call ZT1 transaction, I need to display only few fields. i.e ZMATNR, ZMTART, ZPRODH.
or remaining fields should disable. User should not allow to change the content, even if it is new entries/existing entries. only ZMATNR, ZMTART, ZPRODH.
Suppose if I call ZT2 transaction, I need to display only few fields. i.e ZMATNR, ZMTART, ZHTSCODE
How can we restrict dynamically when you call table maintenance generator table through transaction
or
How can we generate table maintenance for few fields?
Edited by: r badveli on Mar 16, 2009 4:27 PM
Edited by: r badveli on Mar 16, 2009 4:27 PM
Edited by: r badveli on Mar 16, 2009 4:28 PM

Hi ,
go to Se11->Table maintenace generation. Double click on screen to edit and assign the field you want to display/hide to groups. In PBO , after the following lines..
LOOP AT EXTRACT WITH CONTROL
TCTRL_ZMARA                         CURSOR NEXTLINE.
   MODULE LISTE_SHOW_LISTE.
ENDLOOP.
Write a new module in PBO and edit the SCREEN as per the Tcode, you are calling,,'
Hope this helps you
Rj

Fields update on Table maintenance generator screen

HI All..
I have a custom table with five fields. I did table maintenance generator on it. It has Screen 1 as overview screen and scree 2 as single screen.
Now of the five fields two fields are user name and date. When i enter data on the other three fields and save it on the second screen - iam able to update the two fields for username and date and display on the screen two itself.
But if iam not saving the data on the screen 2 and going back to screen 1 and then save it - iam not able to update the user name and date and also to display the username and date on the screen.
Any suggestions are helpful..
Thanks and will reward helpful answers.

In this case..
Iam having the functionality of SM30 through table maintenance generator.
On Screen 2- single screen - user name and date is working as i had written the logic in the relevant PBO and PAI module.
But if user is not saving the data in screen screen2 and coming back to screen 1- which is overview screen and then try to save it-- all other fields are getting saved except the username and date..
Thanks.

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 maintenance generator is not saving entries.

Similar Messages

Maybe you are looking for