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 the content of this article is relevant only for SCM_BASIS Version 7.0 and subsequent versions by default. If the content is applicable to SCM_BASIS 5.0 or 5.1, that will be indicated.

Purpose

The purpose of this page is to provide useful hints and info on working with SCM APO - SDP, FCS and PPS alerts.

Alert Monitor in SCM User Assistance Page (SAP Help).

Overview:

The Alert Monitor is a valuable tool for monitoring exceptions within the system. It uses event triggers and alarm conditions established during planning and scheduling to automatically identify problems in the supply chain. It monitors factors such as material, capacity, transportation and storage constraints, as well as metrics such as delivery performance, cost flow and throughput.

The main transaction for AMO is /N/SAPAPO/AMON1

The alert types can be managed in /N/SAPAPO/AMOCFG

The Alert Monitor related tables > Transaction code SE11: /SAPAPO/AM* + F4 help

In essence, the Alert Monitor is a tool used by planners to monitor the state of planning in the system, and the actual alerts serve as guidelines for replanning.

The attached document contains detailed information and useful hints on SDP and FCS Alerts.

Please note that the Alert Engine has been reorganized at SCM 7.0. You can meet several differences in the coding, the alert determination process and in the User Interface as well after an upgrade from eg. 5.0, 5.1 to 7.0 or higher.

Alert Creation:

  • Depending on the SCM application the alerts can be database or dynamic alerts.
  • Database alerts are created by the application itself for example in case of SDP macro executions in transaction /N/SAPAPO/MC8G. Such jobs can fill the alert database tables with the necessary entries.
  • Dynamic alerts are stored at transaction data level and always maintained real-time.

Alert determination:

Alert Monitoring for PP/DS: SAP Help for PP/DS alerts
The class (acces from SE24) in case of PPS alerts: /SAPAPO/CL_AMOALRT_PP   >>  READ_PP_ALERTS

Alert Monitoring SDP (Supply and Demand Planning):
The class (acces from SE24) in case of SDP alerts: /SAPAPO/CL_AMOALRT_SD  >> READ_SDP_ALERTS

  • SDP Selection IDs (for selection profiles) are stored in: /SAPAPO/TS_SELKO, /SAPAPO/TS_SELPO

Alert Monitoring Overall profile: (from here the application alert profiles are called)
The class (acces from SE24) in case of overall profiles: /SAPAPO/CL_AMOALRT_AMO >> READ_ALERTS

Further Classes:

/SAPAPO/ALERT_MANAGER

/SAPAPO/CL_AMOALRT_APP

/SAPAPO/CL_AMOALRT_APO

BADIs to modify default alert determination:

  1. Alert Priority settings: BADI modify_alert_priority (from interface /SAPAPO/IF_EX_AM_SET_PRIO) > called in FM /SAPAPO/AMOS_ALERT_PRIO_SET
  2. Alert list changes: Class: /SAPAPO/CL_AMOALRT_APP > modify_alertlist_badi  example class: /SAPAPO/CL_EXM_IM_AM_ALERTLIST
  3. Customer defined alert types - only for PPDS  > Class: /SAPAPO/AM_ALERT_PP > READ_CUSTDEF_ALERTS and READ_CUSTDEF_NETALERTS ( CALL BADI p_badi_am_alert_pp->read_custdef_netalerts )
  4. /SAPAPO/CL_AMOALRT_APO > enhancement possibilites
  5. BAdI /SAPAPO/AM_ALERTLIST - MODIFY_FIELDCATALOG - 1374207 - AMON: Modifying the field catalog of saved alert situations - example class: /SAPAPO/CL_EXM_IM_AM_ALERTLIST

 

PP/DS Resource Alerts:

To be able to determine the resource capacity load alerts in the Alert Monitor, please make sure to define a value other than 0 to the two fields Underload Alerts from (%) and Overload Alerts fr.(%) . This two fields reflect the static threshold values instead of the 3 level threshold which used in general to alert types, and these fields must not be equal to 0. Otherwise the program will not determine any alerts.



Forwarded Alerts:

  • You can forward alerts from the alert grid to another SAP user (Planner) with the ''Envelope'' button. This will be shown to the addressed user every time she determines alerts, with an envelope sign on it. It can be acknowledged with the ''Undo" button (that clears any type of status icons from the alerts)

  • Forwarded status is stored in the /SAPAPO/AM_FRWD database table.

Show alerts on the alert grid (ALV view in e.g. /sapapo/amon1 transaction)

The determined alerts are displayed on a table view solution, called ALV view. This provides with a structured display of the alerts, with additional functions, such as exporting to an excel sheet. Although this display mode is created for dialog usage and not to process huge amount of records. Therefore in case of more thousand entries, the alert methods may not be able to pass the data to the ALV program. Therefore please consolidate the selection criteria of the alerts to be displayed for a realistic, dialog mode usage.

/SAPAPO/ALERT_MONITOR class , method > show_alerts

Performance of the Alert Monitor:

Different alert types can be determined for many SCM applications and especially the database alert types are distributed in several alert database tables. Mostly database alert types can grow into huge amount entries. Reading them as a whole can take time, therefore a reasonable selection criteria is highly advised to set up in the /SAPAPO/AMON1 transaction. Please use different selection fields such as product, location and date-time interval. It is also advised NOT to include every database alert type (AOT, AT_ID) into one profile, but to separate them into more profiles.

If the alert determination still takes a considerable amount of time in the dialog mode, it is advised to set up background alert jobs, for obtaining saved alert situations. For more information please see: Alert Determination in the Background / Saved Alert Situations 

Please also consider to regularly remove obsolete records from the database, see ''Deletion of alerts''


Database Tables:

Alert Monitoring tables can be found from SE11 or SE16 transactions by typing /SAPAPO/AM* and pressing F4 help. This lists out most of the relevant tables.

  • /SAPAPO/AM_NOTE > this table stores the actual entries that you see in the ALV view in eg. /SAPAPO/AMON1 or in the respective application. The info fields (1-4) includes the alert entry's details. MANDT / NOTE_ID is the key of the table.

  • /SAPAPO/AM_NOTES > Different alert statuses eg. Take note of alert's tag is found here, this table stores the alert status. MANDT / NOTE_ID / USERNAME / STATUS are forming the key. Therefore the take note of alerts can be differentiated by logon user.

  • /SAPAPO/ALERT_HP > PP/DS database alerts.

  • /SAPAPO/AM_ALERT > Database Alerts
  • /SAPAPO/AM_FRWD
  • /SAPAPO/*ALERT* > F4 help can reveal more
  • /SAPAPO/AM* > F4 help can reveal more

 

Authorization objects for Alert Monitor:

There are two objects existing for Alert Monitor authority checks: C_APO_AMON and C_APO_APRF.

Please see note: ''2042570 - Authorization checks for profile is not called in the Alert Monitor'' in order to set up the possible authorization routes for Alert Monitor for different users.


Alert Determination in the Background / Saved Alert Situations:

The following test case introduces how to create saved alert situations in the background: [TEST CASE] Download saved alert situation to a folder into an .xls (Excel) file

Note: When processing background alert determination for more than one Alert Profiles it is important that the first (initial) determination is executed on them one after another. Paying attention to this will secure that the /SAPAPO/AMSAFTY table is maintained with distinct entries (eg. /SCMB/AMOB1, /SCMB/AMOB2) regarding the field: /SAPAPO/AMSAFTY-ALERTDB for each alert profiles. This means that each alert profile, that is saved for background processing will have its own alert database, where its further attributes are stored. After this initial step the background determination can freely be processed in the same time slot for several saved alert profiles (eg. in a parallel setup RSPC chain).

If you meet such issues that one alert profile's saved alert situation overwrites another profile's saved situation, the most possible root cause is that they have the same DB value in the /SAPAPO/AMSAFTY table. This can happen if the previously described initial separated execution was not met. To eliminate this inconsistent state the alert profile's saved for background determination must be deleted and recreated again. This can be done in transaction /SAPAPO/AMON1 / Go To / Favorite Management / Alerts in the background Tab. The same place where they were initially saved. After recreation the initial separated execution is required as described above in order to raise its own unique database.


Deletion of alerts and Alert Tables Housekeeping:

  • report: /SAPAPO/AMODAL_DELETE    > class / method: /sapapo/cl_amodal_manager=>alert_delete_by_list  >>> deletes from DB /SAPAPO/AM_ALERTS
                                                                   > class / method: /sapapo/cl_amonote=>alert_note_del     >>>   deletes from  DB /SAPAPO/AM_NOTE, /SAPAPO/AM_NOTES,  /SAPAPO/AM_NOTEP, /SAPAPO/AM_FRWD
  • report: /SAPAPO/AMON_REORG          > class / method:  /sapapo/cl_amodal_manager=>alert_delete_by_list >>> deletes from /SAPAPO/AM_ALERTS, sapapo/alert_vm, and other application tables

1631214 - Deletion of Database Alerts

1631207 - Deletion of Alerts in SCM APO Alert Monitor

Keep in mind that these reports can become very memory intensive, if the alert storage tables are overgrowing. Please set up proper selection criteria including alert object types, alert types, and date intervals, in the initial screen to avoid memory dumps, also try to prevent the data overload by maintaining these tables regularly. SAP Help: Deleting Alerts

Please consider the data volume on both the above mentioned tables, as well as in the generated database tables e.g.: /scwm/alert2501

Alert Status:

Class (SE24) where ''Hide Alerts'' ''Take note of alerts'' are maintained and read: /SAPAPO/CL_AMONOTE
Database table: /SAPAPO/AM_NOTES, /SAPAPO/AM_NOTE

Housekeeping report: /SAPAPO/AMONOTE_DELETE

1574949 - APO Alert Status and Hidden Alerts are reset after redetermination (Take note of Alerts)

 

Alert Monitor BADI:

The main BAdi for Alert monitor The BADI user-exit is /SAPAPO/AM_ALERTLIST - please check its documentation in SE18 for further details.
Enhancing Alerts in Alert Monitor

 

Database Alert Determination in SCM_BASIS 5.0 and 5.1

Alert Adapter (APO) Class: /SAPAPO/ALERT_MANAGER (read database alerts for various applications) > methods: READ_SDP_ALERTS , READ_PP_ALERTS

Alert Engine class: /SCMB/ALEN

Alert Grid class: /SAPAPO/CL_ALERT_GRID

 

Related SAP Notes/KBAs

1631214 - Deletion of Database Alerts
2042570 - Authorization checks for profile is not called in the Alert Monitor
495166 - Usage of the alert monitor; Tips and tricks
830673 - AMON: Some consulting issues when handling alert monitor
500051 - Description of alert types
781319 - Creation of customer specific alerts
796769 - SDP: Absolute threshold values for user-spec. supply
521639 - Generation of DB Alerts in Background
1952882 - Planning area does not exist
1889826 - Variance % not calculated for Alert
1843690 - Double click in transaction /SAPAPO/AMON1 - Alert Monitor does not work
1765684 - Exception condition "DB_NOT_EXISTS" during Alerts determination in background.
1763158 - Function Module /SAPAPO/AMPLLP_SDP_ALERTS raises short dump CALL_FUNCTION_NOT_R
1631207 - Deletion of Alerts
1631214 - Deletion of Database Alerts
1574949 - APO Alert Status and Hidden Alerts are reset after redetermination (Take note of Alerts)
1565474 - Navigation from alert monitor to product view or context
1445740 - Filter button missing in Alert Monitor and Planning Book
1387758 - Sorting user-defined Hierarchies-Location/Products
2193806 - Selection for PPDS alert resulting in wrong results in case of excluded objects
1816352 - PPDS: AMON returns alerts which are not requested(BADI impl)
2238517 - FAQ ATP Alerts
1885008 - PP/DS Planning increasing table /SAPAPO/ALERT_HP