SAP Function Modules

comments icon Comments

BAPI_SYSTEM_ALERT_GETDETAILS SAP Function module - Read alert details







BAPI_SYSTEM_ALERT_GETDETAILS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BAPI_SYSTEM_ALERT_GETDETAILS into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SALX
Released Date: 22.09.1998
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BAPI_SYSTEM_ALERT_GETDETAILS - BAPI SYSTEM ALERT GETDETAILS 





CALL FUNCTION 'BAPI_SYSTEM_ALERT_GETDETAILS' "Read alert details
  EXPORTING
    aid =                       " bapiaid       Alert ID
*   get_active = 'X'            " bapiparams-bool_para  Analyze Active Alerts
*   get_history = ' '           " bapiparams-bool_para  Analyze Completed Alerts
    external_user_name =        " bapixmlogr-extuser  Name of the SAP-External User
  IMPORTING
    tid =                       " bapitid       ID of Monitor Tree Element Corresponding to Alert
    value =                     " bapialdata    Alert Data (Value, Severity)
    time =                      " bapialdate    Time of Alert
    properties =                " bapialert     General Alert Properties
    xmi_raw_msg =               " bapixmiraw    Parameters of the External Management Tool Message (Text, Arg)
    xmi_ext_msg =               " bapixmiext    Translated and Triggered External Management Tool Message
    return =                    " bapiret2      Return Messages
    .  "  BAPI_SYSTEM_ALERT_GETDETAILS

ABAP code example for Function Module BAPI_SYSTEM_ALERT_GETDETAILS





The ABAP code below is a full code listing to execute function module BAPI_SYSTEM_ALERT_GETDETAILS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_tid    TYPE BAPITID
,
ld_value    TYPE BAPIALDATA
,
ld_time    TYPE BAPIALDATE
,
ld_properties    TYPE BAPIALERT
,
ld_xmi_raw_msg    TYPE BAPIXMIRAW
,
ld_xmi_ext_msg    TYPE BAPIXMIEXT
,
ld_return    TYPE BAPIRET2
.




DATA(ld_aid) = 'Check type of data required'.


DATA(ld_get_active) = some text here


DATA(ld_get_history) = some text here
 

SELECT single EXTUSER 
  FROM BAPIXMLOGR 
  INTO @DATA(ld_external_user_name).

.

CALL FUNCTION 'BAPI_SYSTEM_ALERT_GETDETAILS'
  EXPORTING
    aid =                        ld_aid
*   get_active =                 ld_get_active
*   get_history =                ld_get_history
    external_user_name =         ld_external_user_name
  IMPORTING
    tid =                        ld_tid
    value =                      ld_value
    time =                       ld_time
    properties =                 ld_properties
    xmi_raw_msg =                ld_xmi_raw_msg
    xmi_ext_msg =                ld_xmi_ext_msg
    return =                     ld_return
    .  "  BAPI_SYSTEM_ALERT_GETDETAILS

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_tid  TYPE BAPITID ,
ld_aid  TYPE BAPIAID ,
ld_value  TYPE BAPIALDATA ,
ld_get_active  TYPE BAPIPARAMS-BOOL_PARA ,
ld_time  TYPE BAPIALDATE ,
ld_get_history  TYPE BAPIPARAMS-BOOL_PARA ,
ld_properties  TYPE BAPIALERT ,
ld_external_user_name  TYPE BAPIXMLOGR-EXTUSER ,
ld_xmi_raw_msg  TYPE BAPIXMIRAW ,
ld_xmi_ext_msg  TYPE BAPIXMIEXT ,
ld_return  TYPE BAPIRET2 .




ld_aid = 'Check type of data required'.

ld_get_active = some text here

ld_get_history = some text here

SELECT single EXTUSER 
  FROM BAPIXMLOGR 
  INTO ld_external_user_name.

SAP Documentation for FM BAPI_SYSTEM_ALERT_GETDETAILS


This function reports all relevant alert properties for an alert specified by an alert ID such as the alert value (or its severity) or ...See here for full SAP fm documentation







Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BAPI_SYSTEM_ALERT_GETDETAILS or its description.


   
 

BAPI_SYSTEM_ALERT_GETDETAILS - Read alert details
BAPI_SYSTEM_ALERT_ACKNOWLEDGE - Confirmation of an Alert
BAPI_SYNC_PROFILE_SET - Netweaver - MI:BAPI to set the profile (TX MEREP_PD)
BAPI_SYNC_JOB_SET - Netweaver - MI: BAPI planning a job
BAPI_SVCHANGE_GET_ITEMS - Read Retail Revaluation Document for Store, Key Date, Item Status
BAPI_SVCHANGE_CHANGE_STATUS - Enter Count Quantity and Change Item Status from A to B or C