SAS_TRACE_ACTIONS_UI SAP (Structure for the Display of the Trace Actions) Structure details
Description: Structure for the Display of the Trace Actions
Related tables to SAS_TRACE_ACTIONS_UI
Access table SAS_TRACE_ACTIONS_UI
Structure field list including key, data, relationships and ABAP select examples
SAS_TRACE_ACTIONS_UI 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 "Structure for the Display of the Trace Actions" 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_SAS_TRACE_ACTIONS_UI TYPE SAS_TRACE_ACTIONS_UI.
The SAS_TRACE_ACTIONS_UI table consists of various fields, each holding specific information or linking keys about Structure for the Display of the Trace Actions data available in SAP. These include ACTION_ICON (Icons of the Action IDs), FROM_SCRIPT_FRAMEWORK (Flag for Action Trigger via Framework), TRIGGER_ID1 (Trigger ID), TRIGGER_ID2 (Trigger 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 (Deep)
SAP SAS_TRACE_ACTIONS_UI 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 |
| ACTION_INDEX | TPDA: Script Action Index | TPDA_SCRIPT_ACTION_INDEX | DEC | 31 | |||||
| ACTION_ICON | Icons of the Action IDs | SAS_SCRIPT_ACTION_ID_ICON | CHAR | 46 | TPDA_ICON | ||||
| FROM_SCRIPT_FRAMEWORK | Flag for Action Trigger via Framework | SAS_SCRIPT_FRAMEWORK_TRIGGERED | CHAR | 1 | FLAG | ||||
| TRIGGER_ID1 | Trigger ID | SAS_SCRIPT_TRIGGER_ID | SSTR | 255 | |||||
| TRIGGER_ID2 | Trigger ID | SAS_SCRIPT_TRIGGER_ID | SSTR | 255 | |||||
| SOURCE_FLAG | 0 | ||||||||
| EVENT_FLAG | 0 | ||||||||
| CUSTOM_FLAG | 0 | ||||||||
| CUSTOM_TREE_FLAG | 0 | ||||||||
| PROGRAM | TPDA:ASC Program in the Trace | TPDA_ASC_PROGRAM | SSTR | 40 | |||||
| INCLUDE | TPDA:ASC: Include in the Trace | TPDA_ASC_INCLUDE | SSTR | 40 | |||||
| LINE | TPDA: Source Code Line Number | TPDA_SC_LINE | INT4 | 10 | TPDA_INT4_NO_VZ | ||||
| EVENTTYPE | TPDA: ASC: Event Name in the Trace | TPDA_ASC_EVENTTYPE | SSTR | 30 | |||||
| EVENTNAME | TPDA: ASC: Event Name in the Trace | TPDA_ASC_EVENTNAME | SSTR | 70 | |||||
| LEVEL | tpda: Stack Level | TPDA_STACK_LEVEL | INT4 | 10 | |||||
| DYNPRO | Flag for Source Position on Screen | SAS_SCRIPT_DYNPRO_SOURCE | CHAR | 1 | FLAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure SAS_TRACE_ACTIONS_UI using ABAP code?
As SAS_TRACE_ACTIONS_UI 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 SAS_TRACE_ACTIONS_UI as there is no data to select.How to access SAP table SAS_TRACE_ACTIONS_UI
Within an ECC or HANA version of SAP you can also view further information about SAS_TRACE_ACTIONS_UI 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