Break point in a program

i kept a break point in a user exit with the statement
BREAK-POINT.
but the control is not stopping there , i am not testing it so didnt give it as user specific . what might be the mistake ? is it not the proper user exit , i have created a project and activated it . i have activated include and all .

Hi,
When you start transation in which you have put a break point, start debugging on(\h). add break-point at statement CALL CUSTOMER-FUNCTION.
keep on pressing F7. You may reach to your exit if it come in way of executing you process.
Could you mention for which functionality you have created using user exit, it will more easy to provde help.
Regards,
Amit R.

Similar Messages

  • Break point through the program

    i am using the statement break <sy-uname> to set the breakpoint. But the control is not stopping at that point. how do i do that.

    Hi,
    Is the break-point given in an update task module..Then I believe it will not stop..
    Also you have to give in single quotes..
    Example..
    BREAK 'USER1'.
    Thanks,
    Naren

  • Dump while setting a break point in ECC 6.0

    Dear Experts,
    In ECC 6.0, when I try to put a break point in the program to stop the control there. I am not able to do so, it is going to dump. The dump message is also not very clear. Do anyone of you are facing the same problem. Any idea why is this happening and how do I fix it.
    Can it be due to the improper installation? Please respond.

    First of all thanks to Mickey, Nitin, Anki, Sujit, Red, Madhu, Vibin for the quick response...To be honest I did not expect such a response as a new member to the SDN community...I am sorry I could not mention the detail about the dump initially...Here is the detailed description..
    Issue: In ECC 6.0, when I write a simple ABAP program (e.g. 'Hello World' program). When I try to keep the cursor on any abap statement and click on the 'session break point' icon in the tool bar to set the break point, i get a status message 'Compling SAPLBREA in separate task and finally i get the dump.
    Dump Detail :
    Runtime Errors: DBIF_REPO_SQL_ERROR
    Short Text : SQL error 1115 occurred when accessing program 'LNAVIDAT' part "SRC".
    Program: SAPLBREA
    Include: LBREATOP
    Row: 41
    There is a an include being called at line no 41, which is "Include LNAVIDAT".
    Now when I click on the 'debugger' icon in the dump...It points to a functional module "RS_SET_BREAKPOINT"
    Also, while double clicking on this include to see the code within, it issues an error message saying "SQL error occurred when accessing the table TRDIR".
                                    Or
    While trying to display the code of the include LNAVIDAT in se38 to see what is wrong with that i get another dump and this time it points to be SELECT query in the dump which is:
    SELECT SINGLE * from PROGDIR WHERE name = rs38m-programm
                                                              and  state = active.
    Thereafter, i keep getting dumps when i try to go to any T.codes (e.g. se11, se38 etc.). until i log off and log in again. Hope this helps you guys understanding the problem. Being new to SAP, I have no clue why is this happening and how to fix it. Thanks in Advance.

  • DL Break Point Issue - Please Help.

    Hello,
    I use to work in DVDSP when you could only do one layer and even then I knew just enough to get the job done. Now I have a program that is 6.6 gigs total size (according to DVDSP) and I can't get this thing to find the break point. I have read through most of the manual regarding this issue and have read many posts - first I have to ask is why is this so difficult?
    Here are the issues in detail and I ask that if you give input please guide me like I have limited knowledge in this.
    I am using DVDSP 4.1.0 on a G5 Dual 1.8 OS is 10.4.8 with a Pioneer DVR 111D. I have 4 'tracks' all coming off one main menu...no sub menu's - so I have the one main and four buttons that go directly to the videos. When I try to 'burn' the DVD I get this error 'Formatting was not successful. A suitable marker could not be found in the required layer break range. See the DVD Studio Pro User's Manual for more information.' The size of each track is as follows:
    Track One: The Main footage is 4.0 Gig (this is the one I am trying to set the break point because the limit is 3.9 Gig)
    Track Two: is 1.7 Gig
    Track Three: 606 Meg
    Track Four: 216 Meg
    I have tried 'Automatic' without luck.
    I have tried to place a few markers approximately 3/4 of the way through Track One the marker that I place is Green and in the Inspector window when I click on that marker I see the 'Marker Function' and then the button to select Dual-Layer Break Point and I select that only. However when I click something else and then come back to Marker the Dual Layer Break Point is not selected!
    I then have gone into the 'Disc/Volume' and tried to select the 'Break Point' and chose Track One but still nothing. I have read in the forums about building the disc and then going into the TS folders and blah blah blah to get this done but that is above my head and I don't understand it.
    I just need to get this video done. It is for a family who's 17 daughter was tragically killed and will be a fund raiser for them...I need to get this done. So if any of you are willing to help that would be SO appreciated AND if any of you would be so kind to walk me through this over the phone THAT WOULD BE GREAT! Just email me at [email protected] and I will email you my number. I know this is a tad different but I don't have much time left to get this done because of my 'real job' and again, I need to get this done!

    Hi csiaudio,
    Build the project (AltAppleC). Then in the format window (Apple+F), Disc/Volume tab you'll be able to see the available break point markers. If they are all greyed out then you do not have one in the project.
    Add Cell markers in places that you think would be ok as the layer switch. You do this by adding a chapter marker and then in the property inspector un-checking the type Chapter. This will now be a marker that can be used as a dual layer break point but is not a chapter marker.
    You'll need to re-build the project and check the format window options again,
    -Jake

  • How to put a break point while creating a travel request in ess

    Hi to all experts,
    My requirement is to put a break point in the badi while creating a travel request in Ess.
    The badi name is TRIP_WEB_CHECK
    i tried both external and session bps
    i also tried this.
    break uname
    break-point
    and it is i check whether is triggering by throwing dump like ( divide by zero) it is triggering
    how to stop it while triggering

    Hi Bhanu,
    Please go through these links:
    How to debug abap code in update rules...routine?
    debug abap routine in infopackage
    Debugging of global transfer and update routine
    Debugging Start/Transfer routine
    And have a look at this demo video to know how to set up break points and how to debug an ABAP program in NW2004s:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0?prtmode=navigate
    Hope it helps..
    Cheers,
    Habeeb

  • Export  data in Excel file - Debug and Break Point

    In the program RFUMSV00 the data  been displayed on the screen with the function REUSE_ALV_LIST_DISPLAY.
    With "Cntrl + Shift + F9" I exported the list of data in an Excel file.
    How can I see, with Debug, where the program RFUMSV00 passed the data to Excel File? I can indicate the point, In the program, where I need to set the break point?
    Thanks,
    Serena

    Hi,
    This download functionality has nothing to have with program RFUMSV00. It is actually processed by REUSE_ALV_LIST_DISPLAY fm, which calls fm LIST_COMMAND which finally calls fm LIST_DOWNLOAD, where you will actually find the downloading part (in fact in another fm, DOWNLOAD_LIST)...
    to resume: REUSE_ALV_LIST_DISPLAY->LIST_COMMAND->LIST_DOWNLOAD->DOWNLOAD_LIST
    so I would put the break-point in the last one..
    Kr,
    Manu.
    correction: I made a mistake, the break-point should be set in LIST_DOWNLOAD...where you will find the call to fm LIST_CONVERT_TO_DAT which is responsible of the download...
    Edited by: Manu D'Haeyer on Dec 9, 2011 1:46 PM

  • Reg usage of break point in debug mode

    Dear experts,
       I want to know how to go to a particular line in debugging mode. Suppose for example, if a program contains main program and includes.  I want to go to a particular line in debugging mode in the includes. How can i go? kindly help me.
    tks

    Hi Prabhakar,
    Using break points you can stop the execution control at that break point.
    If you use only F5, F6, F7 for debugging you don't need of break points.
    But if you want to stop at particular statement while running the report (using F8) you should use Break Point. Ofcourse you can use watchpoints also.
    Watchpoint --- If you put watch point execution control stops at the particular statement when the value of watchpoint is reached.
    Reward If Helpful.
    Regards
    Sasidhar Reddy Matli.

  • Break point in smart form

    Dear Gurus....
    I am new to smartforms. I have a report which is to be integrated with smart form. I want each PO should start from a new page. I have tried putting an alternative and command in main window but it doesnot solve my problem. Please help me out as i need the solution very urgently...
    please mail me the solution here or to my mail id [email protected]
    Thanks in advance.

    Hi Ajay,
    If your question is regarding break point, then create a program line node before the alternative condition and code "break-point". Next time when you execute the program it will stop at this point.
    Please let me know what are you displaying in the form. I understand that you want to have a page break for each PO. Are using Table node?
    Thanks
    Vinod

  • Break point in EXIT_SAPLV05I_002

    Hi, I nead your help.
    I've already put a break point in EXIT_SAPLV05I_002, INCLUDE ZXV05U05 but when I crete a delivery the debuging is not started.
    Dou you know in what moment this exit should stop?
    Thanks
    Dora

    Hi Venkat
    Your user exit does get processed during the delivery save.
    Your breakpoints are not stopping in it because all the indexes tables VKDFS, VEPVG etc
    are handled in the update task, so you have to use update debugging.
    The quick wat to get to your user exit to see what is is doing is as follows:
    Create a delivery in VL01n
    Before you hit the save button switch on the debugger
    then press save
    In the debugger oput a breakkpoint on the ABAP statement COMMIT WORK
    The program will stop at this statement which is the end of the application processing.
    In the debugger go to SETTINGS > UPDATE DEBUGGING
    Then press F8 to contunue
    A new screen will appear with the update task.
    In the new screen put a breakpoint in function module RV_DELIVERY_INDEX_SAVE
    ( If this were from a sales order you would do the same but with function RV_SALES_DOCUMENT_INDEX_ADD)
    Your user exit is called below marked :
    RV_DELIVERY_INDEX_SAVE
      Billing type appears in the index if there is at least one R/3
      billing relevant item in the delivery
         if vbuk_wa-fkstk ca 'AB' or
            vbuk_wa-fkivk ca 'AB'.
    perform lk_01.                   "Fakturaauslöser           >>>>>>>
        EXIT_SAPLV05I_002 is called in here.... 
    I hope this helps explain the system behaviour
    Kind regards
    Brian

  • Can any  one explain me about break point

    Hi gurus
    What is break point what is the use of it? please let me know what is the use of it?
    Thanks in advance

    Hi
    Hi,
    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 Debugger is activated when the program reaches this point.Max 30 breakpoints we can use.
    Session Breakpoints exist only until you are logged in or until ur session is active. Even if u forget to remove the session break points, they are automatically removed once ur session becomes invalid or u logged out.
    Debugger
    This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
    Functional Overview
    Use
    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 specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant 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.
    Direct Processing
    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 a useful procedure if you are not overly familiar with the program 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 choose Program ® Test ® Debugging.
    From the ABAP Editor
    Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
    From any screen
    Choose System ® Utilities ® Debug ABAP.
    From any screen
    Enter /h in the command field.
    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 ® 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
    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 ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
    Displaying Program Attributes
    You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
    Restarting the Debugger
    If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
    Breakpoints
    Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these 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.
    Breakpoints
    at statement
    The Debugger stops the program directly before the specified statement is executed.
    Breakpoints
    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.
    Static Breakpoints
    Static breakpoints are not normally user-specific. 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 the program execution is always to be interrupted at the same place. For further information, refer to 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 further information, refer to 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.
    Lifetime and Transfer of Breakpoints
    A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
    If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
    If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
    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 ® Breakpoint at ® Statement...
    The following dialog box appears:
    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:
    Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
    The following dialog box then appears:
    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.
    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:
    Choose Breakpoint ® Breakpoint at ® Function module...
    The following dialog box appears:
    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.
    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 Methods
    You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
    Prerequisites
    You must be already running the program in the debugger.
    Procedure
    To set a breakpoint for methods:
    1. Choose Breakpoint ® Breakpoint at ® Method...
    The following dialog box then appears:
    2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
    3. Choose ENTER.
    Result
    The system confirms the breakpoint. The breakpoint is added to the list in the display.
    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 ® Breakpoint at ® 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.
    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 ® 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:
    Position the cursor on the line of the source code at which you want to set the breakpoint.
    Choose Utilities ® Breakpoints ® 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 ® Breakpoints ® 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:
    Position the cursor on the line in which you want to set the breakpoint.
    Select the line by double-clicking it or choosing Breakpoint ® 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.
    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 ® 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 ® 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 ® Control debugging ® Breakpoints.
    Example
    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 ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
    Activating and Deactivating Breakpoints
    Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
    Regards
    karthik

  • Where to put break point when debugging the inbound IDOC processing

    Hi, Dear Experts,
    If IDOC has error and want to debug, which program or function module  to put break point when debugging the inbound IDOC processing
    Thank you so much!
    Helen

    It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
    If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

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

  • Break Point in BTE function module

    i have function modules being triggered from 00002010
    00002020 BTEs for tcode F110.How do i set break point in them .i mean is it posible 'coz i guess a session is being created every time i run f110.
    Please help.
    Thanks and Regards,
    Venkat

    1. Set a break point in your function module.
    2. F110 Schedule a payment run (Specify a start time - Do not check Start immediately)
    3. SM37 - Select your job and enter '=JDBG'  in the command field
    4. Continue and and the program will stop at you break point
    Reward points if helpful

  • Break point in sapscript

    hi all,
    how can i stop with break point in sapscript.
    i know the way: utilities, activate debugger and a lot of f5 or f8 until i came to the place i need to stop. this is a very slaw way. it's something more quickly ?
    thanks,
    dany

    Hi Dany
    What you already know is again going to serve your purpose again but with some additional knowledge.
    Just see the 'ELEMENT' in the SapScript code in which relevent information is there where you would like to stop. Say, you would like to stop at ELEMENT 'LINES'...
    When you run your program with Sapscript debugger activated, when it goes to debugger on script very first time, you get a POP-UP window which you might be always ignoring by simple pressing button for 'Continue' but that is really useful!
    You can exploit the options there for your advantage.
    Example: there is a field there for 'ELEMENT', you can simply put your element name and see the magic. there are other options also like 'WINDOW', etc. to filter what you want to debug.
    Cheers
    Ashish

Maybe you are looking for