Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-ABA (Application Component) ABAP Editor⤷
SEDI (Package) PROGRAM EDITOR
Basic Data
| Data Element | SEU_DEBUG_SBRP |
| Short Description | Flag Debugger Session Breakpoint Active Immediately |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Sess.Break |
| Medium | 15 | Sess.Breakpoint |
| Long | 20 | Session Breakpoint |
| Heading | 30 | Session Breakpoint Active |
Documentation
Definition
If a session breakpoint is set in an external mode (SAP GUI window of a logon), this will become active in parallel external modes only when a new internal mode (roll area) is started there. This means, for example, that current transactions or programs will usually not be synchronized with the newly set session breakpoints until they are exited.
The setting "Session Breakpoints Active Immediately" immediately synchronizes transactions and programs that are already running with the newly set session breakpoints. In doing so you can, for example, interrupt a long-running program and force it into the debugger by setting a session breakpoint at the right position in a parallel external session of the same logon.
If a session runs under control of the new ABAP debugger (e.g. after F8) , then this setting is not relevant. Session breakpoints that have been set in parallel sessions are always synchronized immediately.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20050219 |
| SAP Release Created in | 700 |
