SAP SQLT_WRITE_TRACE Function Module for Output SQL trace list
SQLT_WRITE_TRACE is a standard sqlt write 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 Output SQL trace list 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 sqlt write trace FM, simply by entering the name SQLT_WRITE_TRACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SSQ0
Program Name: SAPLSSQ0
Main Program: SAPLSSQ0
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SQLT_WRITE_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 'SQLT_WRITE_TRACE'"Output SQL trace list.
EXPORTING
* SORT_ORDER = "
TABLES
SQL_TRACE_TAB = "
SQL_BHEADER_TAB = "
EXCEPTIONS
WRONG_LIST_DESC = 1
IMPORTING Parameters details for SQLT_WRITE_TRACE
SORT_ORDER -
Data type: SQLT_SORT_ORDEROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SQLT_WRITE_TRACE
SQL_TRACE_TAB -
Data type: SQLT_TRACE_TABOptional: No
Call by Reference: No ( called with pass by value option)
SQL_BHEADER_TAB -
Data type: SQLT_BHEADER_TABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_LIST_DESC - Internal error - incorrect list description
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SQLT_WRITE_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_sort_order | TYPE SQLT_SORT_ORDER, " | |||
| lt_sql_trace_tab | TYPE STANDARD TABLE OF SQLT_TRACE_TAB, " | |||
| lv_wrong_list_desc | TYPE SQLT_TRACE_TAB, " | |||
| lt_sql_bheader_tab | TYPE STANDARD TABLE OF SQLT_BHEADER_TAB. " |
|   CALL FUNCTION 'SQLT_WRITE_TRACE' "Output SQL trace list |
| EXPORTING | ||
| SORT_ORDER | = lv_sort_order | |
| TABLES | ||
| SQL_TRACE_TAB | = lt_sql_trace_tab | |
| SQL_BHEADER_TAB | = lt_sql_bheader_tab | |
| EXCEPTIONS | ||
| WRONG_LIST_DESC = 1 | ||
| . " SQLT_WRITE_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM SQLT_WRITE_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