SAP HDB_GET_EXECUTION_TRACE Function Module for HDB: Gets the execution trace in XML form and saves it on the disk
HDB_GET_EXECUTION_TRACE is a standard hdb get execution trace SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HDB: Gets the execution trace in XML form and saves it on the disk processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for hdb get execution trace FM, simply by entering the name HDB_GET_EXECUTION_TRACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SHDB
Program Name: SAPLSHDB
Main Program: SAPLSHDB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HDB_GET_EXECUTION_TRACE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'HDB_GET_EXECUTION_TRACE'"HDB: Gets the execution trace in XML form and saves it on the disk.
EXPORTING
CON_NAME = "Logical name for a database connection
SQL_STMT = "SQL statement
IMPORTING
RC = "RC of the PlanViz-Plan
IMPORTING Parameters details for HDB_GET_EXECUTION_TRACE
CON_NAME - Logical name for a database connection
Data type: DBCON_NAMEOptional: No
Call by Reference: Yes
SQL_STMT - SQL statement
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HDB_GET_EXECUTION_TRACE
RC - RC of the PlanViz-Plan
Data type: IOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HDB_GET_EXECUTION_TRACE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_rc | TYPE I, " | |||
| lv_con_name | TYPE DBCON_NAME, " | |||
| lv_sql_stmt | TYPE STRING. " |
|   CALL FUNCTION 'HDB_GET_EXECUTION_TRACE' "HDB: Gets the execution trace in XML form and saves it on the disk |
| EXPORTING | ||
| CON_NAME | = lv_con_name | |
| SQL_STMT | = lv_sql_stmt | |
| IMPORTING | ||
| RC | = lv_rc | |
| . " HDB_GET_EXECUTION_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM HDB_GET_EXECUTION_TRACE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects