TREX_EXT_ICM_THROUGHPUT SAP Function module - Throughput from all AppServers to all TREX IndexServers

TREX_EXT_ICM_THROUGHPUT 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_ICM_THROUGHPUT 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_ICM_THROUGHPUT - TREX EXT ICM THROUGHPUT

CALL FUNCTION 'TREX_EXT_ICM_THROUGHPUT' "Throughput from all AppServers to all TREX IndexServers
  EXPORTING
    trex_index_servers =        " trext_host_port  List of TREX IndexServers (Host and Port)
    data_package_size_kb =      " trex_rfc-numc  Data Package Size in KB; 0: only ping
    repeats =                   " trex_rfc-numc  Repeats
    with_ser_deser =            " trex_rfc-flag  Measure with searialization / deserialization
  IMPORTING
    e_icm_throughput =          " trext_icm_throughput_info  Throughput info for ICM
  EXCEPTIONS
    NOT_AVAILABLE = 1           "               Error in RFC_GET_LOCAL_SERVERS
    CONNECTION_TEST_ERROR = 2   "
    GENERAL_ERROR = 3           "               other errors
    .  "  TREX_EXT_ICM_THROUGHPUT

ABAP code example for Function Module TREX_EXT_ICM_THROUGHPUT

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


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


DATA(ld_data_package_size_kb) = 123 


DATA(ld_repeats) = 123 


DATA(ld_with_ser_deser) = some text here
.

CALL FUNCTION 'TREX_EXT_ICM_THROUGHPUT'
  EXPORTING
    trex_index_servers =         ld_trex_index_servers
    data_package_size_kb =       ld_data_package_size_kb
    repeats =                    ld_repeats
    with_ser_deser =             ld_with_ser_deser
  IMPORTING
    e_icm_throughput =           ld_e_icm_throughput
  EXCEPTIONS
    NOT_AVAILABLE =              1
    CONNECTION_TEST_ERROR =      2
    GENERAL_ERROR =              3
    .  "  TREX_EXT_ICM_THROUGHPUT

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
ELSEIF SY-SUBRC EQ 3. "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_icm_throughput
 
 TYPE TREXT_ICM_THROUGHPUT_INFO ,
ld_trex_index_servers
 
 TYPE TREXT_HOST_PORT ,
ld_data_package_size_kb
 
 TYPE TREX_RFC-NUMC ,
ld_repeats
 
 TYPE TREX_RFC-NUMC ,
ld_with_ser_deser
 
 TYPE TREX_RFC-FLAG .


ld_trex_index_servers = 'Check type of data required'.

ld_data_package_size_kb = 123 

ld_repeats = 123 

ld_with_ser_deser = some text here