Regarding watch points in ABAP debugger

Hi,
Could u explain , why we use watch points, what is the use of it
and how to use it.
Thanks & regards,
[email protected]

Watch points
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/14/6d1c370c468b7be10000009b38f936/frameset.htm
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.
See also Setting Watchpoints.
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.
See Specifying a Logical Expression.
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.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with 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:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
ashish
Message was edited by:
        Ashish Gundawar

Similar Messages

  • What is the utility of watch point and break point in ABAP DEBUGGING !

    What is the utility of watch point and break point in ABAP DEBUGGING !
    PLEASE TELL ME IN DETAILS AND IF POSSIBLE WITH SCREEN SHOTS !

    Hi,
    Breakpoints, Watchpoints, and Checkpoints
    Summary
    The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
    Detailed Description
    Breakpoints
    In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, …) is displayed for each breakpoint.
    If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
    The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
    You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
    In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
    Watchpoints
    In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
    For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
    In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton „Compare Variables“( ) and choose the Diff tool to compare the old and new variable values.
    In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
    Checkpoints
    In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
    Pls refer to :
    http://help.sap.com/saphelp_nw70/helpdata/en/e2/5f5a42ed221253e10000000a155106/frameset.htm
    Regards,
    Renjith Michael.

  • What is utility of watch points and break point  in ABAp debugging !

    What is utility of watch points and break point  in ABAp debugging !

    Hi,
    Breakpoints, Watchpoints, and Checkpoints
    Summary
    The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
    Detailed Description
    Breakpoints
    In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, …) is displayed for each breakpoint.
    If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
    The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
    You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
    In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
    Watchpoints
    In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
    For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
    In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton „Compare Variables“( ) and choose the Diff tool to compare the old and new variable values.
    In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
    Checkpoints
    In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
    Regards,
    Renjith Michael.

  • Watch Point

    Hi Experts,
    Can any one explain me about Watch Points ?
    What are the differences between debugger and watch points ?
    Can any one explain me how to use watch points with any sample program,  if   provided with screen shots. I will give full points if any one explain with sample program with screen shots.
    Pls send me to [email protected]
    Thanks in Advance
    Regards and Thanks
    Vijaya

    Hi vijaya,
    check the below links for watch points
    Setting Watchpoints
    http://help.sap.com/saphelp_erp2005/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/frameset.htm
    Changing Watchpoints
    http://help.sap.com/saphelp_erp2005/helpdata/en/c6/617ce2e68c11d2b2ab080009b43351/frameset.htm
    Watchpoint with the new debugger 5.0
    Go through these threads for more information on debugging,
    1) debugging
    2) debugging
    3) Debugging
    4) Debugging
    some more links .....
    Introduction: http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
    A PDF file to know knowledge about Debugging
    Some more links:
    http://www.sap-basis-abap.com/sapab002.htm
    Debug Background Programs: http://www.sapdevelopment.co.uk/tips/debug/debug_backjob.htm
    Debugger: http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    If you need futher information plz do let me know
    ~~Guduri

  • What is watch point and break points?what are there types?

    what is watch point and break points?what are there types?

    Static Breakpoints
    Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
    In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
    Dynamic Breakpoints
    Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. 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 that only activates the breakpoint after it has been reached.
    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 source 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. For more information, refer to the chapter Dynamic Breakpoints.
    In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
    Watch point are used to put logical break point for a certain condition..Example..If you want to know when the internal table is getting append..Then you have to give the program name and the internal table in the watch point.. 
    Steps to create a watch point.
    Start debugging '/H'.
    In the debugging screen press the create watch point button in the application tool bar..
    In the program give the program name..
    in the field give the field name.
    In the relational operator given '='
    In the comp. field/value give the value ..
    Hope this helps..
    Regards,
    Parvez.

  • Create PO cause ABAP debugger

    Hello all:
    When i use me22n/me23n to change/display PO,as soon as i click Item Detail, the ABAP debugger screen popup.
    I know nothing about ABAP,the code is "method IF_EX_ME_PO_PRICING_CUST~PROCESS_KOMK.
    BREAK-POINT. endmethod."
    Can somebody gave me some advice?
    With Regards
    Edited by: king xin on Nov 11, 2010 4:05 AM

    Hi,
    It seems you have asked you ABAPer to apply some code for pricing in BADi and he would have activated the Break-Point for this. Just show to him and ask him to delete the Break-Point.

  • Abap debugger automatically starts up on running query

    Hi All,
    I have a BI 7.0 system. When executing one of the queries from rsrt. It automatically opens of the new abap debugger screen. Any idea how to disable that ?
    Best Regards,
    Vikash

    Hi Vikash,
    please check the BREAK-POINT statement you detected - you may have posted it here including the source name where you found ist.
    Starting with ABAP600 we have the syntax BREAK-POINT { [ID group] .
    If you have any ID here, you should check transaction SAAB for this group. Possibly is has been activated for Break-Points to stop on the server.
    Regards,
    Clemens

  • Types of watch points and break points

    hi to all
              what are the different types of watch points and  break points

    Hi Mahesh!
    Breakpoints
    In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, u2026) is displayed for each breakpoint.
    If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
    The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
    You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
    In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
    Watchpoints
    In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
    For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
    In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton u201ECompare Variablesu201C( ) and choose the Diff tool to compare the old and new variable values.
    In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
    For details
    http://help.sap.com/saphelp_nw70/helpdata/en/e2/5f5a42ed221253e10000000a155106/content.htm
    Reward points if helpful.

  • Abap debugger sarts with any transaction

    hi experts,
        recently i have installed netwaver 7.0 sneak preview on my system until now it was working fine
        bit today when i activate transformation,dtp,infopackage... anything transaction ends in abap debugger
        in program GENERATOR object reference METRSDS cant find any dump or trace in st22 or st11.
        please help me out.
    sanjeev

    Hi Gilberto,
    if you set a break-point and system can't stop there, then you can see a system log entry (SM21). Can you see system log entries regarding your break-points?
    If not, then I think your break-point can't be reached for delivery.
    The include is for all orders, deliveríes and billing documents I think.
    You can show us the code part where you want to set the break-point!
    Regards,
    Klaus

  • Watch points

    Hi all,
    I know that there are two ways of debugging in ABAP. One is setting the breakpoints and the other is watchpoint.Can anyone please explain me what is watch point, what is the need of going for that when we have debugging option, And how to work with watch point ? what is the difference between local and global watch point.
    Regards,
    Varun.

    Hi Varun,
    watch points are used explicitly to stop for a particular record with some value.
    say i have 10000 records , i am looping that itab, i cannot say F5 , to see for a particular record, in that case we will create watch point on itab-field which is equal to some value , when you say F8, then it will stay exactly that particular record.
    it will save the debugging time.
    for more info read this SAP help ..
    http://help.sap.com/saphelp_webas610/helpdata/en/c6/617ce2e68c11d2b2ab080009b43351/content.htm
    regards
    vijay

  • Differences between ABAP debugger of 4.7 and ECC 6.0

    Hey guys,
    I would really appreaciate any statements/documents that can help me determine the differences of abap debugger between these 2 versions.
    Thanks a lot in advance.
    Rgds,
    Mark

    Debugger in R6.1
    Modification 1
    Displaying program attributes
    If you choose Goto → Further Information → Program Attributes then the system will display the attributes fixed point arithmetic, system program, and Unicode check.
    Modification 2
    Displaying data references
    If you double-click a data reference in the Field Name column then the subsequent screen will contain technical information about that reference. A double click in the Field Contentcolumn will display the content of the data reference. The object referred to will be displayed, if you doubleclick the data reference dref->*in the Field Name column.
    Modification 3
    Special display of deep data objects
    To display the headers of strings, internal tables, data references, and object references, you must prefix them with an asterisk. For example, to display the header of the internal table itab in hexadecimal form, you must enter *itab in the Field Namecolumn. In the case of tables without headers the field content only contains zeroes.
    If you prefix the data object name with an ampersand, the relevant reference to the string, internal table, data reference, or object reference is displayed in hexadecimal form. For example, specifying &str will display the reference to the string str.
    Modification 4
    Setting breakpoints in methods
    By choosing Breakpoint → Breakpoint at → Method you can set a breakpoint for a method.
    Modification 5
    Support for class based-exceptions
    The following functions are available if an exception occurs:
    If the INTO ref addition is missing from the CATCHstatement, you can create an exception object in the Debugger under Settings.
    If you choose the Display Exception Objecticon, the system will display the attributes and interfaces of the exception class with their contents in the subsequent screen.
    If you choose Statement That Caused the Exception the system goes to the line in the source code in which the exception was caused. The statement that caused the exception is explicitly indicated in the source code.
    Modification 6
    Debugging mode for Business Server Pages with ABAP scripting
    Business Server Pages (BSP) can now be run in debugging mode. It is also possible to display and set breakpoints. Business Server Pages can be displayed in the Object Navigator, if you select an appropriate application by choosing BSP Applications.
    Modification 7
    Copying breakpoints from HTTP and update sessions
    If you call an HTTP or update session from a logical unit of work (LUW) then a new work process will be started for this session. Any breakpoints that were set in this calling logical unit of work are carried over to the new sessions and can be displayed by choosing Breakpoints. For example, if you call the update module funcusing CALL FUNCTION func IN UPDATE TASK, then the new work process will be displayed in a new window, provided you selected Update Debugging under Settingsin debugging mode. Here you can process all the breakpoints that were set in the calling logical unit of work.
    Modification 8
    Displaying instructions for the database interface
    You can now check the last statements sent to the database. In order to do so, choose Goto → System → System Areasafter the Debugger has been started and enter Area = OSQL in the input field.
    Modification 9
    Forward and backward navigation in the source text
    If you choose Debugging → Goto Statement, then the system will go to that line in which the cursor is positioned. This allows simple forward and backward navigation within the displayed source code.
    Modification 10
    Displaying memory consumption
    If you choose Settings → Memory Display On/Off, the system displays the memory consumption for objects, tables, references, or individual fields. In so doing, it differentiates between allocated and referenced memory and also displays the memory consumption actually used for every data object.
    To see a hit list of the 25 data objects with the highest memory consumption choose Goto → System → System Areas. The following values can be entered in the Areafield:
    ITAB-TOP25 for the display of internal tables
    OBJ-TOP25 for the display of objects
    REF-TOP25 for the display of references
    ALL-TOP25 for the display of all data objects
    Modification 11
    Displaying Unicode fragment view
    If you choose Goto → Display Data Object → System Information, the system displays the Unicode fragment view. In this view structures, internal tables, strings, data references, and objects are broken down into alignment gaps, byte areas and chracter-type areas and all other types - such as P, I, F, strings, references or internal tables.
    The system groups adjacent, character-type components - with the exception of strings - only if there are no alignment gaps between these components. In so doing, it observes all alignment requirements. In the same way, adjacent byte-type components are also grouped together.
    reward appropraite points.
    Regards,
    Mansi.

  • Break points and watch points

    Hi all
       Can anybody help me using break points and watch points.what do they exactly do as well..
    Thanks
    abap user

    Hi
    <b>Breakpoints</b>
    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 <b>change. For further information, refer to Watchpoints.
    Breakpoint Variants</b>
    The Debugger contains different breakpoint variants:
    <b>Static</b>     The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
    <b>Directly-set</b>
    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.
    <b>Breakpoint</b>
    at statement     The Debugger stops the program directly before the specified statement is executed.
    <b>Breakpoint at subroutine</b>     The Debugger stops the program directly before the specified subroutine is called.
    <b>Breakpoint at function module</b>     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.
    <b>Breakpoints at system exceptions</b>     The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
    <b>Use</b>
    <b>Static Breakpoints</b>
    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.
    <b>Dynamic Breakpoints</b>
    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).
    <b>Special Dynamic Breakpoints</b>
    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.
    <b>Transferring Breakpoints to HTTP and Update Sessions</b>
    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.
    <b>Static Breakpoints</b>
    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.
    <b>Dynamic Breakpoints</b>
    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.
    <b>
    Breakpoints at Statements</b>
    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.
    <b>Breakpoints at Subroutines</b>
    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.
    <b>Breakpoints at Function Module</b>
    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
    <b>To set a breakpoint for a function module</b>:
    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.
    <b>Breakpoints at System Exceptions</b>
    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.
    <b>Saving Breakpoints</b>
    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.
    <u>You can also delete breakpoints that you have saved</u>:
    •     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.
    <b>Managing Dynamic Breakpoints</b>
    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.
    <b>Watchpoints</b>
    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.
    <b>Setting Watchpoints</b>
    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
    <u>To set a watchpoint, start the Debugger and proceed as follows:</u>
    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.
    <b>Result</b>
    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.
    <b>Specifying Logical Links</b>
    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.
    <u>To create a logical link between watchpoints:</u>
    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 .
    <b>Deleting Watchpoints</b>
    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.
    <b>Memory Monitoring with Watchpoints</b>
    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.
    <b>Reward ifusefull</b>

  • How to change the value of a variable in new ABAP debugger.

    Hi Guys,
                 I can't change the value of a variable in the new ABAP debugger.. when I change its revert back to old value. but this is not the case with the old version. How to do this..
    Cheers
    Senthil

    Hi,
    1. Dobule click in the variable in the variable tab.
    2. Click the Change icon in Detail.Dis.
    3. enter the new value and press enter
    Refer
    [http://www.sapdb.info/new-abap-debugger/|http://www.sapdb.info/new-abap-debugger/]
    [http://help.sap.com/saphelp_nw70/helpdata/en/84/1f624f4505144199e3d570cf7a9225/content.htm|http://help.sap.com/saphelp_nw70/helpdata/en/84/1f624f4505144199e3d570cf7a9225/content.htm]
    <removed_by_moderator_together_with_points>
    Regards,
    SB
    Edited by: Julius Bussche on Jun 24, 2008 8:21 AM

  • ABAP Memory value in ABAP Debugger

    Hi,
    Is it possible to view the value of ABAP memory IDs in ABAP debugger?
    I know we can view the active ABAP memory IDs in debugger using Goto -> System Areas -> ABAP Memory
    Whereas my question is for those listed ABAP memory IDs, can we see the value in debugger itself?
    Thanks in advance.
    Regards,
    Balaji Viswanath.

    Hi,
    Did you sort out your problem yet? I am looking for the same. So far I know one can get the ABAP stack with the FM SYSTEM_CALLSTACK. This returns the stack but I still have not figured out how to access any stack objects yet.
    Let me know,
    Andreas

  • Timeout Issue in ABAP Debugger

    Hi All,
             Is there any way to increase the timeout for ABAP Debugger. Whenever  I have to cebug, and if i need to check other application at the same time, once I come back to debugger, it gets exited , due to TIMEOUT.
    Can you please help.
    Regards.,
    Muzammil.

    Hi,
    I think the execution of your program is taking a lot of time....check your logic of the program...avoid nested loops..try to increase the performance of your program....avoid nested queries...you can take help from the internet about " how to increase the program's performance"....your problem will be solved...this is not the BASIS issue...
    Arunima

Maybe you are looking for