Skip to end of metadata
Go to start of metadata


This page contains debugging information regarding the program flow of the READ_SDP_ALERT method of class: /SAPAPO/CL_AMOALRT_SD. This page can be useful to help in finding reasoning of why unexpected results are returned during SDP alert determination in for example transaction /SAPAPO/AMON1.


Use SE24 transaction to view the Class: /SAPAPO/CL_AMOALRT_SD and choose method: READ_SDP_ALERT from the list.

For debugging reasons before Alert Determination the initial breakpoint can be set at statement:


Peak points to check:

*   reading of dynamical alerts
IF NOT l_read_dyn_alerts IS INITIAL. >> here, the dynamical alerts are checked if there are any, in the alert profile

*         read dynamic macro alerts for this data view and selection
          CALL FUNCTION '/SAPAPO/TS_DM_ALERT_GET' >> here, the dynamical alerts are listed

*       read alert from alert Data Access Layer
CLEAR lt_alert_macro_db.  >> here, the database macro alerts are obtained into LT_ALERT_MACRO_DB


LOOP AT lt_alert_macro_db INTO ls_alert_macro.  >> LOOP through on LT_ALERT_MACRO_DB check if the database alerts fit to the selection criteria of the alert profile. If an alert record (line) is not matching the selection, it will not be displayed.

The Main variables to track during debugging through the READ_SDP_ALERTS method:

T_ALERTStable including the final results of the read_sdp_alerts method
LT_ALERT_MACRO_DBmacro database alerts local table

dynamic alerts table

L_AT_LIST_TABAlert Types of  the profile (same as in transaction /N/SAPAPO/AMOCFG)

The BADi implementation for modification of the alert list are placed at the very end of the method.

CALL METHOD modify_alertlist_badi   

Related Content

Related Documents

Related SAP Notes/KBAs


  • No labels