ABDBG_ACTIVATION SAP (DO NOT CHANGE: ABAP Debugger Table of Waiting Debuggees) Table details
Description: DO NOT CHANGE: ABAP Debugger Table of Waiting Debuggees
Related tables to ABDBG_ACTIVATION
Access table ABDBG_ACTIVATION
Table field list including key, data, relationships and ABAP select examples
ABDBG_ACTIVATION is a standard SAP Table which is used to store DO NOT CHANGE: ABAP Debugger Table of Waiting Debuggees data and is available within R/3 SAP systems depending on the version and release level.
The ABDBG_ACTIVATION table consists of various fields, each holding specific information or linking keys about DO NOT CHANGE: ABAP Debugger Table of Waiting Debuggees data available in SAP. These include 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)), DEBUGGEE_USER (User Name).. 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: L - Table for storing temporary data, is delivered emptyDisplay/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP ABDBG_ACTIVATION table 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 |
| Key field | Non-key field |
How do I retrieve data from SAP table ABDBG_ACTIVATION using ABAP code
The following ABAP code Example will allow you to do a basic selection on ABDBG_ACTIVATION to SELECT all data from the tableDATA: WA_ABDBG_ACTIVATION TYPE ABDBG_ACTIVATION.
SELECT SINGLE *
FROM ABDBG_ACTIVATION
INTO CORRESPONDING FIELDS OF WA_ABDBG_ACTIVATION
WHERE...
How to access SAP table ABDBG_ACTIVATION
Within an ECC or HANA version of SAP you can also view further information about ABDBG_ACTIVATION 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