Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Please note that this article is relevant only for SCM Version 7.0 and subsequent versions.

Purpose

This article describes the coding behind the alert determination in the READ_PP_ALERTS method (class: /SAPAPO/CL_AMOALRT_PP). This page can be useful to help in finding reasoning of why unexpected results are returned during PP alert determination in for example transaction /SAPAPO/AMON1. 

Overview

Use SE24 transaction to view the Class: /SAPAPO/CL_AMOALRT_PP. Chose method: READ_PP_ALERTS from the list.

(SCM 5.0 > a different object /SAPAPO/ALERT_MANAGER->READ_PP_ALERTS is applicable)

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

CHECK NOT plver IS INITIAL.

Peak points to check:

CALL FUNCTION '/SAPAPO/APROF_GET_PP'   >>  MATLOCs are returned

CALL METHOD get_pegids   >>  PEGIDs are returned

CALL   FUNCTION '/SAPAPO/OM_ALERTS_GET_DATA'   >> LiveCache Alerts are returned


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

VariableExplanation

L_AT_LIST_TAB

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

L_MATLOC_TAB

The Product Locations which are included the Alert Profile’s selection criteria

L_PEGID_TAB

The PEGIDs connected to the Product Locations (connected transactional data eg. orders)

L_LCALERTS_TAB

LCA alerts return from '/SAPAPO/OM_ALERTS_GET_DATA'

T_ALERTS

Determined Alert Records (it can get changed during the method by various methods/functions/BADis)

IT_ALERTS

Determined Alert Records

LT_ALERTS

Determined Alert Records

CT_ALERTS

Determined Alert Records

VFROM

FROM Time Stamp of the determination interval

VTO

TO Time Stamp of the determination interval


The BADi implementations for customer defined alert types and for modification of the alert list are placed at the very end of the method.

CALL BADI p_badi_am_alert_pp->read_custdef_alerts

CALL METHOD modify_alertlist_badi

The above BAdi implementations can be activated in SE18 BADI > /SAPAPO/AM_ALERTLIST

READ_CUSTDEF_PP_ALERTS
MODIFY_ALERTLIST
MODIFY_FIELDCATALOG

Database table /SAPAPO/LC_ALERT stores the LiveCache alert line numbers with respect to the Alert Types from transaction /N/SAPAPO/AMOCFG.

Interface: /SAPAPO/IF_EX_AM_SET_PRIO - MODIFY_ALERT_PRIORITY

Related Documents

Alert Monitor

Related SAP Notes/KBAs

 

 

  • No labels