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



This page is still under construction!


1. Alerting on Analytics with Notification Grouping

Initial Siuation

Customer IDES wants to monitor overdue sales orders via Business Process Monitoring. They want to inform the different sales organizations via email in case they have sales orders that are more than a week overdue. For each sales organization the number of overdue sales orders should be measured individually and the email with the alert information should go to a different recepient per Sales Org. Customer IDES has more than 100 sales organization.

Of course they could configure 100 diffenent monitoring objects for overdue sales orders, each for a different sales org. But this would require a huge configuration effort. So instead, they decide to configure the monitoring of overdue sales orders via alerting on Business Process Analytics. This way, they have a minimal configuration effort. As an added bonus, they can also use Business Process Analytics to analze their overdue sales orders.

Configure Alerting on Analytics

1. Create Analytics Object

At first, you configure the Analytics object for overdue sales orders. To do so, go to the Analytics library in your solution/branch and choose the correct system role. Create an analytics object via right mouse click in the elements tab for your library.

You can create an analytics object from the local catalogue or from the cloud catalogue. Regardless of how you create the analytics object, the coding for the respective object needs to be available in ST-A/PI on the managed system and the customizing for the monitor definition needs to have been loaded into the SAP Solution Manager system.

After you have created you Analytics object, select the key figure you want to use and provide the configuration.

In the Analytics object, you will notice that other than for alerting objects you only have two tabs available for configuration. The Analytics object does not generate alerts, but only loads the data into the Analytics cubes in SAP Solution Manager. Consequently, threshold values do not make sense for Analytics objects and cannot be configured here. Since incidents/notifications/3rd party actions etc. are triggered by alerts, their configuration is also not available for Analytics objects.

Instead, what you can configure are so-called group-by criteria. Via these, you decide how you want to be able to group the data in Analytics. Company IDES wants to group by Sales Organization (meaning that they want to get individually measured values per Sales Org), so they have to flag the group-by criteria for the sales organization. Which group-by criteria are available depends on the monitoring function and the respective key figure.

By providing the time for "Overdue since" in days and flagging the group-by for Sales Organization, all sales documents that are overdue for more than 7 days are counted per Sales Org.

In the tab "Data Collection" you have to provide the data collection scheduling. As a first step, you should set the flag for "Data Collection in Background". Usually, Analytics objects collect a lot of data, so the data collection takes some time and should be executed via a background job on the managed system. As a second step, you should consider the data collection period. Since a lot of data might be loaded, it might not be beneficial to the load on the managed system if the data collection runs every 10 minutes. Additionally, if the backlog is considered in days, it does not make sense to run the data collection every 10 minutes. And lastely, you should consider if the key figure provides a delta mode (meaning only new documents in backlog since the last data collection are considered). Otherwise you might count the same documents with each data collection.

Afterwards, save, generate and activate your settings. Now the data collection for the Analytics object is scheduled. Once the data collection has run, you should be able to see you result in the Analytics.

2. Configure Alerting Object for the Analytics Object

Now you configure the alerting on Analytics. You can create this configuration immediately after you have finished the configuration and activation of the Analytics object. You do not need to wait for data to be loaded into Analytics.

The alerting on Analytics object has to be created in a business process context (e.g. for a business process, business process step or interface). In your solution documentation, choose an appropriate business process, business process step or interface. It is important that the managed system matches with that of the Analytics object (e.g. if the Analytics object was configured for system PR1, you have to find a business process step that is also executed on system PR1 to configure your corresponding alerting on Analytics object).

For the general details concerning how to configure an Analytics object, see 4.3. Create Alerting on Analytics. Create your Alerting on Analytics object via "New" → "Operations" → "Alerting on Analytics" in the "Elements" tab of the business process step. The Solution Manager will bring you a proposal for the Analytics objects already configured for the relevant managed system. Choose your Analytics object.

The configuration of the Alerting on Analytics object looks very similar to that of a "normal" Alerting object, however, there are a few differences.
Firstly, you see that only the key figure that was selected for the Analytics object can be selected as well for the Alerting on Analytics object (this may be different in older Solution Manager versions).

(click picture to enlarge)

Secondly, for the key figure only the Sales Org is available as selection criteria, while for the Analytics object there were much more selection criteria available. The data collection for Alerting on Analytics happens on Solution Manager itself, evaluating the data that is already available in the Analytics cubes. This means that selection criteria for Alerting on Analytics are only available for fields that are stored separately in the cubes. These are the group-by fields if they were flagged in the Analytics object. E.g. you could say in the Analytics object that you collect all overdue sales orders into the cubes grouped by sales org, but for the alerting you only want to consider the sales orgs 1000 - 1999. In our example, company IDES wants to alert on all sales orgs, so they do not provide a filter here.

 (click picture to enlarge)

Thirdly, you see that the group-by field for Sales Org, which was flagged for the Analytics object, is also available to be flagged for the Alerting on Analytics object. If you set this flag, you say you want to get measured values for each sales orgs individually. Otherwise, you would only get one measured value (the sum of all values for the inidividual sales orgs).

Fourthly, the data collection for Alerting on Analytics runs every time data for the respective Analytics object has been loaded into the BW. Consequently you cannot configure a data collection period.

Afterwards, generate and activate.

Once the data collection has run, the result in the monitoring application (or in case of alerts in the alert inbox) looks like in the below screen shot.

 (click picture to enlarge)

You can see that you get measured values for each individual sales organization.

If you want to send individual notifications for each sales organization however, you have to remember that notifications can only be sent for alerts, not for metrics. Therefore, you have to change the configuration for the Alerting on Analytics object so that each variant raises an individual alert.

(click picture to enlarge).

Afterwards, save. Generate and Activate.

Now the result in the Alert Inbox looks like this:

 (click picture to enlarge)
Remember that the alert inbox only shows real alerts (yellow or red), so there might be more measured values for sales orgs that are currently rated as green.

Configure Notification Grouping

Now that you have individual alerts per sales org, you can configure the notification grouping so that individual alert emails are sent for each sales org. For this, an infrastructure called the BRF+ is used in the SAP Solution Manager system.

Create Notification Group

Create BRF+ Decission Table

Assign Decission Table to Alerting on Analytics Object



  • No labels