TPDA_SESSIONS_BPS SAP () Structure details
Description:
Related tables to TPDA_SESSIONS_BPS
Access table TPDA_SESSIONS_BPS
Structure field list including key, data, relationships and ABAP select examples
TPDA_SESSIONS_BPS 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 "" 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_TPDA_SESSIONS_BPS TYPE TPDA_SESSIONS_BPS.
The TPDA_SESSIONS_BPS table consists of various fields, each holding specific information or linking keys about data available in SAP. These include APPLID (TPDA: ID of the Debugger Framework User), DUSER (User Name in User Master Record), LNAME (TPDA: Layout Name of User-Specific Debugger Layout), BPID (TPDA: Debug Session - Breakpoint ID).. 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: Can be enhanced (character-type or numeric)
SAP TPDA_SESSIONS_BPS 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 |
APPLID | TPDA: ID of the Debugger Framework User | TPDA_FRAMEWORK_MEMBER_ID | CHAR | 20 | |||||
DUSER | User Name in User Master Record | XUBNAME | CHAR | 12 | USR02 | XUBNAME | XUS | ||
LNAME | TPDA: Layout Name of User-Specific Debugger Layout | TPDA_LAYOUT_NAME | CHAR | 30 | TPDASESSIONS | CHAR30 | |||
BPID | TPDA: Debug Session - Breakpoint ID | TPDA_SESS_BPID | INT4 | 10 | |||||
FLAGACTIVE | General Flag | FLAG | CHAR | 1 | FLAG | ||||
KIND | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
SKIPCNT | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
.INCLU-SRC | 0 | ||||||||
PROGNAMESRC | Calling Program | SYCPROG | CHAR | 40 | Assigned to domain | PROGRAMM | |||
INCLNAMESRC | Calling Program | SYCPROG | CHAR | 40 | Assigned to domain | PROGRAMM | |||
LINESRC | Line in Source | 0 | |||||||
.INCLU-STA | 0 | ||||||||
STATEMENTSTA | 0 | ||||||||
.INCLU-FOR | 0 | ||||||||
PROGNAMEFOR | Calling Program | SYCPROG | CHAR | 40 | Assigned to domain | PROGRAMM | |||
SUBRNAMEFOR | SYSTEM-EXIT Subroutine | SYXFORM | CHAR | 30 | SYCHAR30 | ||||
.INCLU-MET | 0 | ||||||||
PROGNAMEMET | Calling Program | SYCPROG | CHAR | 40 | Assigned to domain | PROGRAMM | |||
CLASSNAMEMET | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
METHODNAMEMET | Full Component Name | SEOCPDNAME | CHAR | 61 | CHAR61 | ||||
METHKINDMET | See BPMK_* - Constants: global, localprog, localcpool | 0 | |||||||
.INCLU-FUN | 0 | ||||||||
FUNCMNAMEFUN | Name of Function Module | RS38L_FNAM | CHAR | 30 | Assigned to domain | FUNCNAME | LIB | ||
.INCLU-EXC | 0 | ||||||||
CLASSNAMEEXC | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
.INCLU-SYS | 0 | ||||||||
DUMMYFIELDSYS | 0 | ||||||||
.INCLU-NPR | 0 | ||||||||
DUMMYFIELDNPR | 0 | ||||||||
.INCLU-INE | 0 | ||||||||
DUMMYFIELDINE | 0 | ||||||||
.INCLU-TEM | 0 | ||||||||
PROGNAMETEM | Calling Program | SYCPROG | CHAR | 40 | Assigned to domain | PROGRAMM | |||
TEMPLATETEM | SYSTEM-EXIT Subroutine | SYXFORM | CHAR | 30 | SYCHAR30 |
Key field | Non-key field |
How do I retrieve data from SAP structure TPDA_SESSIONS_BPS using ABAP code?
As TPDA_SESSIONS_BPS 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 TPDA_SESSIONS_BPS as there is no data to select.How to access SAP table TPDA_SESSIONS_BPS
Within an ECC or HANA version of SAP you can also view further information about TPDA_SESSIONS_BPS 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