My break points are writing a entry to a log

can somebody explain why a break-point in my code in an update or start routine would casue an entry to the log when loading data?  I've had these before and should not be hit if running in back-ground.

Well, if you want to hardcode, just check for the username.
Put a if condition to check the username, and if its you, then you can have the break point. Well, am not very sure why its creating a log entry. But you can probably avoid this with the workaround i suggested.
regards
Sriram

Similar Messages

  • Break points are not triggering in RFC from portal application

    Helllo,
    I am running Biller Direct application from portal, which is triggering a standard SAP RFC FM back end, am trying to debug my execution from portal, for this i put the External Break point, Session break-poiint at the beginning of this SAP RFC FM, but, its not stoppping at ll, here the user is a Web user, not dialog user.
    How can i stop my execution in this SAP RFC FM to check how the structures are populated?
    Thank you

    Hi Raju,
    Please try the below way and check if it works.
    Open the RFC in R/3 i.e.
    SE37 -> give FM NAME -> DISPLAY.
    Click on UTILITIES -> SETTINGS -> CLICK THE TAB debugging.
    In the screen against the field users : give the value 'WEBLOGIN'.
    Uncheck the FLAG 'IP MATCHING'.
    And at the bottom check the check box against the field
    'Session Break Point Activate Immediately'.
    Save these settings.
    Then go to the line at which you want to debug the code and put an external break point over there.
    But, please take care of one thing as we are giving it as a WEBLOGIN, when ever some logs in, it will reach the brteak point and stop there. We have to click F8 to continue. Or else, the portal will be hanged for them.
    Thanks & regards,
    Y Gautham

  • Debugger Not Stopping at Break Points

    Howdy folks,
    I am trying to debug a rule in which I checkout / modify / checkin a renameUser view. I set some break points at the invoke statements for checking out and checking in. The rule is called from my Update User workflow. I know the rule is executing because I am dumping the context to a text xml file. The break points are right before and after the invoke that dumps the context to xml. However, when I update someone the debugger is not breaking in and stopping the thread to let me step through it. I would really like to see why my checkin and checkout invokes are not working, but can't see the error message due to the debugger not stopping...
    Does anyone have any advice, clues or ideas to get the debugger to work more correctly?

    It's probably running anonymously. That was my issue I think. The break points don't work on anonymous execution. At least not for me. Now, you can specify to use anonymous break points.. But then it breaks at EVERY anonymous break point. I had a hard time stepping through them all to get to what I needed to see execute, before it would time out... good Luck...

  • HI How  to set a Break point In Smart Forms

    Hi Guys,
    i want to set a break-point in main window of the smart form ,before dispalying
    values of the varibles in the main window .
    How to Set a break-point And What are the ways to set a break point.
    Thanks for All.
    From
    Hitu.

    Hi Hitu,
    Generally, Break Points are set for the purpose of debugging in Smartforms.
    For debugging , one of the way is :
    1. Write BREAK POINT in the code window.
    2. Put a break point on the call function in the driver program
    3. Put a break point in the generated Function module.
    Hope this resolves your query.
    <b>Reward all the helpful answers.</b>
    Regards

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

  • How many break points and watchpoints are allowed in ECC 6.0

    Hi,
    Can any one say how many break points and watchpoints are allowed in ECC 6.0

    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.
    There is 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 ie...Watchpoints allow you the option of monitoring the content of individual variables.The Debugger stops as soon as the value of the monitored variable changes.You can use max of 5 watchpoints.
    Difference
    1. Break Point.
    At particular LINE of SOURCE CODE,
    the system will STOP there.
    2. Watch Point.
    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.
    (For this, we have to give some
    VARIABLE NAME & VARIABLE VALUE - with relational operator)
    When this CONDITION gets satisfied,
    (anywhere during the execution of the program),
    the system will AUTOMATICALLY STOP THERE.
    (EG when the value of matnr reaches the specified value)
    That is the purpose of WATCHPOINT
    (the system will WATCH it, like a dog)
    Please go through this link:
    Watchpoint Vs breakpoint
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.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. Watchpoints allow you the option of monitoring the content of individual variables.
    The Debugger stops as soon as the value of the monitored variable changes.
    In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled.
    For more details...
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cd9e68c11d2b2ab080009b43351/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/f1/792442db42e22ce10000000a1550b0/frameset.htm
    If satisfied, rewards me..
    Kind Regards
    Yogesh

  • 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

  • Break-point at CRM_DATAEXCH_AFTER_BAPI_FILL

    We create BADi at CRM_DATAEXCHG_BADI:
    In IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
    and try to testing it.
    But then I set break-point - programm is not see it after save quotation.

    Hi,
        This BAdI is called after save by the MW outbound flow. Please follow the steps below :
    1. Deregister the CSA* queue in trx. SMQR (inbound queue)
    2. Edit the qoutation doc. and save it.
    3. Open the CSA* queue in
    SMQR
    . You will see a queue name like
    CSA_SALESDOCUMENT<document id>
    4. Open the queue entry, select it and press the 'Debug LUW' button. Note: make sure the rfc user id and your user id are dialog users.
    5. You will see the ABAP debugger.
    6. Now put a breakpoint by selecting Breakpoints->set breakpoint at...->method...
    7. Enter your BAdi impl. class name and method as
    IF_EX_CRM_DATAEXCHG_BADI~CRM_DATAEXCH_AFTER_BAPI_FILL
    8. You will see a 'breakpoint set' message.
    9. Press f8 and the flow should stop at this method.
    Rreward if helpful!
    Thanks,
    Sudipta.

  • Dual Layer Break Point problem

    Hi,
    I just found out after I updated DSP 4 to version 4.0.3 my Layer 1 on every project since updating gets corrupted!
    I thought it was the Dual Layer discs I used that caused the problem, but after I re-installed DVD Studio to the original version 4.0.0 the same project worked perfect.
    Anyone else have issues with Dual Layer Break Point after updating to 4.0.3?
    I have tried different chapters as layerbreak points on my project, and even a test project, with the same result. The finished discs is barely playable on some DVD players, showing wierd interference and noise, and DVD Player on mac crashes when reaching the dual layer break point, and the plant i send the master have a software to check DVDs and they said that it couldnt find/was corrupt Layer 1 on one of my discs. Hope someone can fix this, DSP is the best software otherwise!
    Best regards,
    Mats.

    DVD+R or DVD-R?
    http://documentation.apple.com/en/dvdstudiopro/usermanual/index.html#chapter=1%2 6section=9%26tasks=true
    DVD+R Double-Layer 
    You can use DVD+R double-layer media, often referred to as DVD+R DL, for burning your dual-layer projects. With DVD+R double-layer media, DVD Studio Pro places the layer break point and sets the switch point to be nonseamless as specified in your project.
    DVD+R double-layer discs require you to use the Opposite Track Path (OTP) direction setting when burning the disc. This means that the first layer must be larger than the second layer. See Setting the Dual-Layer Direction for more information.
    While DVD+R double-layer discs allow you to burn your dual-layer projects, they tend to have more compatibility issues than the other types of DVD media.
    DVD-R Dual-Layer 
    If your system contains a DVD drive that can write to the new DVD-R dual-layer media, you can burn your DVD project to it with DVD Studio Pro. However, there are several issues:
    Because currently DVD Studio Pro has no way to identify DVD-R dual-layer media as having two layers, burning a dual-layer project to it results in the appearance of an alert message telling you that the DVD media may have insufficient room to hold the project. This message is based on the assumption that the disc is single layer. Both layers of the disc will be written to as needed, however, when you click Continue.
    If you are burning a dual-layer project, the break point you set will not affect where the layer break actually occurs. Instead, the first layer is written to until filled, at which point the drive switches to writing to the second layer.
    The switch between layers is a seamless layer change not supported by some DVD players, which may stop playing the disc when the switch point is reached.
    Important: Do not use DVD-R dual-layer media unless these issues do not impact your project.

  • User-specific break-point

    Hi
      while debugging whether it is possible to have a <b>user-specific breakpoint???</b> if so gimme idea how to make it???
    Thanks in advance

    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.
    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.
    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.
    http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
    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
    Chaeck the following documents,
    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
    Hope you can get all the required information from the above documents.
    Reward points if helpful.

  • DVD Studio Pro Dual Layer Break Point Problem

    I have a problem with a disc that I am burning. It is a dual layer (the break point is not set to seamless) with 1 movie that is about 3.6 GB and 1hr 23 min long, a 30 min slideshow, another 30 min extra and five other extras that total to about 20 min. I put the dual layer break point at the beginning of the slideshow, everything played fine on the computer, but on the Panasonic DVD player it just freezes at 35 seconds into the slideshow. Its never had a problem with DLs before. Itried the DVD on my softmodded Wii, on a program for it called WiiMC (it uses Mplayer) and everything played fine. I tried another burn where i set the break point to fifteen minutes before the end on the main 1:23 movie and on the DVD player it still froze at 35 seconds on the slideshow. Is there anything that you guys can suggest to help?

    DVD+R or DVD-R?
    http://documentation.apple.com/en/dvdstudiopro/usermanual/index.html#chapter=1%2 6section=9%26tasks=true
    DVD+R Double-Layer 
    You can use DVD+R double-layer media, often referred to as DVD+R DL, for burning your dual-layer projects. With DVD+R double-layer media, DVD Studio Pro places the layer break point and sets the switch point to be nonseamless as specified in your project.
    DVD+R double-layer discs require you to use the Opposite Track Path (OTP) direction setting when burning the disc. This means that the first layer must be larger than the second layer. See Setting the Dual-Layer Direction for more information.
    While DVD+R double-layer discs allow you to burn your dual-layer projects, they tend to have more compatibility issues than the other types of DVD media.
    DVD-R Dual-Layer 
    If your system contains a DVD drive that can write to the new DVD-R dual-layer media, you can burn your DVD project to it with DVD Studio Pro. However, there are several issues:
    Because currently DVD Studio Pro has no way to identify DVD-R dual-layer media as having two layers, burning a dual-layer project to it results in the appearance of an alert message telling you that the DVD media may have insufficient room to hold the project. This message is based on the assumption that the disc is single layer. Both layers of the disc will be written to as needed, however, when you click Continue.
    If you are burning a dual-layer project, the break point you set will not affect where the layer break actually occurs. Instead, the first layer is written to until filled, at which point the drive switches to writing to the second layer.
    The switch between layers is a seamless layer change not supported by some DVD players, which may stop playing the disc when the switch point is reached.
    Important: Do not use DVD-R dual-layer media unless these issues do not impact your project.

  • Break points

    hai gurus...
    how many watch points and break point can be used in each program...
    types of watch points and break points....
    Thanks
    Pavan

    Hi
    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 under which a watchpoint is to become active.
    · You can specify a logical link for up to five (conditional) watchpoints.
    See also Specifying Logical Links.
    · 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
    Breakpoints
    Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing 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 Debugger is activated when the program reaches this point.
    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 more information, refer to the chapter Watchpoints.
    Breakpoint Variants
    The Debugger contains different breakpoint variants:
    Static
    A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
    Directly set
    dynamic breakpoints
    Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
    Breakpoints
    at statements
    The Debugger stops the program immediately before the specified statement is executed.
    Breakpoints
    at subroutines
    The Debugger stops the program immediately before the specified subroutine is called.
    Breakpoints at function modules
    The Debugger stops the program immediately before the specified function module is called.
    Breakpoints at methods
    The Debugger stops the program immediately before the specified method is called.
    Breakpoints at exceptions and system exceptions
    The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
    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.
    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 remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, 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.
    we can keep them at :
    Statements
    Subroutines
    Function Module Calls
    at Methods
    System Exceptions
    break point :
    we can start debugging from that point or if we keep break point at some place we can directly got ot htat point using f6.
    watch point: for example if we have to check the output for 4000 records based on a field value i.e.for vendor number 'in'we have to check then we will create watchpoint on field LIFNR value '2000'. then we can directly go to vendor whose numbe ris 2000
    Regards,
    Sree

  • 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

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

  • External break point in sap r/3 system

    i want to set external debugging to rfc in r/3
    i tried to set it
    its getting set
    but when i call rfc from external system(webdynpro)
    its not gng to that break point i.e its not linking to that break point
    what could be the reason
    and how we can set external breakpoint
    are there any setting we need to do in r/3 so that break points will work
    Regards,
    Vani

    Hi Vani,
    First u have set ur Server to Debug mode...then only u can debug the code...
    1. Select "Server0" from J2EE engine (To get this view navigate thru Window--> Show View --> J2EE Engine)
    2. Make a right click on "Server0" and choose "Enabling Debugging of Process"
    3. Now, Navigate to Run --> Debug --> Select your Project as "Webdynpro Application" and click "new" button
    4. Now give some name and Click BROWSE to select ur project and then click APPLY and DEBUG
    Or
    if u use 2004s, then u can do the settings in Portal itself...which gives u more clear information... follow the link
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0cb32c5-36a7-2910-2c9b-ba4a5bbdbb56">WebDynpro Java Debug Configurator</a>
    Hope it helps...
    Regards / Guru

Maybe you are looking for