Breakpoints

[Former Member]

Can any one explain difference between session break point and external break point.I searched links but i couldnt get exxact differences.

Arunkumar

[Former Member]

Hi Arun,

Same Topic has been discussed in this thread:

Regards,

Chandra Sekhar

[Former Member]

Hi chandra,

Can u give some more differences if u know..

Regards

Arunkumar

[former_member217544]

Hi,

Adding to that here is one more point:

External Break-Point:

This will be used when we want to debug the code from externla source( like from portal etc.). For instance if we want to check whether the parameters that are coming to the RFC from portal are passed correctly or not can be chacked and the RFC code can be debugged by keeping external break-point but the same is not possible with session break point.

Regards,

Swarna Munukoti.

[Former Member]

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.

Two types of breakpoints exist: External (HTTP) Breakpoints enable debugging in the Web browser. Session Breakpoints enable debugging within transactions. BEx Web Applications are usually executed in the Web browser. The query monitor (RSRT2) transaction allows you to display a BEx Web application in the SAP GUI. Depending on how you call up your Web application you can choose the appropriate breakpoint type.

· To be able to set an external breakpoint, you have to set the external debugging to active. You can set external debugging to active in the menu under Utilities ® Settings... ® ABAP Editor ® Debugging in the External Debugging field. .

Edited by: murali papana on Sep 4, 2008 12:29 AM

[Former Member]

hi ARUN,

Difference between session break point and external break pointa are:

1) sesson break-point can be user dependent whereas external break points are user independent.

2) external break points will be used when we want to debug the code from external source, but the same is not possible with session break point.

you can also refer to link :

hope it will help you

regards

Rahul sharma

[Former Member]

Hi Arun,

Please check this link.

http://help.sap.com/saphelp_nw70/helpdata/en/b0/940640555ae369e10000000a155106/content.htm

I hope this will help you.

Regards,

Amit Kumar Singh

[Former Member]

Hi,

If you set a breakpoint in the ABAP Editor, 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.

Thanx.

[Former Member]

Hi

Page no :18.

http://www.sap4u.org/media/userfiles/articles/pdf/26.pdf

Regards,

Sravanthi