Debugging options

[Former Member]

Hi all,

Could anyone explains various debugging options?

Thanks and Regards

Chand

[Former Member]

Use this link for a detailed study

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm

[Former Member]

http breakpoint,

break sy-uname.

break-point.

/h option

and save this following code to notapad

[FUNCTION]

Command=/H

Title=Debugger

Type=SystemCommand

and drag this to sap screen, debugging will satrt,

and along with

in system->utilities->you can find system,abap,screen debugging..

vijay

[Former Member]

Pls check the forums for any posts on the same, there should be plenty..here is just a hint...

Activate the Debugger before executing your ABAP program

System -> Utilities -> Debug ABAP/4

The purpose of the debugger is to allow you to execute your program line by line. It also allow you display the data as you execute the program. (double click on the varaible field name and it will be display)

or after program have been executed,

Run transaction SM66 and find your work process.

Select the line of your work process and double click on it Click the debugging option.

If this is a custom program, you can put a wait statement in the code to buy yourself some time.

1) To understand the Watchpoint, you have to play with it.

a) Debug your program.

b) Place your cursor on the field you want to watch

c) Press Shift+F8, or click the Create Watchpoint button

d) Select the LOCAL WATCHPOINT checkbox if you want the watchpoint to be active for the immediate program only (and not includes etc. By default, you want to leave this unchecked).

e) Drop down on the relational operator, and choose one. They are self-explanatory. (For this example, use '=')

f) Select the COMPARISON FIELD checkbox if you want to check the field against another field, else leave unchecked if you want to check your field against a static value.

g) Enter your comparison field (if you checked the previous box) or your check value in the last box. Once your selected field equals the selected value, the program will break as if a breakpoint was reached. It is possible that the program never breaks, meaning your watchpoint criteria was never satisfied (For example if you check Itab-Field = VALUEA, if Itab-field never have a value equal to VALUEA the program will NOT break.)

2) I use SQL Trace is used for analysis, then based on the information retrieved I do manual tuning.

Let me know if u need more info...

F5 is single step debugging, f6 is a block of coke like select statements or subroutines,F7 does a return from a code unit like subroutine or function module and F8 stops the debugging and executes the entire code

[Former Member]

1) Use /H transaction code

2) Set the Break-potin in progrram and then execute

3) Se38>Program>Execute-->Debugging

[Former Member]

Hope this thread helps you.

Tharani

[Former Member]

<b>Display Modes in the Debugger</b>

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.

<b>Display Modes Available Using Pushbuttons</b>

<b>Fields</b>

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.

<b> Table</b>

Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table.

<b>Breakpoints</b>

A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display.

<b>Watchpoints</b>

You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated.

<b> Calls</b>

This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.

<b> Overview</b>

This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.

<b> Settings</b>

This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options.

[Former Member]

Hi chand,

This topic has been already discussed. The link is...

Hope it helps.

Regards,

Maheswaran.B

Message was edited by: Maheswaran B

[Former Member]

Hi Shaik,

I think u r new to Debugging.

There are Four Keys which are Usefull for debugging

F5,F6,F7,F8.

F5- it helps u to go line by line

F6- it helps u to skip a Subroutine.

F7- it helps to come out of the Loop and also any Function Module.

F8-- if at all any Break-Points are u can skip to the Break Poin.

The options which will be used Normally are

Break-Point and Watch Point.

Break-Points can be set at any function module ,Field to navigate fast while debugging.

Watch Points are used to set the value of the Field and while the Process is going on and once the field reaches particular vale u can view it at that point.

Regards

Usha