SAP TREX_EXT_GET_TRACE_FILE Function Module for Get list of trace files for one TREX landscape

Search SAP Function Modules

TREX_EXT_GET_TRACE_FILE is a standard trex ext get trace file SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get list of trace files for one TREX landscape 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 trex ext get trace file FM, simply by entering the name TREX_EXT_GET_TRACE_FILE into the relevant SAP transaction such as SE37 or SE38.

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

Function TREX_EXT_GET_TRACE_FILE 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 'TREX_EXT_GET_TRACE_FILE'"Get list of trace files for one TREX landscape
  EXPORTING
   I_RFC_DESTINATION =  "RFC destination to TREX engine
   I_FILE_NAME =  "File name pattern
   I_HOST =  "Host
*  I_HEAD_OFFSET = 0 "Offset for i_head_length
*  I_HEAD_LENGTH = 50000 "Length in bytes from the beginning
*  I_TAIL_LENGTH = 0 "Length in bytes from the end

 IMPORTING
   E_RETURN_CODE =  "Return code
   E_RETURN_TEXT =  "Return text
   E_LINES =  "Content of the file
   E_LINES2 =  "Content of the file
   E_FILE_SIZE =  "File size

EXCEPTIONS
   CONVERSION_ERROR = 1    ERROR = 2 

.

IMPORTING Parameters details for TREX_EXT_GET_TRACE_FILE

I_RFC_DESTINATION - RFC destination to TREX engine

Data type: TREX_RFC-RFC_DESTINATION
Optional: No
Call by Reference: Yes

I_FILE_NAME - File name pattern

Data type: TREXS_FILE-FILE_NAME
Optional: No
Call by Reference: Yes

I_HOST - Host

Data type: TREXS_FILE-HOST
Optional: No
Call by Reference: Yes

I_HEAD_OFFSET - Offset for i_head_length

Data type: TREX_RFC-NUMC
Optional: Yes
Call by Reference: Yes

I_HEAD_LENGTH - Length in bytes from the beginning

Data type: TREX_RFC-NUMC
Default: 50000
Optional: Yes
Call by Reference: Yes

I_TAIL_LENGTH - Length in bytes from the end

Data type: TREX_RFC-NUMC
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TREX_EXT_GET_TRACE_FILE

E_RETURN_CODE - Return code

Data type: TREX_RFC-RETURN_CODE
Optional: No
Call by Reference: Yes

E_RETURN_TEXT - Return text

Data type: TREX_RFC-RETURN_TEXT
Optional: No
Call by Reference: Yes

E_LINES - Content of the file

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

E_LINES2 - Content of the file

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

E_FILE_SIZE - File size

Data type: TREXS_FILE-SIZE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CONVERSION_ERROR - Error during conversion to UTF-8

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

ERROR - Error, see error message

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

Copy and paste ABAP code example for TREX_EXT_GET_TRACE_FILE 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.

ABAP code using 7.40 inline data declarations to call FM TREX_EXT_GET_TRACE_FILE

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