<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579658#M1080382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It s giving the dump in standard program when executing the T.code ME22N&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Information on where termination occurred&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The termination occurred in the ABAP/4 program "SAPLMEPO " in "FIELD_SELECTION".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main program was "RM_MEPO_GUI ".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The termination occurred in line 103 of the source code of program "LMEPOF2T " (when calling the editor 1030).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please give me the analysys why it has occured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the program is&lt;/P&gt;&lt;P&gt;      if st_check &amp;gt; 250.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;      every 250 reads, see how big the buffer is&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;        st_check = 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        describe table gt_fs_buffer lines l_lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        if l_lines &amp;gt; lc_max_buffer.&lt;/P&gt;&lt;P&gt;          clear ls_buffer.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        too big; remove records with low hits;&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        then reset hit counter&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;          loop at gt_fs_buffer transporting no fields&lt;/P&gt;&lt;P&gt;            where hits &amp;lt; 10.&lt;/P&gt;&lt;P&gt;            delete gt_fs_buffer.&lt;/P&gt;&lt;P&gt;          endloop.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----" /&gt;&lt;P&gt;&amp;gt;          modify gt_fs_buffer from ls_buffer transporting hits.&lt;/P&gt;&lt;P&gt;        endif.&lt;/P&gt;&lt;P&gt;      endif.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Sep 2008 18:25:09 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-09-30T18:25:09Z</dc:date>
    <item>
      <title>TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579658#M1080382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It s giving the dump in standard program when executing the T.code ME22N&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Information on where termination occurred&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The termination occurred in the ABAP/4 program "SAPLMEPO " in "FIELD_SELECTION".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main program was "RM_MEPO_GUI ".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The termination occurred in line 103 of the source code of program "LMEPOF2T " (when calling the editor 1030).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please give me the analysys why it has occured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the program is&lt;/P&gt;&lt;P&gt;      if st_check &amp;gt; 250.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;      every 250 reads, see how big the buffer is&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;        st_check = 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        describe table gt_fs_buffer lines l_lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        if l_lines &amp;gt; lc_max_buffer.&lt;/P&gt;&lt;P&gt;          clear ls_buffer.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        too big; remove records with low hits;&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;        then reset hit counter&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;          loop at gt_fs_buffer transporting no fields&lt;/P&gt;&lt;P&gt;            where hits &amp;lt; 10.&lt;/P&gt;&lt;P&gt;            delete gt_fs_buffer.&lt;/P&gt;&lt;P&gt;          endloop.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-----" /&gt;&lt;P&gt;&amp;gt;          modify gt_fs_buffer from ls_buffer transporting hits.&lt;/P&gt;&lt;P&gt;        endif.&lt;/P&gt;&lt;P&gt;      endif.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 18:25:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579658#M1080382</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T18:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579659#M1080383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you check OSS Note 421506 - ME21N: Short dump TABLE_ILLEGAL_STATEMENT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
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.


&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 18:31:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579659#M1080383</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T18:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579660#M1080384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Aparna,&lt;/P&gt;&lt;P&gt;Is it the same note applies for ME22N also, what you have provided the noe is for ME21N,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please clarrify&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 19:36:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579660#M1080384</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T19:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: TABLE_ILLEGAL_STATEMENT dump in standard program transaction ME22N</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579661#M1080385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2008 19:42:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/table-illegal-statement-dump-in-standard-program-transaction-me22n/m-p/4579661#M1080385</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-30T19:42:22Z</dc:date>
    </item>
  </channel>
</rss>

