Skip to Content
avatar image
Former Member

TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N

It s giving the dump in standard program when executing the T.code ME22N

Information on where termination occurred

The termination occurred in the ABAP/4 program "SAPLMEPO " in "FIELD_SELECTION".

The main program was "RM_MEPO_GUI ".

The termination occurred in line 103 of the source code of program "LMEPOF2T " (when calling the editor 1030).

please give me the analysys why it has occured.

the program is

if st_check > 250.

  • every 250 reads, see how big the buffer is

st_check = 0.

describe table gt_fs_buffer lines l_lines.

if l_lines > lc_max_buffer.

clear ls_buffer.

  • too big; remove records with low hits;

  • then reset hit counter

loop at gt_fs_buffer transporting no fields

where hits < 10.

delete gt_fs_buffer.

endloop.

-


> modify gt_fs_buffer from ls_buffer transporting hits.

endif.

endif.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Sep 30, 2008 at 06:31 PM

    Did you check OSS Note 421506 - ME21N: Short dump TABLE_ILLEGAL_STATEMENT.

    Summary
    
    Symptom
    
    You create a purchase order with Transaction ME21N. In case of large purchase orders, a short dump can
     occur if you scroll between the items.
    
    Additional key words
    
    ME22N, GT_FS_BUFFER, short dump
    
    Cause and prerequisites
    
    The problem is caused by a program error. The problem only occurs after the implementation of Note 
    368585 or after the import of R/3 Support Package 20 for Release 4.6C. In Release 4.6B, the problem does
     not occur. Here, only one correction was made to update the source code to the same status.
    
    
    Solution
    
    An advance correction is available.
    
    
    

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      It could be the same. It depends on what is triggering the dump. If the reason is the one described in the note then the note applies to your case. Check the OSS note and see if it can be applied to you system depending on the patch level.