Hierarchy
⤷ BC-DWB-TOO-ABA (Application Component) ABAP Editor
⤷ SEDI (Package) PROGRAM EDITOR
Basic Data
Data Element | SEU_TERM_ID |
Short Description | Flag Terminal ID |
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 | TerminalID |
Medium | 15 | Terminal ID |
Long | 20 | Terminal ID |
Heading | 11 | Terminal ID |
Documentation
Definition
General Information on the Debugger of Internal Requests
With "external requests" you mean requests that are not triggered in the same logon in which the breakpoints are set. For example, for HTTP or RFC requests, the breakpoints cannot be set before the request in the same application since the request itself possibly creates the logon. So that these requests can nonetheless be analyzed using the Debugger, so-called "external breakpoints" - also referred to as "User Breakpoints" - are used.
Take note of the following information so that the Debugger can be started when you are using external breakpoints:
(1) If an external breakpoint is reached, a new external session is started with the Debugger in the dialog logon in which the breakbpoint was set. If an external request is to be caught using the Debugger, this logon must be retained and must not be closed.
(2) Both the user who performs 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 the authorization for the Debugger function.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20100420 |
SAP Release Created in |