Table Maintenance - Time-Dependence - Expand- Colapse

Hi
We have a Z table for which we have generated table maintenance with time-dependent functionality.
<a href="http://help.sap.com//saphelp_470/helpdata/EN/c1/df5c3c3b067331e10000000a114084/frameset.htm">http://help.sap.com//saphelp_470/helpdata/EN/c1/df5c3c3b067331e10000000a114084/frameset.htm</a>
For this SAP provides Expand-Collapse button on SM30 transaction, and it default shows the valid entries application for current date.
My question here is.. Is there any event/parameter id/settings which should by default shows all entries.
Many thanks for your inputs, for any further details please let me know.
Cheers

Yes.. you can do that.
You can change the Table Maintenance Generator's code and write your own code.
Just check there and comment the CODE which considers the values of DATE as SY-DATUM... just comment it or clear it.
Then you will get all the entries...

Similar Messages

Table Maintenance & View Clusters

Hi,
I am trying to generate table maintenance views and group them using a view cluster. The following is what I have done so far.
I created 2 tables. TAB_A is the primary table with TAB_B the description by language table. They are not linked to each other in any way (even though they probably should).
TAB_A - FLD_A (key, char2)
              FLD_B (date)
              FLD_C (time)
              FLD_D (fltp16)
TAB_B - FLD_E (key, char2, same type as FLD_A)
              FLD_F (key, char3, language field)
              FLD_G (char50)
              FLD_H (date)
              FLD_I (time)
              FLD_J (fltp16)
I then created 2 maintenance views based on the tables above.
VIEW_A - FLD_A
          FLD_B (hidden)
          FLD_C (hidden)
          FLD_D (hidden)
VIEW_B - FLD_E
          FLD_F (hidden)
          FLD_G
          FLD_H (hidden)
          FLD_I (hidden)
          FLD_J (hidden)
I've then used the table maintenance generator to create the screens as well as the unique events to populate the hidden fields.
Using SE54, I've created a view cluster. I have added both of my views to the view cluster as follows:
View/table       TAB_A          TAB_B
Predecess.       TAB_A          TAB_B
Dep              R              R
Pos              1              2
Start            true
I have clicked the field-dependence button and generated the dependencies successfully.
So far everything is okay.
I now need to change the hierarchy in the cluster, so that TAB_B is dependent on TAB_A.
What I have tried so far is to add a foriegn key to TAB_B (this worked but is not an ideal solution).
I also changed the dependency type in the cluster to 'S' (only worked in conjunction with FK)
The documentation indicates that what I am trying to do is possible, but I'm not sure how.
So do any of you bright people out there have any ideas?
Be gentle I'm new to both the forum and SAP in general (hence being given table maintenance).
Kind regards
Chris

In my experience, cluster maintenance view Table 1 keys where always used as foreign keys in Table 2. Then these common fields were used in dependencies and subset.
- Creation of maintenance view on table 1
- Then generation of maintenance dialog on Table 1
- Creation of maintenance view on table 2 defining the keys of Table 1 as subset fields (test the dialog, a popup should appear with the subset fields)
- Then generation of maintenance dialog on Table 2
- Creation of the cluster generating the dependency between Table 1 and itself (without specifying any field) and between Table 1 and table 2 using the subset fields (should work automatically)
Look also at [Create a View Cluster|http://help.sap.com/saphelp_nw04/helpdata/en/d0/999249b2aa11d1a5700000e82deaaa/frameset.htm]
Regards

Missing Date fields in table maintenance generation

I have some non-key date fields in my custom table and have noticed that they do not get generated on the overview screen of my two-step table maintenance dialog. They are present on the detail screen.
If I change the domain of the fields to CHAR they appear.
If I change the maintenance type to one-step they appear.
It seems it is standard behaviour for date fields to be omitted from the overview screen.
Can anyone confirm that this is standard behaviour or give an explanation for date fields being treated in this manner?...or come up with a way of including the fields on the header screen.
I already know that I can:
1. customize the screen to include the fields
2. create a non-date domain for the fields which uses date-type calendar dropdown
Thanks,
Neil

Thankyou Jonathan, I would have been too lazy to go into debug if I didn't have the form name you supplied! It wasn't the reason you suspected but it was failing the following check in that routine:
maintenance in list screen required?
 CHECK p_tvdir-type = one_step_maint OR
 ( <w_dfies>-keyflag NE space "force only keyfields
 OR ( 'CHARNUMC' CS <w_dfies>-datatype "and view char-fields
 AND p_skip_fields = space )
 OR ( 'CHARNUMC' CS <w_dfies>-datatype "and view char-fields
 AND <w_dfies>-intlen GE 20 ) "int 3263961/2000
 OR <w_dfies>-rollname = 'BEGDA' "time dependence
 OR <w_dfies>-rollname = 'ENDDA' "time dependence
 OR <w_dfies>-tabname NE p_gencb-viewname ). "or text table field
Because the datatype was DATS.......looks like it will only include key fields and CHAR, NUMC non-key fields or those with a rollname of BEGDA/ENDDA or texttable fields. In debug I changed the datatype to CHAR and it generated with my field included. I think there might be an OSS note to fix this but haven't found it yet.

Aotu numbering in table maintenance view

Hi experts,
Can anybody help me in auto genereating serial number in table maintenance view. I have created table maintanance view for a z table for which first field is serial no. The requirement is this serial number should be auto genereted. increment by 1. I have writeen the code for the same in PAI event, but it getting incremented by number of rows. e.g for secind row counter is incremented by +2. for thrid row it is +3 and so on....
plz help to achieve consistency .
Thnks n regards,
Ashmita Singh

What happens if the user deletes a recird from the table?
Suhas,
Happy New Year
Disable delete function and provide a deletion indicator. This should be fine right.
The problem would be when the maintenance dialog is regenerated.
@OP - So as suggesgted use events.
Similar threads were discussed before many times. May be you culd search it once.

Maintenance view Vs Table maintenance

Hi,
I would like to know the dif between T.Maintanance And Maintenance view.
As we know as per the def we know Maintenance view will be used to maintain a table. But I have never created any M.view for the same.
However we use Table maintenance generator and SM30 for the same. How these 2 concepts are differnet?
Which one is the best method 2 use?
what one step and two setp process? Advantage and usage of 2step process?
Thanks in advance.
PRa

Hi Praneet..
These two are different concepts altogether but they have some connection.
1. Table Maintenance: To facilitate the Updation / Viewing the Records of a Table thru a Tcode We have to Generate the Table maintenance (program and screens) in Tcode SE54.
This will generate the Function Groups and Screens required to Maintain the Entries in table.
Then only we can maintain this Table in Tcode SM30.
2. Maintenance view: It is one type of View which can be used to update/view the data from multiple tables at a time.
But after creating a Maintenance view, We must generate the Table maintenance .
Only then we can maintain the entries using a Maintenance view.
REWARD IF HELPFUL.

Table Maintenance View Generator - 46C to 60 compatibility

Table Maintenance View Generator - 46C to 60 compatibility
I think SAP changed the way it generated its View Maintenance Screens some time after release 46C such that view maintenance dialogs in 46C are maintainable in subsequent releases but that view dialogs created in subsequent releases are not compatible in 46C. This is my hypothesis.
Can someone confirm? Is there a way to revert 60 code to the way the dialog was generated in 46C?
The error in the transport log from a 60 system to a 46C system is:
"Field '<VIM_TOTAL_STRUC>' is unknown. It is neither in one of the specified"

Hi April,
You can use standard program RSWBO052 to change the package. Enter the object and mark the checkbox -> Execute -> Place the cursor in the object -> Right click mouse -> Reassign -> Enter new package -> Save.
or you can go to transaction SE80 -> Select Package -> Enter &TMP -> Hit Enter -> Find your object -> put the cursor and right click -> Other functions -> Object Directory Entry -> Change -> Change the package -> Save.
Hope this will help.
Regards,
Ferry Lianto
Please reward point if helpful.

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.

Dynamic Column Names - Table Maintenance - SM31

Hey Everyone - I hope you are all having a good day )
Basically I have a custom Z table containing a number of different fields. I have created table maintenance for this table so it can be updated via SM31. This table is a generic mapping table that will be used for all mappings.
What I want to do is change the name of the columns based on x criteria when maintained in SM31. So for example.
The user chooses to edit line one, through SM31- for Company Code 123 - at this point I want to change the name of Columns 1 through 5 to relevant names for that Company Code. e.g A, B, C, D, E respectively. If the User chooses Company Code 567 then the names of Columns 1 through 5 will be something else. e.g. F, G, H, I, J respectively.
In the PBO of the overview screen I have implemented code to process this behaviour. From here I can hide fields etc etc. However I dont know where to change the actual Columns names to what I want them to be - i.e overwrite the Field Name coming in from the data element.
I would be very appreciative if anyone could help out on this. As always, thanks for taking the time to read this and I look forward to hearing from you.
Kind Regards
Damien

When system generates the Table Maintenance, it creates LABEL (text fields) for the column heading in the table control and we can't control this labels from our program. These Label names are as like
*tablename-fieldname E.g. *ZTEST_TAB-FIELD1
So, you can replace these labels with Input Output Text field.
Make sure you give the same name as respective label's name.
Make these fields as "Output Only".
Now, you would be able to change the value of these fields from the PBO.
Word of caution: These of changes would go away if try to recreate the table maintenance.
Regards,
Naimesh Patel

How to validate data entered in table maintenance for Z table?

Hi,
I created a Z-table with table maintenance. I'd like to perform some validation on the entered data.
I know there are events for these : "If this pre-defined time is reached in extended table maintenance, the FORM routine specified for the current view and for this time is processed. This is useful, for example, for performing consistency checks before saving or specific actions when creating new entries."
I also found some info in the Online help:
http://help.sap.com/saphelp_47x200/helpdata/en/91/ca9f0ea9d111d1a5690000e82deaaa/frameset.htm
However it's not clear which event I can use for validation.
I tried event 01, however when I added a message, in the SM30 in case of message, I got the SM30 initial screen.
Do you have any example about validation?
Thanks in advance,
Peter

Hi,
Once you are on the table maintenance generator screen.
GOTO --> Enviornment --> Modification --> Events.
Here specify Event as '01' and the Subroutine name that will hold the data for the validation.
As you know we need to specify a function group.
GOTO SE80 and Open your function group.
Now in the PBO of the screen write a subroutine for the validation before saving an entry in the table.
Refer the code below for validation.
*& Form F9000_CHECK_BEFORE_SAVE
 Subroutine called dynamically to check values before saving
FORM f9000_check_before_save.
TYPES : BEGIN OF ty_flmt,
 zz_flmt_type TYPE zz_flmt_type,
 zz_gsm_flmt_code TYPE zz_flmt_code,
 END OF ty_flmt.
Internal Table
DATA : lit_flmt_code TYPE TABLE OF ty_flmt,
 wa_flmt_code LIKE LINE OF lit_flmt_code.
DATA: lv_subrc TYPE sy-subrc VALUE '0',
 lv_tabix TYPE sy-tabix,
 lv_total_rec TYPE i,
 lv_rec TYPE i,
 flg_upd TYPE flag.
DESCRIBE TABLE total LINES lv_total_rec.
LOOP AT total.
 lv_tabix = sy-tabix.
 READ TABLE extract WITH KEY total.
 IF sy-subrc EQ 0.
 IF extract+3(10) IS INITIAL.
 DELETE total.
 DELETE extract INDEX sy-tabix.
 DELETE extract INDEX lv_tabix.
 lv_subrc = '4'.
 flg_upd = 'X'.
 MESSAGE s119(zcrm_appl) DISPLAY LIKE 'S'.
 SET SCREEN 0.
 ENDIF.
 ENDIF.
 wa_flmt_code-zz_flmt_type = total+13(3).
 wa_flmt_code-zz_gsm_flmt_code = total+16(10).
 APPEND wa_flmt_code TO lit_flmt_code.
ENDLOOP.
IF flg_upd IS INITIAL.
 SORT lit_flmt_code BY zz_flmt_type zz_gsm_flmt_code.
 DELETE ADJACENT DUPLICATES FROM lit_flmt_code.
 DESCRIBE TABLE lit_flmt_code LINES lv_rec.
 IF lv_total_rec <> lv_rec.
 LOOP AT extract.
 READ TABLE total WITH KEY extract.
 IF sy-subrc EQ 0.
 DELETE total INDEX sy-tabix.
 DELETE extract INDEX 1.
 lv_subrc = '4'.
 MESSAGE s289(zcrm_appl) DISPLAY LIKE 'S'.
 SET SCREEN 0.
 ENDIF.
 ENDLOOP.
 ENDIF.
ENDIF.
sy-subrc = lv_subrc.
ENDFORM.
Please reward points and close the thread.
Regards,
Amit Mishra

Blank Records added while using Table maintenance generator - SM30

Hi all,
I have created a ztable and view,
For the view table maintenance generator created using sm30,
First time when i add reords, a blank record is added automatically ,how to prevent it,
Also when i try to add invalid data, system throws error , field becomes display only.
How to solve.
Regards
Senthil

Hi Tarun,
Go to the layout and increase the size of the Screen. or at the screen attributes change the length and width values.
You know that initially the screen occupies default size only.
Hope this would serve your purpose.
Cheerz
Ram

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

Find table for table maintenance

Say youre in transaction mm03 to display a material. How do you find the table you can perform table maintenance on to edit selections for field MVGR5?

Good question. Here is the way that I found it just know. I went to SE11 and looked at the MVKE table and saw that the check table for MVGR5 is TVM5, then I went to the intial screen of SE11 and changed the radiobutton to view, and did F4 help, here I hit the expand view icon and entered TVM5 in as the primary table and checked "Maintainence view", it returned V_TVM5 as the maintenance view. I entered this view name into SM30 and that's it.
I don't think that it is always this cut and dry.
Regards
RIch Heilman

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

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

Table Maintenance - Time-Dependence - Expand- Colapse

Similar Messages

Maybe you are looking for