Further issues of this blog

You can find an introduction to Business Process Monitoring in SAP Solution Manager in the Functional
Scope of Business Process Monitoring in SAP Solution Manager
of this blog. There, all further blogs dealing with various aspects of Business Process Monitoring are linked. The blog will be updated regularly.

OCC Alert Reporting Analysis

The Business Process Operations (BPO) functionality within SAP Solution Manager offers the possibility to monitor the availability and reliability of business processes that have been maintained in a solution landscape. BPO offers a wide range of different monitors for different business areas as well as cross application monitors, e.g. IDoc monitoring.

The Application Operations (AO) functionality within SAP Solution Manager offers the possibility to monitor technical aspects of systems, databases, interfaces, jobs etc.

The OCC Alert Reporting Analysis is an additional feature which can be used within BPO and AO. It is based on the Business Warehouse (BW) functionality and the Monitoring Application Infrastructure (MAI)  included in Solution Manager as a SAP NetWeaver 7.1 system and is available as of SP13 – on demand
also as downport via SAP Note for SP12.

It enables you to:
  • Vizualize the number of alerts per alert status[1] for a specific BPO or AO context in graphical charts for a period of time
  • Display the number of red and yellow alerts[2], alert instances and incidents for a specific BPO or AO context split up by rating in graphical charts   for a period of time
  • Display the number of confirmed alerts for a specific BPO or AO context split up by incident creation in graphical charts for a period of time
  • Display the maximum and average duration until alert confirmation for a specific BPO or AO context split up by rating in graphical charts for a period of time
  • Visualize daily and monthly trends in numbers of alert groups, alert instances, incidents, confirmed alerts with and without incidents and maximum duration until alert group confirmation
With OCC Alert Reporting Analysis in SAP Solution Manager 7.1 as of SP13 replaces the functionality of the BPO Alert Reporting Analysis with SAP Solution Manager 7.1 as of SP12 as described in the BPO Alert Reporting Setup Guide.

As the BPO Alert Reporting the OCC Alert Reporting covers the following functionality

  • Accesses the unified MAI storage locations
  • Relies on the unified MAI data transfer
  • Uses the UI5 user interface, enabling mobile access
  • Uses the twincube concept inkl. automated housekeeping
  • Remembers the selection criteria recently used for the cube acesses

Additionally to the BPO Alert Reporting the OCC Alert reporting

  • Combines the display of BPO and AO Alerts in one application
  • Simplifies the data selection by providing the filter criteria in dynamic dropdown fields (theese replace the BPO context selection in the entry screen)
  • Has an enhanced default analysis scope
  • Enables drill up and down to Alert Name (AO only) and System
  • Enables optional data enrichment
  • Enables to handover selection criteria by enhancing the link with parameters
  • Enables printing of the main charts

The data accesses are realized technically as RFC queries (The queries are not related to BI Content)  working on the collected and stored data in the BW. They are called by oData services within an UI5 dashboard which can be accessed directly following an URL in a web browser.

The OCC Alert Reporting dashboard graphics allows tracking

  • BPO and AO alerts (see Figure 1)
  • The overal number of alerts per status[1] (see Figure 2)
  • The overal number of confirmed alerts with or without incident and split up by alert name(AO only), managed object and system (see Figure 3      and Figure 9)
  • The number of red and yellow alerts, instances and incidents drilled down by alert name(AO only), managed object and system (see Figure 4, Figure 5   and Figure 6)
  • The maximum and average duration in minutes, until red and yellow rated alerts have been confirmed, alert name(AO only), managed object and system (see Figure 7 and Figure 8)
  • The daily and monthly trend of alert, instance and incident numbers for any alert name and managed object combination (see Figure 10)
  • The daily and monthly trend for the maximum and average duration until alert group confirmation for any alert name and managed object      combination
  • The daily and montly trend for the confirmed alerts with or without incidents for any alert name and managed object combination (see Figure 11)

/wp-content/uploads/2015/01/figure1_617898.jpg

Figure 1 – Switch the views for tracking BPO and AO Alerts

/wp-content/uploads/2015/01/figure2_617899.jpg

Figure 2 – Number of Alerts per Status

/wp-content/uploads/2015/01/figure3_617900.jpg

Figure 3 – Number of Confirmed Alerts with or without Incident

/wp-content/uploads/2015/01/figure4_617901.jpg

Figure 4 – Number of Alerts per Managed Object and System

/wp-content/uploads/2015/01/figure5_617902.jpg

Figure 5 – Number of Alert Instances per Managed Object and System with Show Numbers

/wp-content/uploads/2015/01/figure6_617903.jpg

Figure 6 – Number of Alerts with Incidents per Managed Object and System with Monitor

/wp-content/uploads/2015/01/figure7_617904.jpg

Figure 7 – Maximum Number of Minutes from Alert Creation to Confirmation per Alert Name, Managed Object and System

/wp-content/uploads/2015/01/figure8_617905.jpg

Figure 8 – Average Number of Minutes from Alert Creation to Confirmation per Alert Name and Managed Object

/wp-content/uploads/2015/01/figure9_617910.jpg

Figure 9 – Number of Confirmed Alerts with or without Incidents per Managed Object

/wp-content/uploads/2015/01/figure10_617911.jpg

Figure 10 – Number of Red and Yellow Alerts with Incidents over Time for a specific Managed Object and Alert Name Combination

/wp-content/uploads/2015/01/figure11_617918.jpg

Figure 11 – Number of Confirmed Alerts with or without Incidents over Time for a specific Managed Object and Alert Name Combination

The runtime of the oData routines are influenced by the accessed data volume in BW and the amount of data loaded to and processed in the frontend (see Figure 12 and Figure 13). Therefore it is recommended to use as restrictive selection criteria as possible by choosing
  • A smaller timeframe[3] and
  • For the BPO Alert Reporting view: The BPO context for a specific BPO Solution[4] in SAP Solution Manager
  • For the AO Alert Reporting view: The managed object type and the alert category

The data analysis is done based on Managed Object level. A drilldown to alert name (AO only) and system is possible. On the detailed view a drill down to days and months is possible.

/wp-content/uploads/2015/01/figure12_617919.jpg

Figure 12 – AO Selection Criteria Influencing the Data Amount Read and Processed

/wp-content/uploads/2015/01/figure13_617920.jpg

Figure 13 – BPO Selection Criteria Influencing the Data Amount Read and Processed

The displayed OCC Alert Reporting Analysis can be filtered regarding (see Figure 14 and Figure 15)

  • Managed Object (also string parts)
  • System
  • Monitor (BPO)
  • Alert Name (AO)

/wp-content/uploads/2015/01/figure14_617921.jpg

Figure 14 – BPO Sub Selection on the Loaded Frontend Data

/wp-content/uploads/2015/01/figure15_617922.jpg

Figure 15 – AO Sub Selection on the Loaded Frontend Data

Further Documentation and Setup Guide

A Setup Guide for the OCC Alert Reporting Analysis is available in the Business Process Monitoring – Solution Manager – SCN Wiki under –> Media Library –> Technical Information –> BPMon on MAI or directly here.

The Setup Guide is based on the current release which was shipped end of 2014.



[1] As up to SAP Solution Manager 7.1 SP13 the current alert status is
not loaded to the cube, the alert status is derived from the availability of a
processing and confirmation user.

[2] As known from the Alert Inbox the expression “Alert” in OCC Alert
Reporting is used equivalent with “Alert Group”, meaning a group of alert
instances or events (refering to the classical BPMon Alerts) not changing the
rating within a certain time frame.

[3] According to the twin cube concept, the data are stored as daily
and monthly records. According to the default housekeeping settings in the
SOLMAN_SETUP the daily records are kept at least 90 days. That is why the OCC
Alert Reporting switches to monthly display with horizons larger than this
setting.

[4] All BPO solutions migrated to MAI are shown, for which the useris
authorized. The recently selected solution is saved as a user-specific setting
and reloaded, when the user is calling the OCC Alert Reporting again.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply