TREX_EXT_DELETE_TRACE_FILE SAP Function module - Get list of trace files for one TREX landscape

TREX_EXT_DELETE_TRACE_FILE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name TREX_EXT_DELETE_TRACE_FILE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: TREX_EXT_TRACE
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM TREX_EXT_DELETE_TRACE_FILE - TREX EXT DELETE TRACE FILE

CALL FUNCTION 'TREX_EXT_DELETE_TRACE_FILE' "Get list of trace files for one TREX landscape
  EXPORTING
    i_rfc_destination =         " trex_rfc-rfc_destination  RFC destination to TREX engine
    i_trace_files =             " trext_trace_files  File name pattern
  IMPORTING
    e_return_code =             " trex_rfc-return_code  Return code
    e_return_text =             " trex_rfc-return_text  Return text
    e_files_return =            " trext_trace_files  list of trace files
  EXCEPTIONS
    CONVERSION_ERROR = 1        "               Error during conversion to UTF-8
    ERROR = 2                   "               Error, see error message
    .  "  TREX_EXT_DELETE_TRACE_FILE

ABAP code example for Function Module TREX_EXT_DELETE_TRACE_FILE

The ABAP code below is a full code listing to execute function module TREX_EXT_DELETE_TRACE_FILE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_return_code  
 
 TYPE TREX_RFC-RETURN_CODE
,
ld_e_return_text  
 
 TYPE TREX_RFC-RETURN_TEXT
,
ld_e_files_return  
 
 TYPE TREXT_TRACE_FILES
.



DATA(ld_i_rfc_destination) = some text here

DATA(ld_i_trace_files) = 'Check type of data required'.
.

CALL FUNCTION 'TREX_EXT_DELETE_TRACE_FILE'
  EXPORTING
    i_rfc_destination =          ld_i_rfc_destination
    i_trace_files =              ld_i_trace_files
  IMPORTING
    e_return_code =              ld_e_return_code
    e_return_text =              ld_e_return_text
    e_files_return =             ld_e_files_return
  EXCEPTIONS
    CONVERSION_ERROR =           1
    ERROR =                      2
    .  "  TREX_EXT_DELETE_TRACE_FILE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_return_code
 
 TYPE TREX_RFC-RETURN_CODE ,
ld_i_rfc_destination
 
 TYPE TREX_RFC-RFC_DESTINATION ,
ld_e_return_text
 
 TYPE TREX_RFC-RETURN_TEXT ,
ld_i_trace_files
 
 TYPE TREXT_TRACE_FILES ,
ld_e_files_return
 
 TYPE TREXT_TRACE_FILES .



ld_i_rfc_destination = some text here
ld_i_trace_files = 'Check type of data required'.