Show TOC

Component documentationMonitoring and Alerting Infrastructure Analysis Tools


The End-to-End Monitoring and Alerting Infrastructure (MAI) contains a lot of analysis tools for error handling. They are primarily intended for internal se by SAP, and for SAP Support.

To run the MAI analysis tools, call the transaction MAI_TOOLS. You need the role SAP_SM_TECH_MON_TOOL to call this transaction.

Caution Caution

When you call the transaction only a limited number of tools, which are for the use of customers, is displayed. You can display more tools by choosing (Expert Mode). These tools are only for SAP Support, so only selected tools are documented here.

End of the caution.


The Monitoring and Alerting Infrastructure tools are in tabs, which represent activities:

  • Analysis

  • Logs and Traces

  • Configuration

  • Simulation

  • Related Links

The tools are sorted by technical component, within each tab.

The following tools are available




Metric Troubleshoot

This tool program checks the data collection for the managed objects and monitoring use cases of metrics.

For more information, see Metric Troubleshoot.

Alerting Directory Browser

This tool gives an overview of the managed objects which are monitored in technical monitoring. The managed objects (e.g. the technical system PRD) are displayed, not their types (e.g. technical systems of type AS ABAP with release SAP NetWeaver 7.00 – 7.03), as in the Configuration Explorer.

The directory browser only displays values; you cannot make any changes. The metrics, events, alerts and templates used, are displayed for each managed object:

For more information, see Technical Monitoring Directory Browser.

Metric, Event, Alert Details

Use this tool to display technical information and the status of metric types and managed objects. On the selection screen of the program, you can specify the managed objects and metric types and the data about these objects that you want to display.

For more information, see Using the Metric, Event, Alert Details Program.

Check Directory Consistency

The Alerting Directory contains the metrics, events, and alerts (MEA) for managed objects (MOs) that are monitored in the MAI. Together with the MOs, these objects form a hierarchy, and the entry point is the root node of that hierarchy.

Use this tool to check the validity of this data, and remove obsolete entries from the MAI tables. For more information, see Using the Check Directory Consistency Program.

Data Provider Check for PULL_RFC Metrics

Thhis tool gets the current status and measured values of collectors of type PULL_RFC and their metrics.

For more information, see Using the Data Provider Check for PULL_RFC Metrics Program.

E2E MAI Support Servlet

This tool determines the current status, configuration settings and measured values passed, for diagnostics agents and their metrics.

For more information, see Using the E2E MAI Support Servlet Program.

Analysis Expert Mode



Check Logs for Configuration Issues

This tool displays the point of entry for which errors have been reported the in the Event Calculation Engine (ECE) logs, in the last 15 Minuten, and repeats the technical monitoring configuration for a selected point of entry, if you choose Execute.

Note Note

A point of entry is the highest hierarchy level of managed objects, such as the technical system for the use case System Monitoring.

End of the note.

As technical monitoring problems often arise because of configuration errors, this tool can resolve errors by reconfiguring.

Metric Store

This tool displays the contents of the metric store. The metric storecontains the values of the metrics in the Directory Browser. The Event Calculation Engine (ECE) uses these values to determine the monitoring status of the managed objects, and generate events.

You can filter the values of the metric repository to be displayed, by the following criteria:

  • Time period (default: the last 5 minutes). The metric repository only contains the values of the last hour, for performance reasons.

  • Technical scenario and managed object

To display the metric repository according to the above criteria, choose Display Data. The metrics for which there are values in the metric repository according to the filter criteria, are sorted by category, and output with the measured values, their timestamp and a message text.

Performance Monitor of Event Calculation

This tool displays the most important Event Calculation Engine (ECE) KPIs during a specified time period, to evaluate the performance of ECE.

MAI Runtime Component Analysis

This tool displays detailed technical monitoring status information of a managed object. Choose the managed objects with Select Managed Object, by specifying the technical scenario type, and setting its Snapshot-Relevant flag. You can now get the following information for the selected managed objects:

  • Choose Gray Metrics and Events, to display the metrics and events which do not have enough values, so that they are displayed gray. A log entry which can help to find errors, is output in the Message Text column.

  • Choose Download Monitoring Data, to output the most important technical monitoring data in an XML file. You can send information required to find and resolve errors, to SAP support. You can also Upload Monitoring Data, but only do so if advised by SAP Support.

You can also go from this tool to the metric repository (see below) or the Directory Browser. If you click on an entry in the list of selected managed objects, the current technical monitoring status in the various categories, for this object, is displayed.

Aggregate Statistics

Use this program to check the following points:

  • Metrics or events with a large number of aggregates; a large number of aggregates is primarily created if the color of the corresponding metric or event frequently changes, that is, if it is flickering between colors. This is disadvantageous, since the aggregates form the basis of the data that is displayed in the Alert Inbox, and this therefore makes working with the Alert Inbox increasingly complex.

  • Metrics or events for which values are no longer delivered.

  • Number and distribution of aggregates to the different monitoring application cases.

For more information, see Using the Aggregate Statistics Program.

Metric Types with High BW Data Volume

Use this program to check which metric types require the greatest data volume in BW for reporting.

For more information, see Display Use of Program Metric Types by Data Volume.

Analyze ASR Dataset in BW

This tool determines for which profiles, granularities, managed systems and dimensions require a lot of memory in BW for ABAP statistics records, and may cause problems due to system load.

For more information, see Check Table Size and Structure of ASR Aggregates.

Analyze BW Mapping Tables

This tool checks the reliability of the data provision for metrics, and the entire mapping mechanism, from the contents of the mapping tables.

For more information, see Using the BW Mapping Tables Analysis Program.

Reorganization of Reporting DSOs

This tool analyzes and reorganizes the data store objects in which the MAI data is buffered in BW on the way to the InfoCubes, i.e. it deletes obsolete data records.

For more information, see Using the Analysis DSO Reorganization Program.

Configuration and Status of the BW Data Queue

This tool checks the storage of MAI data in BW, and makes various configuration settings. Use it if there are data gaps in Interactive reporting or other applications which display the history data in BW.

For more information, see Using the BW Queue Job Configuration and Status Program.

Logs and Traces



Log Viewer

This tool displays entries about MAI in the application log.

E2E_ALERTING is preselected as a valid object so that exactly the desired entries are output.

Trace Viewer

MAI contains comprehensive trace functions, which show the details of the MAI processes. The trace is a high-performance expert tool to trace procedures, analyze performance, and investigate errors.

For further information, see MAI Trace Functions.

Problem Messages in SolMan

Problem Messages in BW

If there are problems in BW-based reporting, you can check them with these reports.

The differences between the two reports are largely historical. When saving and processing reporting data in BW, steps are performed in the software components ST (SAP Solution Manager) and ST_BCO (BI Content for SAP Solution Manager). Depend on whether your BW is in its own system or in the SAP Solution Manager system, as recommended, these steps run in one or two systems, so there are two message display reports.

Use Problem Messages in SolMan to display messages from the SAP Solution Manager system, and Problem Messages in BW to display messages from the associated BW system.

For more information, see Troubleshooting Tools.

Logs and Traces Expert Mode



Search Logs for Message

This tool lists application log entries (transaction SLG1) for the Event Calculation Engine (object E2E_ALERTING, Subobject ENGINE).

In contrast to the application log, you can restrict the log messages to be output, by message numbers in the message class ACE_MESSAGES.

Note Note

To display all messages, call the Message Maintenance (transaction se91), and in the Message Class field, enter ACE_MESSAGES, and choose Display.

End of the note.

This tool is particularly useful when an error occurs in ECE (you have the message number), and you want to know whether it was one-off, or occurs regularly. Enter the message number and a time period, and run the program. All occurrences of this error in the specified period are output.




Global Switch for Management Settings

The basic MAI functions include alerts, messages, notifications and auto-reactions to inform the persons responsible about an underlying problem, immediately, or trigger automatic technical reactions. You can specify how MAI is to react to an alert, globally or at the level of managed objects or metrics, in the SAP Solution Manager configuration (transaction SOLMAN_SETUP).

A lot of messages, notifications and auto-reactions may be created for fundamental problems, depending on the configuration settings, even if the underlying problem has already been handled. In such cases, further notifications about this problem are not helpful, or even harmful.

In such situations, use the function Global Switch for Management Settings. This deactivates notifications, messages and auto-reactions, globally, for the entire SAP Solution Manager, without changing the configuration settings. The function is a main switch, with which you can temporarily deactivate this function during error handling. Proceed as follows:

  1. Start transaction MAI_TOOLS. In the Configuration Tools tab, choose Global Switch for Management Settings.

  2. You specify in the group boxes the current global activation status of the function, separately for Notifications, Messages and Auto-Reactions. To deactivate the function, choose Deactivate in the group box.

  3. Reactivate the functions after resolving the problem, with Activate.

Suspend/Resume Event Calculation Engine

The Event Calculation Engine (ECE) uses the reported metric values to determine the status, events, and alerts of the managed objects, on the basis of configuration settings in the Alerting Directory. In addition to the calculation of events, it permits the correlation and propagation of events. It is therefore the technical core of the MAI.

From a technical point of view, the ECE runs in a job that is executed once a minute in the SAP Solution Manager system. The job runs under the name SAP_ALERT_CALCULATION_ENGINE (if this has not been manually changed) and calls the report ACE_CALCULATION_CONTROLLER. This job should usually have a runtime of less than a minute.

If the runtime of this job is regularly significantly more than a minute, or there are other significant problems within the MAI, it can be useful to temporarily deschedule the job for the ECE while you identify and correct the error. This program exists for this purpose. However, by descheduling the ECE, you deactivate technical monitoring itself. It is therefore only meaningful as a temporary measure for critical performance or other problems to reduce the workload of the system while you identify and correct the error.

Caution Caution

Use this function only in consultation with SAP support.

End of the caution.
  1. Start transaction MAI_TOOLS. In the Configuration Tools tab, choose Suspend/Resume Event Calculation Engine.

  2. To temporarily deschedule the job for the ECE while you solve the problem, choose the Stop Engine button.


  3. Reschedule the job for the ECE when you have solved the problem, by choosing Restart Engine.

System Reporting Configuration

This tool changes the detailed configuration settings for BW-based reporting:

  • You can specify which metrics, from which managed systems, are to be collected for reporting in BW.

  • You can specify the lifetime of all metrics which the system collects in BW, with different lifetimes for different time resolutions.

  • You can output the results of a variety of checks which help you to recognize whether interactive reporting has been set up correctly. The prerequisites that are required for successful setup are checked.

Configuration Expert Mode



Restrict Metrics Written to BW

This tool specifies for which metrics history data is saved in BW. Metrics required by reporting are preselected.

For more information, in Monitoring and Optimization of the Reporting Performance of MAI Data, see the section Reducing the Number of Metrics to be Saved.

Definition Tool

The definition tool creates templates for types of SAP managed objects. These templates contain all metrics, events and alerts. This tool is not for the use of customers

Simulation Expert Mode



Simulate Template Assignment

This tool lists the assigned template metric, event and alert types of a managed object, grouped by monitoring use cases and work mode.

The name, type and ID of the selected managed object are output. The following data is output for each monitoring use case and work mode to which the object is assigned:

  • Name, ID and version of the template which is assigned to the managed object in the monitoring use case

  • Metric, event and alert types of the assigned template, with ID, version and technical name of the type, and the assignment to the SAP product

  • Event hierarchy of the assigned template

Use this tool to determine which templates and metrics, events and alerts are assigned to a managed object by default, to simulate the auto-configuration.

Related Links



Technical Monitoring

This work center contains tools and functions to monitor the SAP Solution Manager landscape.

For more information, see Technical Monitoring Work Center.

Solution Manager Work Center

This link gives you an overview of the SAP Solution Manager work center.

For more information, see Using the Work Center.

Solution Manager Configuration

You use this work center to configure SAP Solution Manager immediately after installation, following an upgrade, or after importing Support Packages. The system leads you through the process using guided procedures, and provides a constant overview of the progress of your configuration.

For more information, see SAP Solution Manager Configuration

SAP Solution Manager Administration

This work center is the central access point for all the information and functions you need to run the SAP Solution Manager.

For more information, see SAP Solution Manager Administration Work Center.

Agent Framework

The agent framework manages diagnostics agents installed in all managed systems, centrally.

For more information, see Agent Framework.

Alerting Framework

You monitor the status of the alerting infrastructure.

For more information, see Alerting Framework.

Data Provider Maintenance

Various collectors get the data of the metrics in MAI. It comprises an implementation, e.g. an ABAP function module or a web service method, and its configuration. You can display the MAI collectors, and edit and create new ones, in the Data Provider Maintenance.

For more detailed information about the tool, see the SAP Community Network under the following link: published on SAP site

Caution Caution

If you use this link, you accept that the contents of this page are not part of the SAP product documentation, and that you cannot derive expectations about the properties of the product from the information in this page.

End of the caution.

Landscape Management Database

The Landscape Management Database (LMDB) of SAP Solution Manager is the central landscape information repository. It uses the same standard (the Common Information Model, CIM) as the System Landscape Directory (SLD), to represent system information.

For more information, see Managing System Landscape Information.

Landscape Browser

The landscape browser displays the attributes and technical details of all elements in your IT landscape.

Self-Diagnosis of Reporting

The reporting self-diagnosis supports you in troubleshooting and administering BW-based reporting. The status of the connections between the SAP Solution Manager system and the associated BW are shown here; you can also see the current staus of BW-based reporting, broken down by the different scenarios.

For more information, see Self-Monitoring of BW-Based Reporting.

Self-Monitoring Overview

The end-to-end monitoring and alerting infrastructure (MAI) allows stable and reliable operation of complex heterogeneous system landscapes. To monitor the correct functioning of the landscape, a large number of metrics and alert types, as well as various views and applications, are available to you, which provide prior warning about possible problems.

For more information, see Self-Monitoring of the Monitoring and Alerting Infrastructure.

System Monitoring Template Maintenance

For every MO type SAP provides templates that contain the definitions or values of metrics, events, and alerts (MEA) of incidents and notifications. Templates delivered by SAP are already meaningfully configured.

Use this tool to create your own template, based on default templates delivered by SAP.

For more information, see Using Templates.