SAP ABAP Data Element TID_MODE (Terminal ID and External Session Number)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CST (Application Component) Client/Server Technology
⤷ STSK (Package) Task Handler, Number Range, Update, Gateway and so on
⤷ BC-CST (Application Component) Client/Server Technology
⤷ STSK (Package) Task Handler, Number Range, Update, Gateway and so on
Basic Data
Data Element | TID_MODE |
Short Description | Terminal ID and External Session Number |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 12 | |
Decimal Places | 0 | |
Output Length | 12 | |
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 | TID/Sess. |
Medium | 20 | Terminal ID Session |
Long | 30 | TID from SM04 & Session Number |
Heading | 55 | Terminal ID from SM04 and External Session Number |
Documentation
Definition
The terminal ID is the number of the terminal in the list of all the clients logged on to the dispatcher. The session number corresponds to the current external session.
Use
This information is used to determine RFC dependencies in the analysis of RFC connections.
The combination TID/session determines the context belonging to a conversation ID either as a client or as a server. The TID/session combination enables you to determine which RFCs are still coming from this context (client).
The TID/session information on the server side is used to check this also appears again as a client, and hence is part of an RFC chain that is accessible iteratively.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 732 |