SAP SAL_WS_SYSTEM_OBJECT_SET_VALUE Function Module for Set some object value in monitoring segment
SAL_WS_SYSTEM_OBJECT_SET_VALUE is a standard sal ws system object set value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set some object value in monitoring segment 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 sal ws system object set value FM, simply by entering the name SAL_WS_SYSTEM_OBJECT_SET_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAL_WS
Program Name: SAPLSAL_WS
Main Program: SAPLSAL_WS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SAL_WS_SYSTEM_OBJECT_SET_VALUE 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 'SAL_WS_SYSTEM_OBJECT_SET_VALUE'"Set some object value in monitoring segment.
EXPORTING
DESTINATION = "Logical Destination (Specified When Function Is Called)
OBJECT = "Alert: Object
* VALUE = "Alert: Object
* TEXT = "Alert: Attribute Text
IMPORTING
ERROR_TEXT = "
EXCEPTIONS
CALL_INVALID = 1 INVALID_PARAMETERS = 2 INTERNAL_ERROR = 3 C_CALL_FAILED = 4 WS_PROXY_FAILURE = 5 NOT_CONNECTED_TO_SEGMENT = 6
IMPORTING Parameters details for SAL_WS_SYSTEM_OBJECT_SET_VALUE
DESTINATION - Logical Destination (Specified When Function Is Called)
Data type: RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT - Alert: Object
Data type: ALOBJMETH-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
VALUE - Alert: Object
Data type: ALOBJMETH-OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
TEXT - Alert: Attribute Text
Data type: ALTXTLCREA-ATTRTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SAL_WS_SYSTEM_OBJECT_SET_VALUE
ERROR_TEXT -
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
CALL_INVALID -
Data type:Optional: No
Call by Reference: Yes
INVALID_PARAMETERS -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
C_CALL_FAILED -
Data type:Optional: No
Call by Reference: Yes
WS_PROXY_FAILURE -
Data type:Optional: No
Call by Reference: Yes
NOT_CONNECTED_TO_SEGMENT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SAL_WS_SYSTEM_OBJECT_SET_VALUE 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_error_text | TYPE STRING, " | |||
| lv_destination | TYPE RFCDEST, " | |||
| lv_call_invalid | TYPE RFCDEST, " | |||
| lv_object | TYPE ALOBJMETH-OBJECT, " | |||
| lv_invalid_parameters | TYPE ALOBJMETH, " | |||
| lv_value | TYPE ALOBJMETH-OBJECT, " | |||
| lv_internal_error | TYPE ALOBJMETH, " | |||
| lv_text | TYPE ALTXTLCREA-ATTRTEXT, " | |||
| lv_c_call_failed | TYPE ALTXTLCREA, " | |||
| lv_ws_proxy_failure | TYPE ALTXTLCREA, " | |||
| lv_not_connected_to_segment | TYPE ALTXTLCREA. " |
|   CALL FUNCTION 'SAL_WS_SYSTEM_OBJECT_SET_VALUE' "Set some object value in monitoring segment |
| EXPORTING | ||
| DESTINATION | = lv_destination | |
| OBJECT | = lv_object | |
| VALUE | = lv_value | |
| TEXT | = lv_text | |
| IMPORTING | ||
| ERROR_TEXT | = lv_error_text | |
| EXCEPTIONS | ||
| CALL_INVALID = 1 | ||
| INVALID_PARAMETERS = 2 | ||
| INTERNAL_ERROR = 3 | ||
| C_CALL_FAILED = 4 | ||
| WS_PROXY_FAILURE = 5 | ||
| NOT_CONNECTED_TO_SEGMENT = 6 | ||
| . " SAL_WS_SYSTEM_OBJECT_SET_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM SAL_WS_SYSTEM_OBJECT_SET_VALUE
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 OBJECT FROM ALOBJMETH INTO @DATA(ld_object). | ||||
| "SELECT single OBJECT FROM ALOBJMETH INTO @DATA(ld_value). | ||||
| "SELECT single ATTRTEXT FROM ALTXTLCREA INTO @DATA(ld_text). | ||||
Search for further information about these or an SAP related objects