Break points

[Former Member]

Hi all

Please explain about breakpoints..what exactly can we do with breakpoints.if possible with a small example..

Points will b rewarded

Thanks in advance

manu

[Former Member]

Breakpoints are where you want to stop in the code on a specific statement during execution. You can have static as well as dynamic breakpoints in the program..

Refer to the link for details regarding Breakpoints -

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617cc1e68c11d2b2ab080009b43351/frameset.htm

[ferry_lianto]

Hi,

Break Points:

When you set a break point in your program, which executing when the control encounters the break point it stops at that place without executing the command on which you have set the break point.

Please check this link for more information and samples.

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617cbee68c11d2b2ab080009b43351/content.htm

Regards,

Ferry Lianto

[Former Member]

Hi guys

I went thru those materials...i still cant understand how to do that...please explain me with a small code r snapshots...

Thanks

manu

[Former Member]

Hi,

Breakpoints are usually used inorder to execute a program in debug mode i.e,, if we want to see the how the execution is happening i.e., line by line execution of the program can be seen. there are two types of breakpoints- Soft Breakpoint and Hard Breakpoint. in a program if you write the Statement like Break <userid>. then it becomes Hard break point. during execution control will stop at the line where you have specified such statement. from then onwards you can execute line by line by pressing F5 key.

on the other hand in SE38 transaction for your program, if you set a break point by hitting the pushbutton "Set Breakpoint" then it becomes Soft breakpoint. the execution is the same. but the only difference is once you close the session this soft breakpoint will not available however, the hard breakpoint will last forever until you delete the statement Break <userid>.

hope u will understand concept of break points.

thanks,

sksingh

[Former Member]

Hi srinivas

Thanks for ur answer..say for ex in the code if iam not getting the values i expected how its going to help me.

Thanks

manu

[Former Member]

Breakpoints is the best way to identify and fix errors in the programs. For eg, if you are running a report and it is dumping at specific point in the program or the result is not as expected. Then you can keep a breakpoint at that step (hardcoded or dynamic) and run report. As it reaches the breakpoint, it will sho you debugger screen and you can see values of variables at runtime. Using Single step you can execute step by step and find exact reason for the error. I hope this will help you.

[Former Member]

Debugging is tool for to find out solution in runtime.

Break points are two types :

1 Dynamic Break point

2.static break point.

dynamic break point means - /h or click on stop button

Static break point - writing the command like break user id.

you can set up 30 break point for each program..

Sometimes data is coming wrong and you need find out programtically and to see th code it is some what hectic.

you know what values getting wrong so you keep break point some where in the program and you will work in the debugging.

keep on chnaging debugging values and you will get results related to functional issues.

[Former Member]

Hi,

If you are not getting any values which you have expected, then only we go for Break point. Usually we set a break point from the first statement under Start-of-selecton event. And from there onwards we have to debug the program by pressing F5 key and see what values are being populated in Variables, Internal tables etc. Check if any conditions are failing which they are not supposed to be.

thanks,

sksingh