STPDA_DEBUGGEE SAP (Debuggee attributes) Structure details
Description: Debuggee attributes
Related tables to STPDA_DEBUGGEE
Access table STPDA_DEBUGGEE
Structure field list including key, data, relationships and ABAP select examples
STPDA_DEBUGGEE is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Debuggee attributes" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_STPDA_DEBUGGEE TYPE STPDA_DEBUGGEE.
The STPDA_DEBUGGEE table consists of various fields, each holding specific information or linking keys about Debuggee attributes data available in SAP. These include CLIENT (Client ID), DEBUGGEE_ID (16 Byte UUID in 32 Characters (Hexadecimal Encoded)), TERMINAL_ID (16 Byte UUID in 32 Characters (Hexadecimal Encoded)), IDE_ID (16 Byte UUID in 32 Characters (Hexadecimal Encoded)).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP STPDA_DEBUGGEE structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| CLIENT | Client ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| DEBUGGEE_ID | 16 Byte UUID in 32 Characters (Hexadecimal Encoded) | SYSUUID_C32 | CHAR | 32 | SYSUUID_C32 | ||||
| TERMINAL_ID | 16 Byte UUID in 32 Characters (Hexadecimal Encoded) | SYSUUID_C32 | CHAR | 32 | SYSUUID_C32 | ||||
| IDE_ID | 16 Byte UUID in 32 Characters (Hexadecimal Encoded) | SYSUUID_C32 | CHAR | 32 | SYSUUID_C32 | ||||
| DEBUGGEE_USER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
| PRG_CURR | Displayed program (overwriting is possible) | DBGSREPID | CHAR | 40 | PROGRAM_ID | ||||
| INCL_CURR | Displayed program (overwriting is possible) | DBGSREPID | CHAR | 40 | PROGRAM_ID | ||||
| LINE_CURR | Line number | DBGLINNO | INT4 | 10 | |||||
| RFCDEST | Logical Destination (Specified in Function Call) | RFCDEST | CHAR | 32 | Assigned to domain | RFCDEST | RFC | F4_RFCDESTYPEALL | |
| APPLSERVER | Application Server | SYHOST | CHAR | 32 | HOST_ID | ||||
| SYSID | Name of SAP System | SYSYSID | CHAR | 8 | SYCHAR08 | ||||
| SYSNR | Number of Application Server Instance | 0 | |||||||
| DBGKEY | ID of Waiting Debuggee | 0 | |||||||
| TSTMP | UTC Time Stamp in Kernel Format: 'time_t' | 0 | |||||||
| DBGEE_KIND | Type of Waiting Debuggee | 0 | |||||||
| DUMPID | Name of ABAP Runtime Error | S380ERRID | CHAR | 30 | SYCHAR30 | ||||
| DUMPDATE | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| DUMPTIME | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
| DUMPHOST | Name of Current Application Server | SNAP_SYINST | CHAR | 32 | SNAP_INST_ID | ||||
| DUMPMODNO | Index of Work Process | SYWPID | INT4 | 10 | SYST_LONG | ||||
| APPSERVER | appserver name for target rfc destination for runni debuggee | 0 | |||||||
| DUMP_ID | 0 | ||||||||
| DUMP_DATE | 0 | ||||||||
| DUMP_TIME | 0 | ||||||||
| DUMP_HOST | Application Server Name | MSNAME2 | CHAR | 40 | MSNAME2 | ||||
| DUMP_UNAME | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
| DUMP_MODNO | 0 | ||||||||
| DUMP_CLIENT | 0 | ||||||||
| DUMP_URI | 0 | ||||||||
| URI | URI - mandatory client response, optional for client request | 0 | |||||||
| TYPE | Type (workbench type) of the referenced entity - optional | 0 | |||||||
| NAME | Name of the referenced entity - optional | 0 | |||||||
| PARENT_URI | URI of parent reference - optional | 0 | |||||||
| PACKAGE_NAME | Package name of the referenced entity- optional | 0 | |||||||
| DESCRIPTION | Description of the referenced entity - optional | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure STPDA_DEBUGGEE using ABAP code?
As STPDA_DEBUGGEE is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on STPDA_DEBUGGEE as there is no data to select.How to access SAP table STPDA_DEBUGGEE
Within an ECC or HANA version of SAP you can also view further information about STPDA_DEBUGGEE and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects