Hierarchy
⤷ BC-DWB-TOO-ABA (Application Component) ABAP Editor
⤷ SEDI (Package) PROGRAM EDITOR
Basic Data
Data Element | SEU_USER_RAD |
Short Description | Flag User |
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 | User |
Medium | 15 | User |
Long | 20 | User |
Heading | 4 | User |
Documentation
Definition
General Information on Debugging External Requests
With "external requests" you mean requests that are not triggered in the same logon where the breakpoints are set. For example, for HTTP or RFC requests, the requests cannot be set before the request in the same logon since the request might possibly only be created through the logon itself. So that these requests can still be analyzed by the Debugger, so-called "external breakpoints" - also called "User Breakpoints" - are used.
Take note of the following information so that the Debugger can be started when using external breakpoints:
(1) If an external breakpoint is reached, a new external session was started with the Debugger in the same dialog logon in which the breakpoint was set. If an external reqest is to be caught using the Debugger, this logon must therefore be retained and must not be closed.
(2) Both the user who is performing the analysis with the help of the Debugger as well as the user whose request is analyzed with the help of the Debugger must have appropriate debugging authorization.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20100420 |
SAP Release Created in |