SAP PERFORMANCEA_TRACE_GET Function Module for









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

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



Function PERFORMANCEA_TRACE_GET 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 'PERFORMANCEA_TRACE_GET'"
 IMPORTING
   TRACE_USER =  "
   WRITE_TRACE_FILTER =  "
   PROC_NR =  "
   TCODE =  "
   PROGNAME =  "
   TAB_INC =  "
   TAB_EXC =  "
   SQL_TRACE_GET =  "
   ENQ_TRACE_GET =  "
   RFC_TRACE_GET =  "
   HTTP_TRACE_GET =  "
   BUF_TRACE_GET =  "
   MOD_USER =  "
   MOD_DATE =  "
   MOD_TIME =  "
.



EXPORTING Parameters details for PERFORMANCEA_TRACE_GET

TRACE_USER -

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

WRITE_TRACE_FILTER -

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

PROC_NR -

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

TCODE -

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

PROGNAME -

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

TAB_INC -

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

TAB_EXC -

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

SQL_TRACE_GET -

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

ENQ_TRACE_GET -

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

RFC_TRACE_GET -

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

HTTP_TRACE_GET -

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

BUF_TRACE_GET -

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

MOD_USER -

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

MOD_DATE -

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

MOD_TIME -

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

Copy and paste ABAP code example for PERFORMANCEA_TRACE_GET 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_user  TYPE SYUNAME, "   
lv_write_trace_filter  TYPE CHAR1, "   
lv_proc_nr  TYPE CHAR3, "   
lv_tcode  TYPE RSTRFTCODE, "   
lv_progname  TYPE RSTRFPROG, "   
lv_tab_inc  TYPE TABLIMIT, "   
lv_tab_exc  TYPE TABLIMIT, "   
lv_sql_trace_get  TYPE CHAR1, "   
lv_enq_trace_get  TYPE CHAR1, "   
lv_rfc_trace_get  TYPE CHAR1, "   
lv_http_trace_get  TYPE CHAR1, "   
lv_buf_trace_get  TYPE CHAR1, "   
lv_mod_user  TYPE SYUNAME, "   
lv_mod_date  TYPE DATS, "   
lv_mod_time  TYPE TIMS. "   

  CALL FUNCTION 'PERFORMANCEA_TRACE_GET'  "
    IMPORTING
         TRACE_USER = lv_trace_user
         WRITE_TRACE_FILTER = lv_write_trace_filter
         PROC_NR = lv_proc_nr
         TCODE = lv_tcode
         PROGNAME = lv_progname
         TAB_INC = lv_tab_inc
         TAB_EXC = lv_tab_exc
         SQL_TRACE_GET = lv_sql_trace_get
         ENQ_TRACE_GET = lv_enq_trace_get
         RFC_TRACE_GET = lv_rfc_trace_get
         HTTP_TRACE_GET = lv_http_trace_get
         BUF_TRACE_GET = lv_buf_trace_get
         MOD_USER = lv_mod_user
         MOD_DATE = lv_mod_date
         MOD_TIME = lv_mod_time
. " PERFORMANCEA_TRACE_GET




ABAP code using 7.40 inline data declarations to call FM PERFORMANCEA_TRACE_GET

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!