<?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 report Dynpro in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694226#M1577261</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;With the new debugger its not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;· Classic ABAP Debugger &lt;/P&gt;&lt;P&gt;The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.&lt;/P&gt;&lt;P&gt;With the classic Debugger it is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit and are called recursively from a subordinate unit. For example, a conversion exit cannot be analyzed using the Debugger if it runs within a WRITE statement. However, with the new Debugger this is possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New Debugger &lt;/P&gt;&lt;P&gt;The new ABAP Debugger is executed in its own external mode (Debugger), while the application to be analyzed (debuggee) uses a second external mode. So far, the application to be analyzed and the debugger itself shared the same roll area of an external mode. For this reason, each action of the Debugger could influence the program flow of the application. Therefore, the classic Debugger cannot use any ABAP statements for designing the user interface. The path for designing modern UI techniques is not available for it. &lt;/P&gt;&lt;P&gt;The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the debugger at any time during a session under the menu option Debugging. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;Arbind Prasad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Feb 2011 10:24:17 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-02-22T10:24:17Z</dc:date>
    <item>
      <title>Debug report Dynpro</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694223#M1577258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I want to debug my report dynpro while is writing, with old debuger this could be done,&lt;/P&gt;&lt;P&gt; but with the new i cant, anyone knows how to do this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;J.Ortiz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 09:55:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694223#M1577258</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T09:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: Debug report Dynpro</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694224#M1577259</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;how u did that with old debugger.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Prabhakar....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 10:00:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694224#M1577259</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T10:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Debug report Dynpro</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694225#M1577260</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;Check this link &lt;A href="http://help.sap.com/saphelp_nw70/helpdata/en/43/95a6c84f7c60b7e10000000a11466f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw70/helpdata/en/43/95a6c84f7c60b7e10000000a11466f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 10:03:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694225#M1577260</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T10:03:23Z</dc:date>
    </item>
    <item>
      <title>Re: Debug report Dynpro</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694226#M1577261</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;With the new debugger its not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;· Classic ABAP Debugger &lt;/P&gt;&lt;P&gt;The Classic ABAP Debugger runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.&lt;/P&gt;&lt;P&gt;With the classic Debugger it is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit and are called recursively from a subordinate unit. For example, a conversion exit cannot be analyzed using the Debugger if it runs within a WRITE statement. However, with the new Debugger this is possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New Debugger &lt;/P&gt;&lt;P&gt;The new ABAP Debugger is executed in its own external mode (Debugger), while the application to be analyzed (debuggee) uses a second external mode. So far, the application to be analyzed and the debugger itself shared the same roll area of an external mode. For this reason, each action of the Debugger could influence the program flow of the application. Therefore, the classic Debugger cannot use any ABAP statements for designing the user interface. The path for designing modern UI techniques is not available for it. &lt;/P&gt;&lt;P&gt;The New ABAP Debugger, on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the debugger at any time during a session under the menu option Debugging. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;Arbind Prasad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 10:24:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694226#M1577261</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T10:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: Debug report Dynpro</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694227#M1577262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; hi...&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; how u did that with old debugger.....&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; Thanks,&lt;/P&gt;&lt;P&gt;&amp;gt; Prabhakar....&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you pass througth a write statement appears a new icon bettwen the watchpoint and F8 icon you can show your dynpro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks all for replies.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;J.Ortiz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 10:47:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/debug-report-dynpro/m-p/7694227#M1577262</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-22T10:47:13Z</dc:date>
    </item>
  </channel>
</rss>

