<?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 Re: Runtime error - POSTING_ILLEGAL_STATEMENT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869038#M929885</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There short dump might be due to an user exit. If you look into the ABAP debugger there is an option in Settings - &amp;gt; update debugging. &lt;/P&gt;&lt;P&gt;when you select it, the update debugging will be siwtched on. Now go an check the enhancemetns which are active for MIGO. For Ex- MB_DOCUMENT_BADI method -&amp;gt; AFTER UPDATE. ( Hope you are aware of Badi's ). Put a break point inside the BADI method, I meant the implementation which is active. If the there are any statements like MESSAGE.. CALL SCREEN . .It will take you to a short dump...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Might be one of the probable reason. .. Please investigate..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 May 2008 07:58:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-23T07:58:02Z</dc:date>
    <item>
      <title>Runtime error - POSTING_ILLEGAL_STATEMENT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869036#M929883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls advise how to resolve this runtime error issue mentioned below...which Im getting in PO creation and at the time of releasing the same but getting the error as background express document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;************Runtime error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks &amp;amp; regards&lt;/P&gt;&lt;P&gt;sankar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 May 2008 07:52:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869036#M929883</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-23T07:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime error - POSTING_ILLEGAL_STATEMENT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869037#M929884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Closed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Post a new one with clear details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regret inconvenience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;sankar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 May 2008 07:54:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869037#M929884</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-23T07:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: Runtime error - POSTING_ILLEGAL_STATEMENT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869038#M929885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There short dump might be due to an user exit. If you look into the ABAP debugger there is an option in Settings - &amp;gt; update debugging. &lt;/P&gt;&lt;P&gt;when you select it, the update debugging will be siwtched on. Now go an check the enhancemetns which are active for MIGO. For Ex- MB_DOCUMENT_BADI method -&amp;gt; AFTER UPDATE. ( Hope you are aware of Badi's ). Put a break point inside the BADI method, I meant the implementation which is active. If the there are any statements like MESSAGE.. CALL SCREEN . .It will take you to a short dump...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Might be one of the probable reason. .. Please investigate..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 May 2008 07:58:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-error-posting-illegal-statement/m-p/3869038#M929885</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-23T07:58:02Z</dc:date>
    </item>
  </channel>
</rss>

