Breakpoints and Breakpoint Statements

Breakpoints interrupt the program execution and transfer the control to the ABAP Debugger. Breakpoint Types There are the following types of breakpoints that were conceived for different a pplication uses: If you set a breakpoint in the ABAP Editor (SE38), then it is a session brea kpoint or an external breakpoint . You can also set a breakpoint statement in th e source text of the program. You can initiate a debugging session in this way (the execution of an applic ation is first interrupted and then the ABAP Debugger starts). If you set a breakpoint in the window of the ABAP Debuggers, then this is a debugger breakpoint . Debugger breakpoints can be set in addition in a debugging session that alre ady exists. The following restrictions apply: Up to 30 session breakpoints, external breakpoints, and debugger breakpoints can be set. A breakpoint is either active or inactive. Only active breakpoints take effect. Inactive breakpoints are ignored at run time. With the ABAP Debugger tools you can manage external, session, and debugger breakpoints. For more information, see Managing Breakpoints in the ABAP Debugger . Breakpoint statement are ignored. The main features of the individual breakpoint types are explained below. Session breakpoints With session breakpoints you can stop and debug requests that you trigger in the same user session where you have set the session breakpoints. They are therefor e particularly useful for debugging SAP GUI-based applications. You set a session breakpoint in the ABAP Editor (SE38) as a line breakpoint, tha t is, for a particular row of the source text. For more information, see Managin g Breakpoints in the ABAP Editor. In addition to this, other breakpoint types ca n be coverted to session breakpoints during a debugging session. For more inform ation, see Managing Breakpoints in the ABAP Debugger. A session breakpoint is valid within all main modes (external modes) of the user session where it was set. If you end the user session (by logging off the system), then all of the session breakpoints set in this session are deleted. Note Note Session breakpoints are therefore no longer available for implicit new logons, f

or example when switching the server using transaction SM51. However, you can first save session breakpoints that are valid in the current us er session in the database and reload them in another user session. See: Managin g Debugger Sessions External breakpoints External breakpoints (previously known as: User breakpoints) apply to the curren t user session in the same way as session breakpoints. In addition to this, they remain valid for future user sessions. This does not only mean dialog sessions, but also sessions initiated with RFC or HTTP requests. You can debug applications with external breakpoints, that use the RFC interface or HTTP protocol (External Debugging). Functions modules, Web services and Web Dynpro applications, and BSP applications also belong to this. An external breakpoint can apply to: A user in the current SAP system A user in the current application server of the current SAP system User sessions started by a request that has a specific terminal ID. You can set external breakpoints: In the ABAP Editor (SE38) as line breakpoints, that is, for a specific line of the source text. For more information, see Managing Breakpoints in the ABAP E ditor. in transaction SICF. Other breakpoint types can be coverted to session breakpoints during a debug ging session. For more information, see Managing Breakpoints in the ABAP Debugge r. External breakpoints are active for two hours. They are then deactivated. If an external breakpoints is set then all external breakpoints that had previously be en set are reactivated. External breakpoints apply on the calendar day that they are set. They are delet ed in the first minute of the next calendar day (at midnight). See also: External Debugging (HTTP and RFC Debugging) Debugger breakpoints Debugger breakpoints are breakpoints that you set in the window of the ABAP Debu gger. There are the following kinds of debugger breakpoints: Line breakpoints that you set in specific lines of the source test are the s ame as setting breakpoints in the ABAP Editor. Line breakpoints that you define for specific situations and which the syste m implicitly sets, for the relevant row in the source text: Breakpoints at subroutines Breakpoints at function modules

Breakpoints at methods Breakpoints at source code Breakpoint at ST template Breakpoints at Web Dynpro Dynamic breakpoints that you define for specific situations which are not as signed to a specific row in the source text. This includes: Breakpoints at statements Breakpoints at exceptions Other: Breakpoints at stack changes (program/procedure switch ABAP + Dynpro stack) Breakpoints at imprecise DECFLOAT calculations Breakpoints at messages You set debugger breakpoints in the ABAP Debugger window during a debugging sess ion that already exists. For more information, see Managing Breakpoints in the A BAP Debugger. A debugger breakpoint applies to the whole current debugging sessions (all inter nal and main modes). When the Debugger is closed, all debugger breakpoints are deleted. You can ovoid this by converting them first to session breakpoints or external breakpoints. F or more information, see Managing Breakpoints in the ABAP Debugger. Breakpoint Statements Breakpoint statements are ABAP statements that represent breakpoints contained i n the source text of the program. A breakpoint of this type can be active at runtime: For all users For a specific user If a specific cheakpoint group is active. You can only add or delete breakpoint statements in the development phase by mod ifying the source text of the program. For more information, see Breakpoint Stat ements. The ABAP Debugger tools do not manage them. Note Note Session breakpoints, external breakpoints, and debugger breakpoints are more fle xible than breakpoint statements: They can be created at runtime and managed wit h the tools of the ABAP Debugger (for example, activated and deactivated). The s ource text of the program must not be modified as well. change in the

Related Content The following content is not part of SAP product documentation. For more informa tion, see the following disclaimer Information published on SAP site . SAP Community Network (SCN) ABAP Development Java Development Business Process Management and Composition Business Rules Management Process Integration (PI) & SOA Middelware B2B Integration SAP NetWeaver Portal User Interface Technology SAP NetWeaver Business Warehouse Web Dynpro ABAP Web Dynpro Java Composite Applications Security SAP NetWeaver Application Server SAP NetWeaver Administrator Enterprise Services Repository (ESR) Product Availability Product Availability Matrix Support Information Search in SAP Notes Share this: