TPDA_SCRIPT_ORIGIN SAP () Structure details
Description:
Related tables to TPDA_SCRIPT_ORIGIN
Access table TPDA_SCRIPT_ORIGIN
Structure field list including key, data, relationships and ABAP select examples
TPDA_SCRIPT_ORIGIN 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_ORIGIN TYPE TPDA_SCRIPT_ORIGIN.
The TPDA_SCRIPT_ORIGIN table consists of various fields, each holding specific information or linking keys about data available in SAP. These include CUSER (Changed by), CDATE (System Date), CTIME (System Time), SCRIPT_CLASS (TPDA: Script Class).. 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_SCRIPT_ORIGIN 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 |
| FILE_NAME | TPDA: File Name | TPDA_FILE_NAME | CHAR | 70 | |||||
| CUSER | Changed by | USER | CHAR | 12 | CHAR12 | ||||
| CDATE | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| CTIME | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
| SCRIPT_CLASS | TPDA: Script Class | TPDA_SCRIPT_CLASS | CHAR | 30 | SEOCLSNAME | CLASS | |||
| SCRIPT_COMMENT | Report title | REPTI | CHAR | 70 | REPTI | ||||
| WRITES_TRACE | TPDA: Script Contains Trace Output | TPDA_SCRIPT_WRITES_TRACE | CHAR | 1 | FLAG | ||||
| NO_BREAK | TPDA: Script Cannot Be Interrupted | TPDA_SCRIPT_NO_BREAK | CHAR | 1 | FLAG | ||||
| BP_REACHED | TPDA: Script Trigger: Breakpoint Reached | TPDA_TRIGGER_BP_REACHED | CHAR | 1 | FLAG | ||||
| WP_REACHED | TPDA: Script Trigger: Watchpoint Reached | TPDA_TRIGGER_WP_REACHED | CHAR | 1 | FLAG | ||||
| SINGLE_STEP | TPDA: Script Trigger: Debugger Single Step | TPDA_TRIGGER_SINGLE_STEP | CHAR | 1 | FLAG | ||||
| NEW_ROLLAREA | TPDA: Script Trigger: Roll Area Change | TPDA_TRIGGER_NEW_ROLLAREA | CHAR | 1 | FLAG | ||||
| SINGLE_RUN | TPDA: Script Trigger: Start Directly | TPDA_TRIGGER_DIRECT_RUN | CHAR | 1 | FLAG | ||||
| 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_ORIGIN using ABAP code?
As TPDA_SCRIPT_ORIGIN 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_ORIGIN as there is no data to select.How to access SAP table TPDA_SCRIPT_ORIGIN
Within an ECC or HANA version of SAP you can also view further information about TPDA_SCRIPT_ORIGIN 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