SAP ST05_ACTIVATE_TRACE Function Module for









ST05_ACTIVATE_TRACE is a standard st05 activate trace 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 st05 activate trace FM, simply by entering the name ST05_ACTIVATE_TRACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: ST05_API
Program Name: SAPLST05_API
Main Program: SAPLST05_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ST05_ACTIVATE_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 'ST05_ACTIVATE_TRACE'"
EXPORTING
TRACE_TYPES = "
* TRACE_FILTER = "
* ALL_SERVERS = ' ' "

IMPORTING
SERVER_INFORMATION_TABLE = "

EXCEPTIONS
NO_AUTHORITY = 1 MISSING_TRACE_TYPE = 2 NO_CROSS_CLIENT_TRACING = 3 USER_MISMATCH = 4 ACTIVATION_ERROR = 5 NO_SERVER_LIST = 6
.



IMPORTING Parameters details for ST05_ACTIVATE_TRACE

TRACE_TYPES -

Data type: ST05_API_TRACE_TYPES
Optional: No
Call by Reference: No ( called with pass by value option)

TRACE_FILTER -

Data type: ST05_API_TRACE_FILTER
Optional: Yes
Call by Reference: No ( called with pass by value option)

ALL_SERVERS -

Data type: ST05_BOOLEAN
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ST05_ACTIVATE_TRACE

SERVER_INFORMATION_TABLE -

Data type: ST05_SERVER_INFORMATION_TABLE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

MISSING_TRACE_TYPE -

Data type:
Optional: No
Call by Reference: Yes

NO_CROSS_CLIENT_TRACING -

Data type:
Optional: No
Call by Reference: Yes

USER_MISMATCH -

Data type:
Optional: No
Call by Reference: Yes

ACTIVATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_SERVER_LIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ST05_ACTIVATE_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_trace_types  TYPE ST05_API_TRACE_TYPES, "   
lv_no_authority  TYPE ST05_API_TRACE_TYPES, "   
lv_server_information_table  TYPE ST05_SERVER_INFORMATION_TABLE, "   
lv_trace_filter  TYPE ST05_API_TRACE_FILTER, "   
lv_missing_trace_type  TYPE ST05_API_TRACE_FILTER, "   
lv_all_servers  TYPE ST05_BOOLEAN, "   ' '
lv_no_cross_client_tracing  TYPE ST05_BOOLEAN, "   
lv_user_mismatch  TYPE ST05_BOOLEAN, "   
lv_activation_error  TYPE ST05_BOOLEAN, "   
lv_no_server_list  TYPE ST05_BOOLEAN. "   

  CALL FUNCTION 'ST05_ACTIVATE_TRACE'  "
    EXPORTING
         TRACE_TYPES = lv_trace_types
         TRACE_FILTER = lv_trace_filter
         ALL_SERVERS = lv_all_servers
    IMPORTING
         SERVER_INFORMATION_TABLE = lv_server_information_table
    EXCEPTIONS
        NO_AUTHORITY = 1
        MISSING_TRACE_TYPE = 2
        NO_CROSS_CLIENT_TRACING = 3
        USER_MISMATCH = 4
        ACTIVATION_ERROR = 5
        NO_SERVER_LIST = 6
. " ST05_ACTIVATE_TRACE




ABAP code using 7.40 inline data declarations to call FM ST05_ACTIVATE_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.

 
 
 
 
 
DATA(ld_all_servers) = ' '.
 
 
 
 
 


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!