Debugging

[Former Member]

Hi All,

Debugging, how many are there? What is meant by Stopwatch?

Thanks & Regards,

<b>Anil Kumar</b>

[Former Member]

Hi

see t his document

reward if usefull

ABAP Debugger

The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.

As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.

Features

The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:

• Ways of starting the Debugger

• Choosing different views

• Choosing different execution options in the Debugger

• Displaying source code in the Debugger

• Setting and deleting breakpoints

• Setting and deleting watchpoints

• Stopping a program at a particular statement or event

• Displaying and changing field contents at runtime

• Displaying ABAP Objects and references

• Displaying and positioning strings

• Setting and deleting database locks

• Opening the ABAP Editor, or Object Navigator

• System settings and runtime warnings

Starting the Debugger

There are two possible strategies for starting the Debugger in the ABAP Workbench:

• By setting breakpoints then running the program

• By running the program in debugging mode.

Setting Breakpoints

A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.

Running a Program in Debugging Mode

You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also useful if you do not know the program very well and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:

From the Object Navigator Select a report or transaction and program and choose Program &#61614;&#61472;Test &#61614;&#61472;Debugging.

From the ABAP Editor Choose Program &#61614; Execute &#61614; Debugging (or the Debugging pushbutton).

From any screen Choose System &#61614; Utilities &#61614; Debug ABAP.

From any screen Enter " /h " in the command field.

Checking System Programs for Errors

To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System &#61614; Utilities &#61614; Debug system from any screen. To stop the system Debugger, choose Debugger &#61614; Debugging off.

Displaying Program Attributes

You can display the attributes Fixed point arithmetic, System program and Unicode checks active of the program that has just been executed by choosing Goto &#61614; Further Information &#61614; Program Attributes.

Display Modes in the Debugger

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.

Display Modes Available Using Pushbuttons

Fields 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. See also Processing Fields

Table Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables

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

Watchpoints 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. See also Setting Watchpoints

Calls 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.

Overview 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.

Settings This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings

Other Display Modes

You can access other display modes by choosing Goto &#61614; Display data object.

Single field Displays the contents and technical attributes of a field.

Structured

field Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.

Strings Display the content and current length of the string. You can also display part of the content by means of offset and length.

Internal table Displays the type, line numbers and contents of an internal table.

Object Displays the structure of an ABAP Object.

For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects

Breakpoints

Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.

There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.

Breakpoint Variants

The Debugger contains different breakpoint variants:

Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.

Directly-set

dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.

Breakpoint

at statement The Debugger stops the program directly before the specified statement is executed.

Breakpoint

at subroutine The Debugger stops the program directly before the specified subroutine is called.

Breakpoint at function module The Debugger stops the program directly before the specified function module is called.

Breakpoint at method The Debugger stops the program directly before the specified method is called.

Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.

Use

Static Breakpoints

Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.

Dynamic Breakpoints

Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. All dynamic breakpoints are deleted when you log off from the R/3 System.

Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:

• You do not have to change the program code

• You can set them even when the program is locked by another programmer

• You can define a counter (for example, only activate the breakpoint after it has been reached five times).

Special Dynamic Breakpoints

Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the program code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger.

Transferring Breakpoints to HTTP and Update Sessions

If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.

If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.

Static Breakpoints

You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.

Setting Breakpoints

To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.

program RSDEBUG_01.

....

if SY-SUBRC <> 0.

break-point.

endif.

....

When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 …).

Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.

However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.

Deleting Breakpoints

Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities &#61614; Global search. You can also use the Extended Program Check to find them.

If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.

Dynamic Breakpoints

You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.

Setting Dynamic Breakpoints in the ABAP Editor

You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:

1. Position the cursor on the line of the source code at which you want to set the breakpoint.

2. Choose Utilities &#61614; Breakpoints &#61614; Set or the Stop icon. The system confirms that the breakpoint has been set.

To display a list of all dynamic breakpoints in a program, choose Utilities &#61614; Breakpoints &#61614; Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.

Setting Dynamic Breakpoints in Debugging Mode

To set a dynamic breakpoint in the Debugger:

1. Position the cursor on the line in which you want to set the breakpoint.

2. Select the line by double-clicking it or choosing Breakpoint &#61614; Set/delete.

The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.

When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.

Breakpoints at Statements

You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.

Prerequisites

You must already be running the program in the Debugger.

Procedure

To set a breakpoint at an ABAP statement:

1. Choose Breakpoint &#61614; Breakpoint at &#61614; Statement...

2. Enter the ABAP statement.

The system sets a breakpoint at all points in the program at which the ABAP statement occurs.

3. Choose ENTER.

The breakpoint applies to all lines containing the specified statement.

Result

The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.

Breakpoints at Subroutines

You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.

Prerequisites

You must already be running the program in the Debugger.

Procedure

To set a breakpoint for a subroutine:

1. Choose Breakpoint &#61614; Breakpoint at &#61614; Event/Subroutine.

2. Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.

3. Choose ENTER.

Result

The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.

Breakpoints at Function Module

You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.

Prerequisites

You must already be running the program in the Debugger.

Procedure

To set a breakpoint for a function module:

1. Choose Breakpoint &#61614; Breakpoint at &#61614; Function module...

2. Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.

3. Choose ENTER.

Result

If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.

Breakpoints at System Exceptions

You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.

Prerequisites

You must already be running the program in the Debugger.

Procedure

To set a breakpoint at a system exception:

Choose Breakpoint &#61614; Breakpoint at &#61614; System exception.

Result

The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.

When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.

Saving Breakpoints

If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.

To save the breakpoints that you have set in the Debugger:

Choose Breakpoint &#61614; Save.

The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.

You can also delete breakpoints that you have saved:

• By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.

• By choosing Breakpoint &#61614; Delete all. In this case, the system deletes all dynamic breakpoints.

Managing Dynamic Breakpoints

The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto &#61614; Control debugging &#61614; Breakpoints.

Functions

This display mode contains the following functions for breakpoints:

Breakpoint Display

The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.

Counter

In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.

Deleting Breakpoints

Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint &#61614; Set/delete. To delete all breakpoints, choose Breakpoint &#61614; Delete all.

Activating and Deactivating Breakpoints

Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint &#61614; Activate/deactivate.

Watchpoints

Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.

Use

You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.

Features

• You can set up to five watchpoints in a program.

• You can also specify the conditions on which a watchpoint is to become active.

• You can specify logical conditions between up to five conditional watchpoints.

• You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.

• You can change and delete watchpoints.

Setting Watchpoints

If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.

A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.

Procedure

To set a watchpoint, start the Debugger and proceed as follows:

1. Choose Breakpoint &#61614; Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears.

2. Decide whether you want to set a local or global watchpoint.

3. Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.

4. If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .

5. To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.

Operator Meaning

< Less than

<= Less than or equal

= Equal

<> Not equal

>= Greater than or equal

> Greater than

6.

7. You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.

Result

The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.

Specifying Logical Links

If you have more than one conditional watchpoint, you can specify a logical link between them:

OR Only one of the specified conditions must be met

AND All of the conditions must be met.

To create a logical link between watchpoints:

1. Choose Goto &#61614; Control debugging &#61614; Watchpoints or the Watchpoints pushbutton to open the watchpoint display.

2. Set the Logical operator between watchpoints option.

The default value is always OR .

Changing Watchpoints

1. Choose Goto &#61614; Control debugging &#61614; Watchpoints or the Watchpoints pushbutton to display the watchpoint list.

2. Choose the pencil icon in the line containing the watchpoint you want to change.

3. Change the watchpoint attributes in the Create/Change Watchpoint.

3. Choose ENTER .

Deleting Watchpoints

You cannot delete watchpoints by choosing Breakpoint &#61614; Delete or Breakpoint &#61614; Deactivate/activate. Instead, proceed as follows:

1. Choose Goto &#61614; Control debugging &#61614; Watchpoints or the Watchpoints pushbutton to display the watchpoint list.

2. Choose the trashcan icon in the line containing the watchpoint you want to delete.

Memory Monitoring with Watchpoints

You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.

&objectname Displays the references of strings, internal tables as well as data and object references

*itab Displays the table header of the internal table itab

Analyzing Source Code

The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways.

Displaying the Source Code

All of the display modes in the Debugger have the same structure. The top half of the screen displays an extract from the program source code as it appears in the ABAP Editor.

Features

The Source code of field contains an extract from the program, subroutine, or function module currently being processed. The source code display also contains the following additional functions:

Expand/Reduce Program Segment

Use this button to close the information about the current display mode. The system then displays more of the source code.

Use this button to reopen the information for the current display mode.

Entering Line Numbers

You can scroll in the source code using the arrow keys. If you enter a line number in the left-hand field, that line will become the top line of the display.

Scrolling by Double-Clicking

If you double-click the first column of a line, it becomes the top line of the display.

Scrolling one Screen at a Time

You can use the PgUp and PgDn keys to scroll up and down one page at a time in the source code.

Navigating Forwards and Backwards

If you choose Debugging &#61614; Goto Statement, the line containing the cursor is displayed. This provides you with a straightforward way of navigating forwards and backwards in the displayed source code.

Displaying the Current Line

This arrow indicates the next line of source code that will be processed.

Use this button to make the current line appear in the source code display.

Display After a System Exception

When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.

Finding a String in the Source Code

To find a string in the source code, choose Edit &#61614; Find in source code or the Find icon from the standard toolbar. A dialog box appears in which you can enter a string:

To find the next occurrence of the same string, choose Edit &#61614; Find next in source code, or the appropriate icon.

[Former Member]

Hi ,

You can debugg in Five ways:

First Step: Initial screen of se38 , There is buttom in application tool bar is call Debugging , u just click on that and go to debugging screen , when ever u debug the any think first of all activate the program .

Second Step: Set the breapoint .

3rd Step: write the hard code 'break-point' in the program and debug.

4th step: using /H command u can debug .

5th step:Goto Sap Easy Access screen , In the Standard tool bar there is buttom is called Generaets a shortcut it' near by activate buttom , click that Generates shortcut then a sceen will come at that screen Just choose Type: System Command and Command : /H .

Then Press enter .

It will creat a shortcut in ur comuter .

what ever screen and program u want to debugg , just drag and place that shortcut to that progarm and screen , plz try it and tell me it's working or not .

Regards,

Nihar Swain.

[Former Member]

Hi,

Debugging Document.

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

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

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm

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

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

Debugging is used to check whether the logic which we have written works correctly. There are 2 types of debugging :

1. Static Debugging

2. Dynamic Debugging.

We go for static debuging when we know the line of code where we want to debug. you can use break-point statement in your code in order to debug it, else u can use the Red color stop button to set the break-point.

We go for dynammic debugging, when we want to know the program flow while we are executing the program. Hence dynammic debugging is done only during the runtime of the program. For that we have to use /h command in the transaction code in order to debug when we execute the program

System Debugging

If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Update Debugging

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

Normal Debugging

Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

For debugging tutorial:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://www.sapdevelopment.co.uk/tips/debug/debughome.htm

http://www.sap-basis-abap.com/sapab002.htm

Regards,

Priyanka.

[Former Member]

hi,

hi,

go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->

f5-used for line by line debugging

f6-used for directly executing function modules or performs i.e. control won't go into that block.

f7-run to cursor

f8-direct executing.

fileds: here we can check fild values.

click fileds option and double click on the filed or type the filen name beside filed

tables : here we can check the data in the internal table.

click tables option and double click on the internal table.

Break points:

if you want to debug a particulr part you can use this.

place the cursor at any perform click breakpoint or double click on that line.it will be set.

if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.

Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.

debugging procedure:

Use '/H' in the command line and execute the report/program, so that it goes to debugging mode

2. keep a hard coded break point in the code like BREAK-POINT and it stops there.

3.From the program Menu, Keep the Soft Break-points and do the debugging.

see the links

Refer to this thread

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

Check these documents.

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_nw04/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

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

http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm

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

http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm

http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34

Look at the SAP help link below

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

[Former Member]

refer these links

http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm

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

regards,

srinivas

[Former Member]

Hi,

You can debug in six ways.

1) Put break points where eevr you need by selecting STOP(Red button) button in the programme.

2) User specific Debugging. BREAK User name. Example: If your logon user name is anildas then the user specific break point should be BREAK anildas.

in this case Debuging will only occur when user login with anildas.

3) One more is BREAK-POINT. It allows ever user for debugging.

4) in the command field of the selection screen simply put /H and enter it will allows you to debug the program.

5) If you are already in debug screen and if you want to set break points at particular statement like at subroutine or method or function module etc. then go to path Breakpoint-Breakpoint at -

6) If you are already in debug mode then go to line where ever you need put break point and double click on the first column of the line.

Watch point : Watch point is another method of debugging . You can create watch point only in debug mode . Wacth points allows you to specify the value for particular field. Supose if you are in debug mode and you dont want to debug the program until some field reached to some value and once it reached to particular value then you want to check furhter steps.

For creating watch point : In the application tool bar you have one button called create watch point click on that and you will see one pop-up asking for Field name Relational Operator and Comp. field/value. Dont check box for comarision field. and enter.

Thanks,

Nageswar