Short dump in table maintenance genarator

hi all,
in SM30 i gave my table name and clicked on maintain it is going to short dump?
what may be the reason?
regards,
siri.

hi,
I feel that while regeneratng table maintainence after deletion you have to come out of that completely(till SE11) and then press table maintianence generator and create... hope you might have not done the same and so is the result of that dump as the changes were not reflected..
Regards,
Santosh

Similar Messages

Short Dump in table maintenance events

Dear Experts,
I am getting a short dump when i am trying to maintain my Z table. the error is "The statement "MOVE src TO dst" requires that the operands "dst" and "src" are convertible. Since this statement is in a Unicode program, the special conversion rules for Unicode programs apply. In this case, these rules were violated.
the actual short dump is appearing at Move total to fs_zsdslsbud.
ZSDSLSBUD table has a NUMC, 4 char field but in total internal table it is appearing as 0000####. I guess this is the error. I tried to replicate the same code where there are only char type fields and i dont have any issues with below code.
My Z table also have a currency field. How to handle the unicode conversion in this case? can i use Try and Catch statements. A piece of code would be appriciated.
Thanks in advance.
FORM f_trigger_before_save.
DATA: wf_index TYPE sy-tabix. "Index to note the lines found
DATA: BEGIN OF fs_zsdslsbud.
          INCLUDE STRUCTURE zsdslsbud.
          INCLUDE STRUCTURE vimtbflags.
DATA: END OF fs_zsdslsbud.
LOOP AT total.
    IF <action> = neuer_eintrag .
      READ TABLE extract WITH KEY <vim_xtotal_key>.
      IF sy-subrc EQ 0.
        wf_index = sy-tabix.
      ELSE.
        CLEAR wf_index.
      ENDIF.
*      (make desired changes to the line total)
      MOVE total TO fs_zsdslsbud.
      fs_zsdslsbud-ernam = sy-uname.
      fs_zsdslsbud-erdat = sy-datum.
      fs_zsdslsbud-erzet = sy-uzeit.
      total = fs_zsdslsbud.
      MODIFY total.
      CHECK wf_index GT 0.
      extract = total.
      MODIFY extract INDEX wf_index.
    ELSEIF <action> = aendern.
      READ TABLE extract WITH KEY <vim_xtotal_key>.
      IF sy-subrc EQ 0.
        wf_index = sy-tabix.
      ELSE.
        CLEAR wf_index.
      ENDIF.
*      (make desired changes to the line total)
      MOVE total TO fs_zsdslsbud.
      fs_zsdslsbud-aenam = sy-uname.
      fs_zsdslsbud-aedat = sy-datum.
      fs_zsdslsbud-aezet = sy-uzeit.
      total = fs_zsdslsbud.
      MODIFY total.
      CHECK wf_index GT 0.
      extract = total.
      MODIFY extract INDEX wf_index.
    ENDIF.
ENDLOOP.
sy-subrc = 0.
ENDFORM.                    "f_trigger_before_save
Thanks,
Rajesh.

Hi,
Use this FM instead of Move statement.. In Unicode environments the left and right operands should be of same data type. to over come this you can use the below FM
   CALL FUNCTION 'HR_99S_COPY_STRUC1_STRUC2'
          EXPORTING
             P_STRUCT1       = total
        IMPORTING
             P_STRUCT2       = fs_zsdslsbud.

Can we assingn a transaction code to the table maintenance genarator

Hi Gurrus ,
Can we assign a transaction code to the table maintenance genarator code .

Hi,
refere this link,
http://fuller.mit.edu/misc/creating_sm30_transaction.htm
VIEW_MAINTENANCE_CALL : or SM30 is actually called u201CCall View Maintenance
In a nutshell, this program provides a simple selection screen with VKORG, radiobutton for either dollar amount or quantity, and two pushbuttons: Display and Maintain. Then the program fills in the action field and the selection table (i_sellilst) according to the useru2019s selections. When the button is pushed, the screen goes to the same screen as SM30 (sans the first selection screen, of course) and brings up the values that fit the criteria. When the user clicks u201Cbacku201D (green arrow)
reward if found useful..
cheers
Mohinder Singh
Edited by: Mohinder Singh Chauhan on Jun 2, 2008 12:52 PM

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

Need information for table maintenance genarator?

HI Sir,
I have a tcode for table maintenance generator of Z table, my requirement is to add new field to that Z table.
Is it required to maintain table maintenance generator again for that table and how to assign the same tcode for that.
plz help me to solve this.
thanks and regards
syed
Basic question. Please put some effort from your side before posting here. You have already been warned against breaking the rules of this forum. Continued violations will lead to account deletion.
Edited by: kishan P on Sep 2, 2010 11:59 AM

Hi Taj,
When you add your new field in the table, the table gets partially active first, then you need to Adjust the table using Database Utility (SE14) to get the table activated.
For Database Utility see online help [Database Utility|http://help.sap.com/erp2005_ehp_02/helpdata/EN/a4/3790360ee65840e10000009b38f839/frameset.htm]
Then You need to regenerate the table maintainence Generator.
Hope this helps.
Regards
Abhii
Edited by: Abhii on Sep 2, 2010 7:06 AM

WHAT IS TABLE MAINTENANCE GENARATOR

HOW TO CREATE TABLE MAINTENANCE GENERATOR

Hi,
Table maintanance Generator is used to manually input values using transaction sm30.
Follow the 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 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 Table Maintenance Generator
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.
Regards,
Padmam.

How to delete the short dump list in st22

Hi all,
i want to clear the runtime error list in ST22.
How to clear the list of short dump in ST22.
is there any T.code kindly suggest
thanks in advance
Sundar.c

Dear Sundar,
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
Hope this information resolves your error and also more useful in the feature.
Thanks
Kishore

Problem in creating table maintenance generator for 61 fields in table

Hi Experts,
I am facing problem in creating a table maintenance genarator for a ZTABLE which has 61 fields
i am using below details whicle creating the TMG
in Maintenance screen
i am giving maintenance type as two step
Maint screen no overview screen 2
                          single screen        3
Dialog Data Transport details
Recording routine    standard recording routine
but it is giving following error
screen SAPL<ZTABLE NAME>    0003 could not be generated
In DYNPFIELD_ATTR mandatory field LINE has no value
please let me know how to sort out these errors.
Is there any limit on the number of fields for which we can create table maintenance generetor.
Thanks a lot in advance
Sudipto

Hi Sudipto,
There is not limit to the number of fields of the Table which can be used in TMG for generation. But, from the usability point of view this will horrible.
I created a Z table and added 64 fields and was able to generate the TMG with the screens perfectly. So, I guess there should not be any problem.
Well, have a look at the Function Group. I guess the screen numbers are already used by some other screens. You can set the system to propose freely available screen numbers from the pool.
Also, check whether proper authorization is assigned or not.
And if nothing is working, you can degenerate all the generated screens and then can have a new regeneration of it.
Hope these tips will work.
Thanks,
Samantak

Reg table maintenance

what is the pre requisite for table maintenance generator

IN Se11, when you create table you can create the table maintenance generator there.
In utilities you will see table maintenance genarator. YOu have to create a function group. TO be on a safer side use the same name as the table name for the function group. and then create.
Hope this helps.
Shreekant

Problem with table maintenance allowed

hi,
here my problem is table is genarated and stored under local object that time i m creating function group is zabc. afterwards i m storing my table in my development class that time it is not possible to change function group in table maintenance genarator plz help me any one knows.
what is the exact use of table maintenance generator i m using this for ztables and i m going to screen painter i m adjesting the fields.what is the exact use of it.

Hi,
1) You may delete the function group assignment and re-assign another one in change mode
2) The use of table maintenance generator is to provide users with a screen to maintain data in the table. If the data is not going to be populated by any users then there is no need for it. Transactions will automatically populate the data in the background
3) One can access the maintenance screen by going to SM30 or can assign your own transaction code to access it
Hope it helps.
Raj
Reward points if helpful

Maintenance View Giving Short Dump DYNPRO_FIELD_CONVERSION

Hi,
Client has a maintenance view for the table J_2IRG1BAL. But the maintenance view is giving short dump DYNPRO_FIELD_CONVERSION. Can anyone please tell me what could be the reason? How to solve it?
Regards,
Sriram.

Hi,
DYNPRO_FIELD_CONVERSION dump may be due to the following reason, you can find few OSS notes
- Negative entry in Time confirmation
- Negative entry in cost
- Negative entry in reversation
Check these just for reference.
Please Refer the below link it will useful for u.
DYNPRO_FIELD_CONVERSION
dump while entering enteries trough sm30
Regards,
Dhina..

Short dump 'Table does not exist in database'

Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following   Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num   = :p_matnr and
                model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
    Table does not exist in database.
What happened?
    The table or view name used does not
    exist in the database.
    The error occurred in the current database connection "DEFAULT".
What can you do?
    Check the spelling of the table names in your report.
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not
     caught in
   procedure "DYN_LIC_SEL_TOT" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.

Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions.

Short Dump while scrolling in a maintenance view

A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.

Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay

Short dump while accessing the table

There is a report ppioa0000, when executing the report it is going for short dump, error analysis showing that
<b>when accessing the attributes of dictionary table IOSOPER meaningless values are found.</b>
and ABAP run time error showing that DDIC_FIELD_ACCESS_ERROR
suggest me,
thanks and regards
krishna

The database is damaged, links between SAP dictionary and actual database seems to be broken. Try to use SE14 to adjust database.
Regards

Timeout Short Dump on a Data Query to a blank table.

Hi,
My program gives a short dump on quering a blank table. The dump says timeout.
what could the possible problem be.
regards,

Runtime Error          TIME_OUT
       Occurred on     02/19/2009 at   10:35:35
Time limit exceeded.
What happened?
The program "SAPLE31C" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 5400 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.
successfully processed, the system gives it another 5400 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
You should usually execute long-running programs as batch jobs.
If this is not possible, increase the system profile parameter
"rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has an unsuitable index: Check index generation.
You may able to find an interim solution to the problem
~~~~~~~
The line to which it points is a select query on a table that has not records.

Short dump in table maintenance genarator

Similar Messages

Maybe you are looking for