SAP LWMSM_ALERT_OBJECTS_GET Function Module for Get problematic tasks
LWMSM_ALERT_OBJECTS_GET is a standard lwmsm alert objects get 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 problematic tasks 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 lwmsm alert objects get FM, simply by entering the name LWMSM_ALERT_OBJECTS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: LWMS_MONITOR
Program Name: SAPLLWMS_MONITOR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LWMSM_ALERT_OBJECTS_GET 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 'LWMSM_ALERT_OBJECTS_GET'"Get problematic tasks.
EXPORTING
* IV_PRPRF = "Site
IV_OBCLS = "Object class
CHANGING
* IT_OBJKEY = "
* ET_OBJECT = "
IMPORTING Parameters details for LWMSM_ALERT_OBJECTS_GET
IV_PRPRF - Site
Data type: LMON_PRPRFOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBCLS - Object class
Data type: LMON_OBCLSOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for LWMSM_ALERT_OBJECTS_GET
IT_OBJKEY -
Data type: INDEX TABLEOptional: Yes
Call by Reference: Yes
ET_OBJECT -
Data type: INDEX TABLEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for LWMSM_ALERT_OBJECTS_GET 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_iv_prprf | TYPE LMON_PRPRF, " | |||
| lv_it_objkey | TYPE INDEX TABLE, " | |||
| lv_iv_obcls | TYPE LMON_OBCLS, " | |||
| lv_et_object | TYPE INDEX TABLE. " |
|   CALL FUNCTION 'LWMSM_ALERT_OBJECTS_GET' "Get problematic tasks |
| EXPORTING | ||
| IV_PRPRF | = lv_iv_prprf | |
| IV_OBCLS | = lv_iv_obcls | |
| CHANGING | ||
| IT_OBJKEY | = lv_it_objkey | |
| ET_OBJECT | = lv_et_object | |
| . " LWMSM_ALERT_OBJECTS_GET | ||
ABAP code using 7.40 inline data declarations to call FM LWMSM_ALERT_OBJECTS_GET
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