SAP MS_GET_TRACEFILE Function Module for









MS_GET_TRACEFILE is a standard ms get tracefile SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ms get tracefile FM, simply by entering the name MS_GET_TRACEFILE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSGSERVER
Program Name: SAPLMSGSERVER
Main Program: SAPLMSGSERVER
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MS_GET_TRACEFILE 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 'MS_GET_TRACEFILE'"
 IMPORTING
   LINES =  "
   SRVNAME =  "

EXCEPTIONS
   NO_SERVER_LIST = 1    OPEN_FAILED = 2    RFC_ERROR = 3    INTERNAL_ERROR = 4    NOT_AUTHORIZED = 5    NOT_FOUND = 6
.



EXPORTING Parameters details for MS_GET_TRACEFILE

LINES -

Data type: SYMSG_LLINES
Optional: No
Call by Reference: Yes

SRVNAME -

Data type: C
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_SERVER_LIST - No list of servers received

Data type:
Optional: No
Call by Reference: Yes

OPEN_FAILED -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - No Authorization

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MS_GET_TRACEFILE 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_lines  TYPE SYMSG_LLINES, "   
lv_no_server_list  TYPE SYMSG_LLINES, "   
lv_srvname  TYPE C, "   
lv_open_failed  TYPE C, "   
lv_rfc_error  TYPE C, "   
lv_internal_error  TYPE C, "   
lv_not_authorized  TYPE C, "   
lv_not_found  TYPE C. "   

  CALL FUNCTION 'MS_GET_TRACEFILE'  "
    IMPORTING
         LINES = lv_lines
         SRVNAME = lv_srvname
    EXCEPTIONS
        NO_SERVER_LIST = 1
        OPEN_FAILED = 2
        RFC_ERROR = 3
        INTERNAL_ERROR = 4
        NOT_AUTHORIZED = 5
        NOT_FOUND = 6
. " MS_GET_TRACEFILE




ABAP code using 7.40 inline data declarations to call FM MS_GET_TRACEFILE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!