SAP SET_PARAMETER Function Module for
SET_PARAMETER is a standard set 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 set parameter FM, simply by entering the name SET_PARAMETER into the relevant SAP transaction such as SE37 or SE38.
Function Group: SMON
Program Name: SAPLSMON
Main Program: SAPLSMON
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SET_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 'SET_PARAMETER'".
EXPORTING
* LOCAL_REMOTE = 'LOCAL' "
* LOGICAL_DESTINATION = "
* FP_DETAILSREQI = -1 "
* FP_DETAILSMODE = -1 "
* FP_NORMCOLLINT = -1 "
* FP_TRACELEVEL = -1 "
* FP_IDLEINTERVAL = -1 "
* FP_IDLEAFTER = -1 "
EXCEPTIONS
INTERNAL_ERROR_ADRESS_FAILED = 1 COMMUNICATION_FAILURE = 10 INTERNAL_ERROR_DIFFERENT_FIELD = 2 INTERNAL_ERROR_NO_NEW_LINE = 3 COLLECTOR_NOT_RUNNING = 4 SHARED_MEMORY_NOT_AVAILABLE = 5 COLLECTOR_BUSY = 6 VERSION_CONFLICT = 7 NO_NETWORK_COLLECTOR_RUNNING = 8 SYSTEM_FAILURE = 9
IMPORTING Parameters details for SET_PARAMETER
LOCAL_REMOTE -
Data type: DEF_PAR_FU-LOC_REMOTEDefault: 'LOCAL'
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOGICAL_DESTINATION -
Data type: RFCDES-RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
FP_DETAILSREQI -
Data type: DEF_PAR_FU-DETAILSREQDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
FP_DETAILSMODE -
Data type: DEF_PAR_FU-DETAILSMODDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
FP_NORMCOLLINT -
Data type: DEF_PAR_FU-NORMCOLLINDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
FP_TRACELEVEL -
Data type: DEF_PAR_FU-TRACELEVELDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
FP_IDLEINTERVAL -
Data type: DEF_PAR_FU-IDLEINTERVDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
FP_IDLEAFTER -
Data type: DEF_PAR_FU-IDLEAFTERDefault: -1
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERNAL_ERROR_ADRESS_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR_DIFFERENT_FIELD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR_NO_NEW_LINE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COLLECTOR_NOT_RUNNING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SHARED_MEMORY_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COLLECTOR_BUSY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VERSION_CONFLICT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_NETWORK_COLLECTOR_RUNNING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SET_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_local_remote | TYPE DEF_PAR_FU-LOC_REMOTE, " 'LOCAL' | |||
| lv_internal_error_adress_failed | TYPE DEF_PAR_FU, " | |||
| lv_communication_failure | TYPE DEF_PAR_FU, " | |||
| lv_logical_destination | TYPE RFCDES-RFCDEST, " | |||
| lv_internal_error_different_field | TYPE RFCDES, " | |||
| lv_fp_detailsreqi | TYPE DEF_PAR_FU-DETAILSREQ, " -1 | |||
| lv_internal_error_no_new_line | TYPE DEF_PAR_FU, " | |||
| lv_fp_detailsmode | TYPE DEF_PAR_FU-DETAILSMOD, " -1 | |||
| lv_collector_not_running | TYPE DEF_PAR_FU, " | |||
| lv_fp_normcollint | TYPE DEF_PAR_FU-NORMCOLLIN, " -1 | |||
| lv_shared_memory_not_available | TYPE DEF_PAR_FU, " | |||
| lv_fp_tracelevel | TYPE DEF_PAR_FU-TRACELEVEL, " -1 | |||
| lv_collector_busy | TYPE DEF_PAR_FU, " | |||
| lv_fp_idleinterval | TYPE DEF_PAR_FU-IDLEINTERV, " -1 | |||
| lv_version_conflict | TYPE DEF_PAR_FU, " | |||
| lv_fp_idleafter | TYPE DEF_PAR_FU-IDLEAFTER, " -1 | |||
| lv_no_network_collector_running | TYPE DEF_PAR_FU, " | |||
| lv_system_failure | TYPE DEF_PAR_FU. " |
|   CALL FUNCTION 'SET_PARAMETER' " |
| EXPORTING | ||
| LOCAL_REMOTE | = lv_local_remote | |
| LOGICAL_DESTINATION | = lv_logical_destination | |
| FP_DETAILSREQI | = lv_fp_detailsreqi | |
| FP_DETAILSMODE | = lv_fp_detailsmode | |
| FP_NORMCOLLINT | = lv_fp_normcollint | |
| FP_TRACELEVEL | = lv_fp_tracelevel | |
| FP_IDLEINTERVAL | = lv_fp_idleinterval | |
| FP_IDLEAFTER | = lv_fp_idleafter | |
| EXCEPTIONS | ||
| INTERNAL_ERROR_ADRESS_FAILED = 1 | ||
| COMMUNICATION_FAILURE = 10 | ||
| INTERNAL_ERROR_DIFFERENT_FIELD = 2 | ||
| INTERNAL_ERROR_NO_NEW_LINE = 3 | ||
| COLLECTOR_NOT_RUNNING = 4 | ||
| SHARED_MEMORY_NOT_AVAILABLE = 5 | ||
| COLLECTOR_BUSY = 6 | ||
| VERSION_CONFLICT = 7 | ||
| NO_NETWORK_COLLECTOR_RUNNING = 8 | ||
| SYSTEM_FAILURE = 9 | ||
| . " SET_PARAMETER | ||
ABAP code using 7.40 inline data declarations to call FM SET_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.| "SELECT single LOC_REMOTE FROM DEF_PAR_FU INTO @DATA(ld_local_remote). | ||||
| DATA(ld_local_remote) | = 'LOCAL'. | |||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_logical_destination). | ||||
| "SELECT single DETAILSREQ FROM DEF_PAR_FU INTO @DATA(ld_fp_detailsreqi). | ||||
| DATA(ld_fp_detailsreqi) | = -1. | |||
| "SELECT single DETAILSMOD FROM DEF_PAR_FU INTO @DATA(ld_fp_detailsmode). | ||||
| DATA(ld_fp_detailsmode) | = -1. | |||
| "SELECT single NORMCOLLIN FROM DEF_PAR_FU INTO @DATA(ld_fp_normcollint). | ||||
| DATA(ld_fp_normcollint) | = -1. | |||
| "SELECT single TRACELEVEL FROM DEF_PAR_FU INTO @DATA(ld_fp_tracelevel). | ||||
| DATA(ld_fp_tracelevel) | = -1. | |||
| "SELECT single IDLEINTERV FROM DEF_PAR_FU INTO @DATA(ld_fp_idleinterval). | ||||
| DATA(ld_fp_idleinterval) | = -1. | |||
| "SELECT single IDLEAFTER FROM DEF_PAR_FU INTO @DATA(ld_fp_idleafter). | ||||
| DATA(ld_fp_idleafter) | = -1. | |||
Search for further information about these or an SAP related objects