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

Function SCSM_CONTEXTS_UPDATE 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 'SCSM_CONTEXTS_UPDATE'".
EXPORTING
SEGMENT_TYPE = "
* SEGMENT_DESTINAT = "
* MCCREATE = "
* UPDATE_USER = SY-UNAME "SAP System, User Logon Name
* SUPPRESS_REFILL = ' ' "Alert: SALC: Flag (X) if only local input for function call
* SEGMENT_VERSION = "Alert: Version of Monitoring Infrastructure
EXCEPTIONS
COULD_NOT_SET_ENQUEUE = 1 SYSTEMWIDE_ONLY_FOR_APPSERVER = 2 RFCDEST_MISSING_FOR_HOSTSEGM = 3 RFC_ERROR_IN_SALS_CALL = 4
IMPORTING Parameters details for SCSM_CONTEXTS_UPDATE
SEGMENT_TYPE -
Data type: ALCONSEG-SEGMENTTYPOptional: No
Call by Reference: Yes
SEGMENT_DESTINAT -
Data type: RFCDESTOptional: Yes
Call by Reference: Yes
MCCREATE -
Data type: ALMCCREAT2Optional: Yes
Call by Reference: Yes
UPDATE_USER - SAP System, User Logon Name
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: Yes
SUPPRESS_REFILL - Alert: SALC: Flag (X) if only local input for function call
Data type: ALPARAMS-ONLY_LOCALDefault: ' '
Optional: Yes
Call by Reference: Yes
SEGMENT_VERSION - Alert: Version of Monitoring Infrastructure
Data type: ALCONSEG-VERSIONOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
COULD_NOT_SET_ENQUEUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEMWIDE_ONLY_FOR_APPSERVER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RFCDEST_MISSING_FOR_HOSTSEGM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RFC_ERROR_IN_SALS_CALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SCSM_CONTEXTS_UPDATE 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_segment_type | TYPE ALCONSEG-SEGMENTTYP, " | |||
| lv_could_not_set_enqueue | TYPE ALCONSEG, " | |||
| lv_segment_destinat | TYPE RFCDEST, " | |||
| lv_systemwide_only_for_appserver | TYPE RFCDEST, " | |||
| lv_mccreate | TYPE ALMCCREAT2, " | |||
| lv_rfcdest_missing_for_hostsegm | TYPE ALMCCREAT2, " | |||
| lv_update_user | TYPE SY-UNAME, " SY-UNAME | |||
| lv_rfc_error_in_sals_call | TYPE SY, " | |||
| lv_suppress_refill | TYPE ALPARAMS-ONLY_LOCAL, " ' ' | |||
| lv_segment_version | TYPE ALCONSEG-VERSION. " |
|   CALL FUNCTION 'SCSM_CONTEXTS_UPDATE' " |
| EXPORTING | ||
| SEGMENT_TYPE | = lv_segment_type | |
| SEGMENT_DESTINAT | = lv_segment_destinat | |
| MCCREATE | = lv_mccreate | |
| UPDATE_USER | = lv_update_user | |
| SUPPRESS_REFILL | = lv_suppress_refill | |
| SEGMENT_VERSION | = lv_segment_version | |
| EXCEPTIONS | ||
| COULD_NOT_SET_ENQUEUE = 1 | ||
| SYSTEMWIDE_ONLY_FOR_APPSERVER = 2 | ||
| RFCDEST_MISSING_FOR_HOSTSEGM = 3 | ||
| RFC_ERROR_IN_SALS_CALL = 4 | ||
| . " SCSM_CONTEXTS_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM SCSM_CONTEXTS_UPDATE
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 SEGMENTTYP FROM ALCONSEG INTO @DATA(ld_segment_type). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_update_user). | ||||
| DATA(ld_update_user) | = SY-UNAME. | |||
| "SELECT single ONLY_LOCAL FROM ALPARAMS INTO @DATA(ld_suppress_refill). | ||||
| DATA(ld_suppress_refill) | = ' '. | |||
| "SELECT single VERSION FROM ALCONSEG INTO @DATA(ld_segment_version). | ||||
Search for further information about these or an SAP related objects