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_TERM_ID_NAME |
| Short Description | Name of Terminal ID |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR32 | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| 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 | Term Name |
| Medium | 15 | Terminal Name |
| Long | 20 | Teminal ID Name |
| Heading | 32 | Teminal ID Name |
Documentation
Definition
The terminal ID represents the logon of the Windows user to the Windows operating system. It should identify all actions that are executed from this Wndows logon session.
You can only work with the terminal ID if you use the SAP GUI for Windows.
Setting the Breakpoint
If there is not yet an assignment to a Wndows logon, a terminal ID is implicitly assigned (Windows Registry) to this WIndows logon when a breakpoint is set. The assigned terminal ID appears to the right beside the radio button "Terminal ID" in the ABAP Workbench dialog box described here. If an external breakpoint is set, this will then only activate the Debugger when the started request also has this terminal ID.
Starting the Request
If you wish to start a request for which you have previously set a breakpoint with the terminal ID, you must now link this request with the same terminal ID so that the Debugger can be activated.
If you are in the same Windows logon, proceed as follows:
- SAP GUI: In the window of the SAP GUI that initiates the request, enter "/htid" in the OK Code field. Now all the requests initiated from this SAP GUI window (more precisely, from this external session) are linked with the terminal ID that was set for the current Windows logon. Here, the request can be processed in several systems without the information of the terminal ID getting lost. All the involved systems must have at least Release NetWeaver 7.1 EhP1.
- Microsoft Internet Explorer: Use the "SAP HTTP Plug-In for the Microsoft Internet Explorer". You will find information on this in Note 1041556. If you start the Internet Explorer using the "SAP HTTP Plug-In for the Microsoft Internet Explorer", all outbound requests will automatically be associated with the terminal ID of the Windows logon. However, you must have the function "Start Transaction" activated in the plug-in (see documentation of the "SAP HTTP Plug-In for the Microsoft Internet Explorer").
If you wish to start the request from a different Windows logon, proceed as follows:
SAP GUI: In the SAP GUI window that initiates the request, enter "/hset tid=<tid>" in the OK Code field. Here, <tid> is the terminal ID that - as described above - appears in the ABAP Workbench of the Windows logon where the breakpoint was set. From now on, all requests intiated from your SAP GUI window (more precisely, from this external session) will be associated with this terminal ID. A request can also be processed in several systems without information of the terminal ID getting lost. However, all the systems involved must have at least Release NetWeaver 7.1 EhP1.
Microsoft Internet Explorer: Use the "SAP HTTP Plug-In for the Microsoft Internet Explorer". For information on this, refer to note 1041556. If you start the Internet Explorer with the help of the "SAP HTTP Plug-In for the Microsoft Internet Explorer", then you should enter - in the field "Terminal ID" of the plug-in - the terminiatl ID that, as described above, appears in the ABAP Workbench of the Windows logon in which the breakpoint was set. Afterwards, all oubound requests of the browser are associated with this terminal ID. A request can be processed in several systems without the information on the terminal ID getting lost. All the systems involved must have at least Release NetWeaver 7.1 EhP1.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in |
