SAP /SDF/MSS_DEV_TRACE Function Module for SQL Server information from the developper trace
/SDF/MSS_DEV_TRACE is a standard /sdf/mss dev 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 SQL Server information from the developper trace 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 /sdf/mss dev trace FM, simply by entering the name /SDF/MSS_DEV_TRACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SDF/RI_SQLSERVER
Program Name: /SDF/SAPLRI_SQLSERVER
Main Program: /SDF/SAPLRI_SQLSERVER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SDF/MSS_DEV_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 '/SDF/MSS_DEV_TRACE'"SQL Server information from the developper trace.
EXPORTING
* CONTROLFLAG = ' ' "Free text
TABLES
* DEVTRACE = "
EXCEPTIONS
NOT_SQLSERVER = 1 CANT_OPEN_FILE = 2
IMPORTING Parameters details for /SDF/MSS_DEV_TRACE
CONTROLFLAG - Free text
Data type: /SDF/TABLE-FIELD1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for /SDF/MSS_DEV_TRACE
DEVTRACE -
Data type: /SDF/TABLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_SQLSERVER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANT_OPEN_FILE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /SDF/MSS_DEV_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: | ||||
| lt_devtrace | TYPE STANDARD TABLE OF /SDF/TABLE, " | |||
| lv_controlflag | TYPE /SDF/TABLE-FIELD1, " ' ' | |||
| lv_not_sqlserver | TYPE /SDF/TABLE, " | |||
| lv_cant_open_file | TYPE /SDF/TABLE. " |
|   CALL FUNCTION '/SDF/MSS_DEV_TRACE' "SQL Server information from the developper trace |
| EXPORTING | ||
| CONTROLFLAG | = lv_controlflag | |
| TABLES | ||
| DEVTRACE | = lt_devtrace | |
| EXCEPTIONS | ||
| NOT_SQLSERVER = 1 | ||
| CANT_OPEN_FILE = 2 | ||
| . " /SDF/MSS_DEV_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM /SDF/MSS_DEV_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.| "SELECT single FIELD1 FROM /SDF/TABLE INTO @DATA(ld_controlflag). | ||||
| DATA(ld_controlflag) | = ' '. | |||
Search for further information about these or an SAP related objects