SAP LTSKM_ALERT_OBJECTS_GET Function Module for Get Problematic tasks









LTSKM_ALERT_OBJECTS_GET is a standard ltskm 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 ltskm alert objects get FM, simply by entering the name LTSKM_ALERT_OBJECTS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: LTSK_MONITOR
Program Name: SAPLLTSK_MONITOR
Main Program: SAPLLTSK_MONITOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function LTSKM_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 'LTSKM_ALERT_OBJECTS_GET'"Get Problematic tasks
  EXPORTING
*  IV_ROOT_OBJECT =  "Values of the Object Key Fields
   IV_OBCLS =  "Object Class for Monitoring
   IV_PRPRF =  "Presentation profile
   IV_ROOT_OBCLS =  "Root object-class

CHANGING
*  ET_OBJECT =  "
.



IMPORTING Parameters details for LTSKM_ALERT_OBJECTS_GET

IV_ROOT_OBJECT - Values of the Object Key Fields

Data type: LMON_OBJKEY_VAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OBCLS - Object Class for Monitoring

Data type: LMON_OBCLS
Optional: No
Call by Reference: No ( called with pass by value option)

IV_PRPRF - Presentation profile

Data type: LMON_PRPRF
Optional: No
Call by Reference: Yes

IV_ROOT_OBCLS - Root object-class

Data type: LMON_OBCLS_ROOT
Optional: No
Call by Reference: Yes

CHANGING Parameters details for LTSKM_ALERT_OBJECTS_GET

ET_OBJECT -

Data type: INDEX TABLE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LTSKM_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_et_object  TYPE INDEX TABLE, "   
lv_iv_root_object  TYPE LMON_OBJKEY_VAL, "   
lv_iv_obcls  TYPE LMON_OBCLS, "   
lv_iv_prprf  TYPE LMON_PRPRF, "   
lv_iv_root_obcls  TYPE LMON_OBCLS_ROOT. "   

  CALL FUNCTION 'LTSKM_ALERT_OBJECTS_GET'  "Get Problematic tasks
    EXPORTING
         IV_ROOT_OBJECT = lv_iv_root_object
         IV_OBCLS = lv_iv_obcls
         IV_PRPRF = lv_iv_prprf
         IV_ROOT_OBCLS = lv_iv_root_obcls
    CHANGING
         ET_OBJECT = lv_et_object
. " LTSKM_ALERT_OBJECTS_GET




ABAP code using 7.40 inline data declarations to call FM LTSKM_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!