TREX_EXT_RESTART_SERVER SAP Function module - Restart a TREX server

TREX_EXT_RESTART_SERVER 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_RESTART_SERVER into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM TREX_EXT_RESTART_SERVER - TREX EXT RESTART SERVER

CALL FUNCTION 'TREX_EXT_RESTART_SERVER' "Restart a TREX server
  EXPORTING
    i_rfc_destination =         " trex_rfc-rfc_destination  RFC Destination
    i_server =                  " trexs_server_info-location  Host:port
    i_pids =                    " trexs_server_info-pids  process ID's separated by comma
    i_remote_method = '0'       " trex_rfc-numc3  0: restart Server, 1:reconfig 2:kill
  IMPORTING
    e_return_code =             " trex_rfc-return_code  Return Code
    e_return_text =             " trex_rfc-return_text  Return Text
  EXCEPTIONS
    CONVERSION_ERROR = 1        "               Error during UTF-8 conversion
    ERROR = 2                   "               Error, see error message
    .  "  TREX_EXT_RESTART_SERVER

ABAP code example for Function Module TREX_EXT_RESTART_SERVER

The ABAP code below is a full code listing to execute function module TREX_EXT_RESTART_SERVER 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
.



DATA(ld_i_rfc_destination) = some text here


DATA(ld_i_server) = some text here


DATA(ld_i_pids) = some text here


DATA(ld_i_remote_method) = Check type of data required
.

CALL FUNCTION 'TREX_EXT_RESTART_SERVER'
  EXPORTING
    i_rfc_destination =          ld_i_rfc_destination
    i_server =                   ld_i_server
    i_pids =                     ld_i_pids
    i_remote_method =            ld_i_remote_method
  IMPORTING
    e_return_code =              ld_e_return_code
    e_return_text =              ld_e_return_text
  EXCEPTIONS
    CONVERSION_ERROR =           1
    ERROR =                      2
    .  "  TREX_EXT_RESTART_SERVER

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_server
 
 TYPE TREXS_SERVER_INFO-LOCATION ,
ld_i_pids
 
 TYPE TREXS_SERVER_INFO-PIDS ,
ld_i_remote_method
 
 TYPE TREX_RFC-NUMC3 .



ld_i_rfc_destination = some text here

ld_i_server = some text here

ld_i_pids = some text here

ld_i_remote_method = Check type of data required