SAP EXCHANGE_PROFILE_GET_PARAMETER Function Module for
EXCHANGE_PROFILE_GET_PARAMETER is a standard exchange profile get parameter SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 exchange profile get parameter FM, simply by entering the name EXCHANGE_PROFILE_GET_PARAMETER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXMS_SLD_EP
Program Name: SAPLSXMS_SLD_EP
Main Program: SAPLSXMS_SLD_EP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXCHANGE_PROFILE_GET_PARAMETER 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 'EXCHANGE_PROFILE_GET_PARAMETER'".
EXPORTING
* SECTION = "
NAME = "Name of the profile parameter
IMPORTING
VALUE = "
EXCEPTIONS
NO_RFC_DESTINATION = 1 COMMUNICATION_ERROR = 2 EP_ERROR = 3 EP_ABAP_SHORTCUT_ERROR = 4 EP_ABAP_AUTH_PWD_ERROR = 5 EP_ABAP_AUTH_ERROR = 6
IMPORTING Parameters details for EXCHANGE_PROFILE_GET_PARAMETER
SECTION -
Data type: STRINGOptional: Yes
Call by Reference: Yes
NAME - Name of the profile parameter
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for EXCHANGE_PROFILE_GET_PARAMETER
VALUE -
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_RFC_DESTINATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_ERROR - Communication Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EP_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EP_ABAP_SHORTCUT_ERROR -
Data type:Optional: No
Call by Reference: Yes
EP_ABAP_AUTH_PWD_ERROR -
Data type:Optional: No
Call by Reference: Yes
EP_ABAP_AUTH_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXCHANGE_PROFILE_GET_PARAMETER 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.| DATA: | ||||
| lv_value | TYPE STRING, " | |||
| lv_section | TYPE STRING, " | |||
| lv_no_rfc_destination | TYPE STRING, " | |||
| lv_name | TYPE STRING, " | |||
| lv_communication_error | TYPE STRING, " | |||
| lv_ep_error | TYPE STRING, " | |||
| lv_ep_abap_shortcut_error | TYPE STRING, " | |||
| lv_ep_abap_auth_pwd_error | TYPE STRING, " | |||
| lv_ep_abap_auth_error | TYPE STRING. " |
|   CALL FUNCTION 'EXCHANGE_PROFILE_GET_PARAMETER' " |
| EXPORTING | ||
| SECTION | = lv_section | |
| NAME | = lv_name | |
| IMPORTING | ||
| VALUE | = lv_value | |
| EXCEPTIONS | ||
| NO_RFC_DESTINATION = 1 | ||
| COMMUNICATION_ERROR = 2 | ||
| EP_ERROR = 3 | ||
| EP_ABAP_SHORTCUT_ERROR = 4 | ||
| EP_ABAP_AUTH_PWD_ERROR = 5 | ||
| EP_ABAP_AUTH_ERROR = 6 | ||
| . " EXCHANGE_PROFILE_GET_PARAMETER | ||
ABAP code using 7.40 inline data declarations to call FM EXCHANGE_PROFILE_GET_PARAMETER
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