<?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: debug include in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417032#M820656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Direct Processing&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;From the Object Navigator&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Select a report or transaction and choose Program -&amp;gt; Test -&amp;gt; Debugging.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From the ABAP Editor&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Choose Program -&amp;gt; Execute -&amp;gt; Debugging (or the Debugging pushbutton).&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From any screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Choose System -&amp;gt; Utilities -&amp;gt; Debug ABAP.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From any screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Enter /h in the command field.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Display Modes in the Debugger &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Display Modes Available Using Pushbuttons&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Fields&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Feb 2008 07:10:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-14T07:10:12Z</dc:date>
    <item>
      <title>debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417029#M820653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am working on a include related to USer Exit for Va02 .Here for debugging ,I understood from SDN that we have to give /h,But where to giv is it in the main screen of the va02 or in the se38 include program or where ? plese give process&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:07:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417029#M820653</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:07:36Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417030#M820654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;put a breakpoint at the include.. and execute va02...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:09:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417030#M820654</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2008-02-14T07:09:32Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417031#M820655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;while running the transaction put /h&lt;/P&gt;&lt;P&gt;r else put a breakpoint in the include&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:10:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417031#M820655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:10:04Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417032#M820656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;lt;b&amp;gt;Direct Processing&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;From the Object Navigator&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Select a report or transaction and choose Program -&amp;gt; Test -&amp;gt; Debugging.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From the ABAP Editor&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Choose Program -&amp;gt; Execute -&amp;gt; Debugging (or the Debugging pushbutton).&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From any screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Choose System -&amp;gt; Utilities -&amp;gt; Debug ABAP.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;From any screen&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Enter /h in the command field.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Display Modes in the Debugger &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Display Modes Available Using Pushbuttons&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Fields&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:10:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417032#M820656</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:10:12Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417033#M820657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if this break-point is to find when this user-exit is getting triggered.....then write the foll code inside ur include(UE)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;BREAK-POINT.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Donot forget to remove this statement before transporting....&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;jose.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:11:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417033#M820657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417034#M820658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or you can directly put a hard coded break point in your user exit and execute when ever control comes to user exit that will stop the t-code there and from that place start your verification by pressing F5 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or if you want to debug a perticular screen then enter /H in the command bar &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and press enter &lt;/P&gt;&lt;P&gt;after that if you do any action coresponding to that screen then it will take you to debug mode&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:12:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417034#M820658</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: debug include</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417035#M820659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to debug VA02 then you will put /h in the command field one you have given /h whatever action you perform on the screen now will take you to debugging mode,&lt;/P&gt;&lt;P&gt; and if you just want to debug that particular include give /h in se38. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Gunjan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Feb 14, 2008 3:46 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2008 07:13:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-include/m-p/3417035#M820659</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-14T07:13:24Z</dc:date>
    </item>
  </channel>
</rss>

