TPDA_SCRIPT_DEBUG_SETTINGS SAP () Structure details
Description:
Related tables to TPDA_SCRIPT_DEBUG_SETTINGS
Access table TPDA_SCRIPT_DEBUG_SETTINGS
Structure field list including key, data, relationships and ABAP select examples
TPDA_SCRIPT_DEBUG_SETTINGS 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_SCRIPT_DEBUG_SETTINGS TYPE TPDA_SCRIPT_DEBUG_SETTINGS.
The TPDA_SCRIPT_DEBUG_SETTINGS table consists of various fields, each holding specific information or linking keys about data available in SAP. These include SYSTDBG (General Flag), CLOSEDEBF8 (TPDA: Option - Close Debugger After 'F8' and Roll Area End), SYNCBPS (TPDA: Copy Session BPs Automatically), EXCCREATEOBJECT (TPDA: Always Create Exception Object).. 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)
SAP TPDA_SCRIPT_DEBUG_SETTINGS 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 |
| SYSTDBG | General Flag | FLAG | CHAR | 1 | FLAG | ||||
| CLOSEDEBF8 | TPDA: Option - Close Debugger After 'F8' and Roll Area End | TPDA_CLOSE_DEB_F8 | CHAR | 1 | FLAG | ||||
| SYNCBPS | TPDA: Copy Session BPs Automatically | TPDA_SYNCBPS | CHAR | 1 | FLAG | ||||
| EXCCREATEOBJECT | TPDA: Always Create Exception Object | TPDA_EXCCREATEOBJECT | CHAR | 1 | FLAG | ||||
| UPDATEDEBUG | TPDA: Update Debugging On/Off | TPDA_UPDATEDEBUG | CHAR | 1 | FLAG | ||||
| BTCDEBUG | TPDA: In Background Task: Block Sending | TPDA_BTCDEBUG | CHAR | 1 | FLAG | ||||
| EMODESTACK | TPDA: Cross-Roll Area Stack | TPDA_EMODESTACK | CHAR | 1 | FLAG | ||||
| ESI | TPDA: Debugger Setting: ESI Debugging | TPDA_ESI | CHAR | 1 | |||||
| ACFLUSH | TPDA: Debugger Setting: Automation Controller Flush | TPDA_ACFLUSH | CHAR | 1 | |||||
| SOAAC | TPDA: Debugger Setting: Debug Shared Objects (SHO) | TPDA_SOAAC | CHAR | 1 | |||||
| CHECKREADBINARY | TPDA: Debugger Setting: Check READ BINARY SEARCH | TPDA_CHECKREADBINARY | CHAR | 1 | |||||
| LAYERCONTROL | TPDA Setting Layer Debugging | TPDA_LAYER_DEBUG | CHAR | 1 | |||||
| OBJECT_NAME | SLAD: Profile Name | SLAD_PROFILE_NAME | CHAR | 40 | SLAD_PROFILE | SLAD_OBJECT_NAME |
| Key field | Non-key field |
How do I retrieve data from SAP structure TPDA_SCRIPT_DEBUG_SETTINGS using ABAP code?
As TPDA_SCRIPT_DEBUG_SETTINGS 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_SCRIPT_DEBUG_SETTINGS as there is no data to select.How to access SAP table TPDA_SCRIPT_DEBUG_SETTINGS
Within an ECC or HANA version of SAP you can also view further information about TPDA_SCRIPT_DEBUG_SETTINGS 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