SAP BAPI_SYSTEM_MT_GETALERTDATA Function Module for Read alert data into monitor tree









BAPI_SYSTEM_MT_GETALERTDATA is a standard bapi system mt getalertdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read alert data into monitor tree 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 bapi system mt getalertdata FM, simply by entering the name BAPI_SYSTEM_MT_GETALERTDATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALX
Program Name: SAPLSALX
Main Program: SAPLSALX
Appliation area: S
Release date: 22-Sep-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_SYSTEM_MT_GETALERTDATA 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 'BAPI_SYSTEM_MT_GETALERTDATA'"Read alert data into monitor tree
  EXPORTING
*  GET_ALERT_HISTORY = ' ' "Also Analyze Alert History
   EXTERNAL_USER_NAME =  "Name of the SAP-External User
*  START_TIMESTAMP =  "Alert: UTC Time Stamp in Format 
*  END_TIMESTAMP =  "Alert: UTC Time Stamp in Format 
*  LAST_X_MINUTES =  "Natural Number

 IMPORTING
   RETURN =  "Return Messages

TABLES
*  ROOT_NODES =  "Root of Requested Subtree
   TREE_NODES =  "Monitor Tree Elements
   ALERT_DATA =  "Alert Data Determined
.



IMPORTING Parameters details for BAPI_SYSTEM_MT_GETALERTDATA

GET_ALERT_HISTORY - Also Analyze Alert History

Data type: BAPIPARAMS-BOOL_PARA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXTERNAL_USER_NAME - Name of the SAP-External User

Data type: BAPIXMLOGR-EXTUSER
Optional: No
Call by Reference: No ( called with pass by value option)

START_TIMESTAMP - Alert: UTC Time Stamp in Format

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

END_TIMESTAMP - Alert: UTC Time Stamp in Format

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

LAST_X_MINUTES - Natural Number

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

EXPORTING Parameters details for BAPI_SYSTEM_MT_GETALERTDATA

RETURN - Return Messages

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

TABLES Parameters details for BAPI_SYSTEM_MT_GETALERTDATA

ROOT_NODES - Root of Requested Subtree

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

TREE_NODES - Monitor Tree Elements

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

ALERT_DATA - Alert Data Determined

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

Copy and paste ABAP code example for BAPI_SYSTEM_MT_GETALERTDATA 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_return  TYPE BAPIRET2, "   
lt_root_nodes  TYPE STANDARD TABLE OF ALGLOBTID, "   
lv_get_alert_history  TYPE BAPIPARAMS-BOOL_PARA, "   ' '
lt_tree_nodes  TYPE STANDARD TABLE OF BAPITNDEXT, "   
lv_external_user_name  TYPE BAPIXMLOGR-EXTUSER, "   
lt_alert_data  TYPE STANDARD TABLE OF BAPIALEXT, "   
lv_start_timestamp  TYPE ALTMSTPUTC, "   
lv_end_timestamp  TYPE ALTMSTPUTC, "   
lv_last_x_minutes  TYPE INT4. "   

  CALL FUNCTION 'BAPI_SYSTEM_MT_GETALERTDATA'  "Read alert data into monitor tree
    EXPORTING
         GET_ALERT_HISTORY = lv_get_alert_history
         EXTERNAL_USER_NAME = lv_external_user_name
         START_TIMESTAMP = lv_start_timestamp
         END_TIMESTAMP = lv_end_timestamp
         LAST_X_MINUTES = lv_last_x_minutes
    IMPORTING
         RETURN = lv_return
    TABLES
         ROOT_NODES = lt_root_nodes
         TREE_NODES = lt_tree_nodes
         ALERT_DATA = lt_alert_data
. " BAPI_SYSTEM_MT_GETALERTDATA




ABAP code using 7.40 inline data declarations to call FM BAPI_SYSTEM_MT_GETALERTDATA

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 BOOL_PARA FROM BAPIPARAMS INTO @DATA(ld_get_alert_history).
DATA(ld_get_alert_history) = ' '.
 
 
"SELECT single EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_external_user_name).
 
 
 
 
 


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!