What is External Break points?

Question

Hello,
What are external Break points...?
My issue : I need to check a condition in the Source code...
What do I need to do to get control at that condition directly to check whether the data is passing in those tables or not?
Any suggestions would be appreciated...
Regards,
Krishna Chaitanya

Answer 1

Hi,
Breakpoints
Setting and editing breakpoints, too, in the new Debugger is almost identical to the classic Debugger. However, several breakpoints can be set simultaneously in the new Debugger if you choose the path Breakpoint ® Create Breakpoint. Afterwards, the system displays a window in which the following options are available.
Here it is obvious that, in contrast to the classic Debugger, all the input fields u2013 with the exception of those in the ABAP command tab u2013 have a search help function (function key F4). For example, under the Method tab you enter a certain class. Then, in the search help, all the methods that belong to this class are proposed.
There are also certain differences when setting and deleting breakpoints. A double-click within a source code line creates a breakpoint in this line in both Debugger types, provided the cursor was not positioned on an ABAP keyword. A second double-click in the same line deletes this breakpoint in the classic Debugger, while it is only deactivated in the new Debugger.
Breakpoint Types
When you set a breakpoint in the Debugger, it is created as a debugger breakpoint by default. A debugger breakpoint is only valid while the Debugger instance, in which it was set, is active. When the Debugger is closed, all debugger breakpoints set in it are deleted.
If you set a breakpoint in the ABAP Editor, for example, this breakpoint is a session breakpoint. Session breakpoints remain active independently of the existence of a Debugger and are valid for all external sessions of a logon. Within the Debugger, you can convert a debugger breakpoint into a session breakpoint and vice versa.
If the setting Session Breakpoints Active Immediately is checked (via Utilities ® Settings ® ABAP Editor ® Debugging in the ABAP Editor or Object Navigator), you can set a session breakpoint in an external session of a logon to force a running program into the Debugger that runs in the same logon (for example, in an external session) and will process the point at which the session breakpoint was set.
User breakpoints (previously known as external breakpoints) are valid for all user logons on the current server of the current system. User breakpoints are specifically required when debugging BSP or Web Dynpro applications. In these cases, you do not log on using the SAP GUI but via a browser, for example. Therefore, any breakpoints must be set before logging on.
User breakpoints are only valid for a period of 2 hours.
As of Release 7.00, user breakpoints set for BSP or Web Dynpro applications are also valid for SAP GUI logons.
Within the Debugger, you can convert debugger or session breakpoints into user breakpoints and vice versa.
External Debugging
Use
You can use debugging in order to carry out detailed troubleshooting. With the debugger, you check a given section of code in the Request Handler or an ABAP function module for errors.
Basically, there are two different types of debugging:
·        With conventional debugging, you can analyze programs that you call up within your own user session on the server, with breakpoints being set at corresponding points in the coding.
·        With external debugging, you can analyze programs that are called up by an external user with HTTP. For the purpose of external debugging, special breakpoints (external breakpoints) are set on the target server.
Two variants are available for conventional debugging: the classical variant and the new (2-processor) variant, which creates a separate session for the debugger. At present, external debugging can only be performed with the classical variant.
This section deals especially with external debugging, as it is generally makes sense to call up an external user completely (with all sent parameters) in one step when investigating ICF processes.
Prior to Release 640, the external debugging described below was known as HTTP debugging.
Prerequisites
·        If you use load distribution for your system environment, the server group (logon group) is reduced to one server before debugging commences.
·        Ideally, the user who performs the debugging should not be a collective user.
Activities
Note that the troubleshooting method described here can affect your system performance. You should therefore only activate it if you really need it. You are advised to monitor the corresponding settings regularly and to deactivate any functions you no longer require.
In transaction SICF, you can use the external debugger to set external breakpoints and check the debugging of the relevant section of code:
       1.      Select the required service in the service hierarchy.
       2.      Choose Edit ® Debugging ® Activate Debugging.
       3.      Enter the required data (if you have selected the service previously, the system will propose the service path for you). 
Reward If Helpfull,
Naresh.