Loading…

SAP APO Alert Monitor Configuration

SAP APO Alert Monitor Configuration

What is Alert Monitor?

Supply chain planners need to constantly monitor the correctness of the forecast in APO for many products in a timely manner. Reviewing the forecasts individually for every IPC and market in several interactive planning books is very time-consuming and at most times not possible. A solution is required to have a central transaction where the forecasts can be reviewed on an exceptional basis. This function in SCM APO is called the Alert Monitor.

The aim of Demand Planning is to develop forecasts and demand plans that are as accurate as possible. You can use the Alert Monitor to monitor your planning for its precision and ability to be realized.

The alert monitor can be launched from the interactive planning book or as a standalone application. To do this, you use alert profiles to specify in what situations the system reports the problem, in other words, generates an alert. In the Alert Monitor Window, you can monitor all the alerts that have occurred, and can navigate directly to the relevant application function in order to resolve the problem. This document will focus on the standalone Alert Monitor.

In Demand Planning there are 2 alert groups that can be used: Forecast Alerts – system generated alerts for error situations occurring during the statistical forecast run; and Macro-dependent Alerts – alerts that are generated by call (either online or with a background job) for MNP-specific alerts such as forecast accuracy, consistency, etc.

This document will cover 2 kinds of alerts – database and dynamic. Database alerts are generated at a specified point in time and are saved in the database. These alerts do not change even if the planning situation has changed. Dynamic alerts are generated online in the application like interactive planning table and reflect the current planning situation. They cannot be saved to the database and are lost when you exit the application.

The overall process will be as follows:

Load of actual sales  Generation of database alerts for forecast accuracy and consistency  Read database alerts  Monitor alerts  Statistical forecasting and Manual adjustments  Backup MNP to MNP -1  Generation of database alerts for MNP  Read database alerts  Monitor alerts and correct demand plan if necessary.

The program, to generate alerts, will be executed weekly for the checks in the MNP situation, and monthly for the checks in forecast accuracy and consistency.

Example:
Alert Type: MNP vs. MNP-1 exceeds target (Database)
Description: An error message is raised if the absolute % variance exceeds 20% for any period of the next 6 months.
Frequency: Weekly

Alert Monitor Setting
(If the alert profile is already set up, proceed to Alert Monitor Administration or Alert Monitor.)

To use the alert monitor you need an alert profile to define the following:
• Period for which the system determines alerts.
• Application-specific (Forecasting, Supply and Demand Planning, PP/DS) alert profiles to define the alerts that can be viewed by a planner.
• Assignment of the relevant profile to your user.
• Assignment of a substitute user to a profile in case of planned leave from work.
• Configuration for determination of alerts in a background job.
• Structure or hierarchy for displaying the alerts.
• Object selection – planning version, planning book/data view, selection profile

Transaction Code: /SAPAPO/AMON_SETTING
Path: Supply Chain Monitoring  Current Settings  /SAPAPO/AMON_SETTING

Leave a Reply