<?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 ABAP Dump in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848334#M359625</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What is abap dump ?&lt;/P&gt;&lt;P&gt;How to see runtime errors in ABAP ?&lt;/P&gt;&lt;P&gt;Bye,&lt;/P&gt;&lt;P&gt;muttu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Feb 2007 13:42:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-02-03T13:42:28Z</dc:date>
    <item>
      <title>ABAP Dump</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848334#M359625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What is abap dump ?&lt;/P&gt;&lt;P&gt;How to see runtime errors in ABAP ?&lt;/P&gt;&lt;P&gt;Bye,&lt;/P&gt;&lt;P&gt;muttu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Feb 2007 13:42:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848334#M359625</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-03T13:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Dump</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848335#M359626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can check the same in Tcode ST22 (abap dump analysis ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can click on that particular dump and check the details .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;vijay.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Feb 2007 13:45:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848335#M359626</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-03T13:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Dump</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848336#M359627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dynamic Check&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Errors that cannot be detected statically and that occur at runtime are detected by the ABAP runtime environment. Such errors lead to exceptions. If an exception is not handled or cannot be handled, a runtime error occurs. If such a runtime error occurs, the ABAP runtime environment terminates the program, generates a short dump, and switches to a special screen from which you can analyze it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Short dumps are divided into blocks describing different aspects of the error. In the overview, you can see what information is contained in the short dump, for example, the contents of data objects, active calls, control structures, and so on. The short dump overview also allows you to display the point in the program at which the termination occurred in the ABAP Debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following kinds of errors can occur:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Internal error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The kernel encountered an error. In this case, inform SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Installation and environment or resource error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An error that occurred due to incorrect system installation or missing resources (for example, database closed).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·        Error in application program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typical causes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Contents of a numeric field have the wrong format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arithmetic overflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;External procedure does not exist.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type conflict when passing parameters to an external procedure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Short dumps are retained in the system for 14 days. Use Transaction ST22 to administer short dumps. If you want to retain a short dump beyond the default 14 days, use the Keep function. If you want to delete short dumps by a date criterion other than the default 14 days, choose Reorganize. If you display a short dump using Transaction ST22, you cannot branch to the Debugger.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If problems occur in an ABAP program that you cannot solve yourself, you can send an extract of the short dump to SAP. The contents of the short dump are essential to the SAP Hotline and Remote Consulting to enable them to solve your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Feb 2007 14:16:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848336#M359627</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-03T14:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP Dump</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848337#M359628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this description is good and useful. Let me make 2 small additions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A program may issue messages of different types&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type I and S are just for information, they will not affect the program flow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;W - Warnings warn you about certain things. In online programs issued during screen processing the WARNING takes you back to the screen that you have to confirm the value entered or change it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E - will stop program flow.  In online programs issued during screen processing it takes you back to the screen where you have to change something to avoid the message&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;X - In some situations, especially those that are not planned to occur at all, the program issues an X message. Then it terminates and creates a DUMP. This is meant to help to analyze the situation and find out how this could happen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a DUMP occurs in online processing the program switches to dump list screen with a DEBUG button on the top. If you´hit the DEBUG button the debugger starts and is positioned to the statement where the dump occured. All programs are still loaded in memory allowing to check all fields values, call hierarchy, system and user tables and so on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Feb 2007 15:18:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-dump/m-p/1848337#M359628</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-02-03T15:18:52Z</dc:date>
    </item>
  </channel>
</rss>

