SAP TREX_EXT_ALERTSERV_GET_CONFIG Function Module for Get Alertserver Configuration

Search SAP Function Modules

TREX_EXT_ALERTSERV_GET_CONFIG is a standard trex ext alertserv get config 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 Alertserver Configuration 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 alertserv get config FM, simply by entering the name TREX_EXT_ALERTSERV_GET_CONFIG into the relevant SAP transaction such as SE37 or SE38.

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

Function TREX_EXT_ALERTSERV_GET_CONFIG 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_ALERTSERV_GET_CONFIG'"Get Alertserver Configuration
  EXPORTING
   I_RFC_DESTINATION =  "RFC destination to TREX

 IMPORTING
   E_RETURN_CODE =  "Return Code
   E_TRACE_LEVEL =  "Trace Level
   E_CHECKSET_PROPERTIES =  "Properties of a Checkset in the TREX Alert Server
   E_CHECK_PROPERTIES =  "Properties of a Check in the TREX Alert Server
   E_SAVE_MAIL_TO_FILE =  "0: false, 1: true
   E_RETURN_TEXT =  "Return Text
   E_MAX_HISTORY_ENTRIES =  "
   E_MAX_HISTORY_AGE =  "
   E_SMTP_SERVER =  "
   E_MAIL_SENDER =  "
   E_MAIL_RECIPIENTS =  "
   E_MAIL_SUBJECT =  "
   E_SEND_MAILS =  "0: false, 1: true

EXCEPTIONS
   CONVERSION_ERROR = 1    ERROR = 2 

.

IMPORTING Parameters details for TREX_EXT_ALERTSERV_GET_CONFIG

I_RFC_DESTINATION - RFC destination to TREX

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

EXPORTING Parameters details for TREX_EXT_ALERTSERV_GET_CONFIG

E_RETURN_CODE - Return Code

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

E_TRACE_LEVEL - Trace Level

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

E_CHECKSET_PROPERTIES - Properties of a Checkset in the TREX Alert Server

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

E_CHECK_PROPERTIES - Properties of a Check in the TREX Alert Server

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

E_SAVE_MAIL_TO_FILE - 0: false, 1: true

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

E_RETURN_TEXT - Return Text

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

E_MAX_HISTORY_ENTRIES -

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

E_MAX_HISTORY_AGE -

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

E_SMTP_SERVER -

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

E_MAIL_SENDER -

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

E_MAIL_RECIPIENTS -

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

E_MAIL_SUBJECT -

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

E_SEND_MAILS - 0: false, 1: true

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

EXCEPTIONS details

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TREX_EXT_ALERTSERV_GET_CONFIG 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_ALERTSERV_GET_CONFIG

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