Alert Reporting Analysis with SAP Solution Manager 7.1 SP05+

Business Process

Monitoring - Alert

Reporting Analysis

with SAP Solution

Manager 7.1 SP05+

February 2014

BPM Alert Reporting Analysis - Setup and User Guideline

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and

SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®,

MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,

Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM

are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of

the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,

WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

J2EE™ is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business

Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, and other SAP products

and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. MarketSet and Enterprise

Buyer are jointly owned trademarks of SAP Markets and Commerce

One. All other product and service names mentioned are the

trademarks of their respective owners.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address: http://service.sap.com//bpm

SAP AG

Dietmar-Hopp-Allee 16 D-69190 Walldorf, Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

BPMon Alert Reporting Analysis with SAP Solution Manager 7.1 SP05+

February 2014 3

TABLE OF CONTENTS

1 INTRODUCTION ........................................................................................................................................ 5

2 SETUP ........................................................................................................................................................ 9

2.1 Prerequisites .......................................................................................................................................... 9

2.1.1 SAP Solution Manager System Release ..................................................................................... 9

2.1.2 BW components already activated .............................................................................................. 9

2.1.3 Solution Manager Configuration: Configuration User and RFC Connection ........................ 10

2.1.4 Further Important SAP Notes ..................................................................................................... 10

2.2 Activation ............................................................................................................................................. 11

2.2.1 Automatic BPMon Alert Reporting Setup Guidance ................................................................ 11

2.2.2 BPMon Customizing Settings .................................................................................................... 14

2.2.3 Adding of additional BPMon solutions to BPMon Alert Reporting ........................................ 16

2.3 Execution of BPMon Alert Reporting ................................................................................................ 17

2.3.1 Technical View ............................................................................................................................. 17

2.3.2 Work-Center-integrated View ..................................................................................................... 20

2.3.3 View the Alert Data in BPO Dashboards ................................................................................... 23

2.4 Monitor the Data Transfer ................................................................................................................... 25

2.5 Housekeeping ...................................................................................................................................... 27

2.6 Adapt Customer Queries when using Multiple Alert Assignment ................................................. 28

3 TROUBLESHOOTING ............................................................................................................................. 30

3.1 Problems during activation process in SolMan Setup .................................................................... 30

3.1.1 The activation displays red messages ...................................................................................... 30

3.1.2 Has the latest BI content been activated? ................................................................................ 32

3.1.3 Errors during Activation of Objects with Type Info Object ..................................................... 33

3.2 Problems after the activation ............................................................................................................. 36

3.2.1 No data are shown in my dashboard ......................................................................................... 36

3.2.2 Are the extractors really active? ................................................................................................ 36

3.2.3 The dashboard graphics do not look like in the screens above ............................................ 36

3.2.4 The extractor DSWP_BPM_ALERT_REPORTING_EXTR stops with “Illegal Input” ............. 36

3.2.5 Message ‘Chart “CHART_*”. Data Provider does not contain any data’ is shown............... 38

3.2.6 The web template does not display the recently transferred cube data ............................... 39

3.2.7 The extractors DSWP_BPM_ALERT_REPORTING_* are in status red .................................. 40

3.2.8 You expect more than 10000 alerts per run .............................................................................. 41

3.2.9 No data transferred to BW although too alerts are to be transferred .................................... 42

3.2.10 The value helps in the selection screen do not display any or valid data ............................ 43

BPMon Alert Reporting Analysis with SAP Solution Manager 7.1SP05+

4 February 2014

3.2.11 In BW only capital letters are stored ......................................................................................... 44

3.2.12 The alert confirmation timestamp and user are not transferred ............................................ 44

3.2.13 In the Solution Value Help the Keys are visible without Descriptions................................... 44

3.2.14 Extractor complains that the Cube 0SM_BPM1 or 0SM_BPM1 is no real-time Cube ........... 45


February 2014 5

1 Introduction

The Business Process Monitoring (BPMon) 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. BPMon offers a wide range of different monitors for different business areas as well as cross application monitors, e.g. IDoc monitoring.

The Alert Reporting Analysis is an additional feature which can be used within BPMon. It is based on the Business Warehouse (BW) functionality included in Solution Manager as a SAP NetWeaver 7.1 system and is available as of SP05. It enables you to:

Store measured values and alerts for a long-term availability

Display measured values and alerts in graphical charts for a period of time to visualize a trend

Analyze measured values and alerts furthermore using Business Intelligence tools.

The main functionality is available with SAP Solution Manager 7.1 SP05. For a better look and feel we recommend to use SAP Solution Manager 7.1 SP07.

With BPMon Alert Reporting Analysis in SAP Solution Manager 7.1 the functionality of the Trend Analysis Reporting with SAP Solution Manager 7.0, as described in the BW Setup Guide for “Trend Analysis Reporting with SAP Solution Manager”,

Is simplified in the setup procedure

Stabilizes the filling of the BPMon alert cube 0SM_BPM (instead of the sensitive job chain you have a stable extractor report)

Uses the same data transfer framework as BPMon Analytics

Has an enhanced default analysis scope

Checks for illegal characters

The dashboards are designed technically as queries, working on the collected and stored data in the BW. They are included in a web template which can be accessed directly following a URL in a web browser.

The BPMon Alert Reporting dashboard graphics allows tracking

the maximum measured values1 (see Figure 1)

the maximum time to confirm critical alerts2 (see Figure 2)

the number of critical alerts3 (see Figure 3)

1 For reporting on measured values use in SP05 and SP06 the old web template 0SM_BPM_WT0001.

Please note that if you have referenced several steps to a monitoring object, than filtering for process and step is not possible. From SP07 filtering on process and step will be possible, even if you have referenced several steps to a monitoring object. For reporting on measured values from SP07 use new web template 0SM_BPM_WT0001N.

2 For reporting on time needed for alert confirmation use new web template 0SM_BPM_WT0001N. Please

note that from SP07 filtering on process and step will be possible.

3 For reporting on number of alerts use new web template 0SM_BPM_WT0001N. Please note that from

SP07 filtering on process and step will be possible.

http://service.sap.com/~sapdownload/011000358700000300302009E/BI_SetupGuide.pdf

http://service.sap.com/~sapdownload/011000358700000300302009E/BI_SetupGuide.pdf


6 February 2014

The analysis is done for a certain timeframe, a specified solution in SAP Solution Manager and optionally a specific alert type (see Figure 4).

A drill down from day to hour is possible. The displayed Alert Reporting Analysis trends can be filtered regarding:

Monitoring Type

Monitoring Object

Alert Type (Key Figure)

With SP05 a major change in BPMon data model in SAP Solution Manager Release 7.1 allows one monitoring object to be assigned to several business process steps. Therefore an alert might not always be uniquely related to a business process or a business process step. As in the cube only one of those assignments can be stored, you should make sure that each monitoring object is assigned to one business process step only. That guarantees correct results when using the process and step selection functions in the old web template 0SM_BPM_WT0001.

With SP07 the new web template 0SM_BPM_WT0001N has been enhanced so that business process and step can be selected for multiple assignments, too (see Figure 5).

Figure 1 - Maximum Measured Values over Time with Web Template 0SM_BPM_WT0001N


February 2014 7

Figure 2 - Maximum Time from Alert Creation to Confirmation over Time

Figure 3 - Number of red and yellow Alerts created over Time

Figure 4 - Selection Criteria of the new web template (SP05 and SP06)


8 February 2014

Figure 5 - Selection Criteria (SP7+)


February 2014 9

2 Setup

In order to use the BPMon Alert Reporting Analysis Reporting, a productive BPMon solution should already be available in SAP Solution Manager so that the monitoring data extraction and analysis can be performed.

4 It is strongly recommended to configure, generate and activate BPMon in a solution before going

on with the activation process as described in the subsequent chapters.

DISCLAIMER:

Please use this Setup-Guide for Alert Reporting Analysis for Business Process Monitoring at your own risk. All our recommendations regarding the activation of this functionality are based on our general experience and maybe are not valid for your specific implementation, especially when you are already using the BW component in SAP Solution Manager. In this case, please consult and involve the people already working with BW in the target system to make sure that all functions in BW keep working.

2.1 Prerequisites

2.1.1 SAP Solution Manager System Release

Using the Alert Reporting Analysis feature of BW, implementing the current releases and support packages for the ST, ST-SER and ST-BCO components is mandatory. We recommend the following releases as an absolute minimum configuration:

Software Component Release Level

ST SAP Solution Manager 710 005

ST-SER SAP Solution Manager Service Tools 701_2010_1 0013

ST-BCO BI Content for SAP Solution Manager 710 0003

2.1.2 BW components already activated

Before setting up BPMon Alert Reporting feature, you need to find out if Business Warehouse (BW) in your SAP Solution Manager is already being used.

This can be checked in table “RSADMINA” on your SAP Solution Manager system, which can be accessed by transaction SE16 directly. If the table is empty, no usage of BW components was activated before and the client for BW usage can be chosen freely.

If an entry already exists, a BW client was already set before. You have to use the client defined in column “BWMANDT” for all further setup activities. Otherwise, inconsistencies in the BW part might occur later on during activation process.

If no entry exits, choose the BW client. Which client to choose, depends on your authorization concept for the clients in your SAP Solution Manager system. We recommend using the SAP Solution Manager client (already in use for BPMon) for BW activation and to use SolMan Setup (i.e. the automated Solution Manager Configuration tool) for the activation process.

4 More information on how to setup BPMon can be found in the Setup Guide available in

http://service.sap.com/bpm Media Library Technical Information Setup Guide - Business Process Monitoring. Make sure that you generated and activated your monitoring configuration.


10 February 2014

2.1.3 Solution Manager Configuration: Configuration User and RFC Connection

During the BPMon setup („System Preparation“ and „Basic Configuration“ and „Managed System Configuration“ see Figure 6) a configuration user is created automatically. The system assigns roles and authorizations to this setup user automatically for

Performing the Technical Setup of BPMon Alert Reporting

Performing BW reporting (data analysis, display trend analysis and alerting)

Displaying Dashboards

Alternatively, you can also use the Solution Manager Administrator user (for example SOLMAN_ADMIN).

Figure 6 - Solution Manager Configuration

To enable the data transfer from SAP Solution Manager to BW an RFC Connection is required, which is also part of the automatic Solution Manager Configuration.

Find more information on the automatic user creation concept in the Security Guide in section 8.2.

Read as well the details about the authorizations and RFC connections for Business Process Operations functionalities in the Security Guide in chapter 25.

2.1.4 Further Important SAP Notes

We recommend implementing the following SAP Notes to get True Type Fonts in the graphical charts and a more clear display of the coordination axis in the trend chart:

SAP Note 1028690: “True Type Fonts delivered with IGS”

The recommendation in this SAP Notes needs to be implemented if you predict that a font different than the IGS standard font (with limited options) will be used.

SAP Note 596825: “GFWCHART configuration file”

service.sap.com/~sapidb/011000358700000482312011E/SM7_SECURITY_SP05.pdf


February 2014 11

This SAP Note provides a solution for issues related to fonts in the IGS graphic charts and the layout of the coordination axis.

After implementation of these SAP notes, the application server has to be restarted.

We recommend implementing the following SAP Notes to get the latest updates of BPMon Alert Reporting and its assigned functions:

SAP Note 1796563: “BPMon Alert Reporting TD - Solman 7.1 Corrections”

2.2 Activation The following chapters describe the activation process of the BPMon Alert Reporting functionality via the solution manager setup functionality. If any problems arise during activation, please refer to chapter 3 Troubleshooting of this document.

2.2.1 Automatic BPMon Alert Reporting Setup Guidance

To access the automatic activation of BPMon Alert Reporting, call transaction SOLMAN_SETUP and find on

the left hand side the button to setup “Business Process Monitoring” (see Figure 7).

Follow the step by step configuration tabstrip (see Figure 8). The automatic activation of BPMon Alert

Reporting can be triggered on tab 1.1 “Configure automatically” with the automatic activity “Load Alert Data

to BW Cube”. To do this select the line, change to the edit mode, make sure that the execution status is set

to “Execute” and hit the button “Execute Selected” (see Figure 9).

The activation takes a few minutes, as it contains the following steps:

Deletion of currently scheduled Jobs RDSWP_BI_BPM_EXTRACT, which might had been used to

transfer the alerts for the former BPMon Trend Analysis reporting

Activation of the relevant BI content, which is basically the Info Cube 0SM_BPM, the web template

0SM_BPM_WT0001N and the assigned queries

Changing Info Cube 0SM_BPM to real-time mode

Deletion of the job chains, which might have been used to transfer the alerts for the former BPMon

Trend Analysis reporting

Registration and activation of the BPMon Alert Reporting Extractors at the extractor framework.

Cleaning up of the transfer table DSWP_BPM_BI_EXTN, which might have been used to transfer the

alerts for the former BPMon Trend Analysis reporting and which is now used in a changed manner.

Hit the button refresh and review the log entries. After a successful activation of BPMon Alert Reporting, the

log should display no red messages. As the log tells you with a yellow message the last, but optional step is

to delete the DSO and PSA assigned to Info Cube 0SM_BPM via transaction RSA1. These BW data

structures do not harm the BPMon Alert Reporting function, but are no longer needed, as they might have

been used for the former BPMon Trend Analysis reporting.

In case of red messages, please refer to chapter 3 Troubleshooting of this document.

If the extractor framework is running all BPMon Alerts, which have been created with the customizing setting

“Keep Data for BI” are transferred to BW Cube and can be analyzed (see chapter 2.2.2 BPMon Customizing

Settings).


12 February 2014

Figure 7 - The SOLMAN_SETUP screen


February 2014 13

Figure 8 - Automatic Configuration

Figure 9 - Automatic activation of BPMon Alert Reporting


14 February 2014

Figure 10 - Successful Log

2.2.2 BPMon Customizing Settings

If you are using SAP Solution Manager 7.1 SP05 (and higher), please make sure that for each monitoring object a parameter set is assigned where the flag “Keep Data for BW” is set, otherwise the alert data are not transferred to BW.

In order to check or maintain these setting, go via the Business Process Operations work center to the “Setup Business Process Monitoring” (see Figure 12), select your solution and there go to “Cross Functions” and then click on “Alert Parameter Sets”.

“Keep Data for BW” is set per parameter set (in the last column you can see to which objects the parameter set is assigned to).

Figure 11 - The flag “Keep Data for BW” in the BPMon Setup


February 2014 15

Figure 12 - Access the BPMon Settings via the Work Center "Business Process Operations"

Alternatively you can access the alert parameter sets via the settings of Business Process Monitoring in the Solution Manager Work Center “Business Process Operations”. Click on “Setup Business Process Monitoring” (see Figure 12). In the context navigation choose the business scenario, business process and step and select the monitoring object you want to transfer the alerts for (see Figure 13).

The flag “Keep Data for BW” can be found at the tab “Alert Reorganization and Others” (see Figure 14). If this flag is set, the alerts of this monitoring object will be taken into account for the transfer to BW.

Save the settings, before you leave the screen.


16 February 2014

Figure 13 - Business Process Monitoring Setup

Figure 14 - Edit Monitoring Object Settings

2.2.3 Adding of additional BPMon solutions to BPMon Alert Reporting

Further solutions can easily be added to the BPMon Alert Reporting Analysis as long as they are active for BPMon and “Keep data for BW” is set.

Make sure that you generate and activate the monitoring object once again, if you have changed the settings of the assigned alert parameter set.

Then the new solutions and monitoring objects are automatically considered in the BPMon alerts data transfer.


February 2014 17

2.3 Execution of BPMon Alert Reporting

Depending on the Support Package level of your system, please choose the appropriate web template(s) that fit to your purposes

5.

Support Package

Web Template Measured Value Trend

Number of Critical Alerts

Max. Confirmation Time

BPStep Selection

SP05 + SP06 0SM_BPM_WT0001 Yes No No Yes (Single)

SP05 + SP06 0SM_BPM_WT0001N Yes Yes Yes No

SP07+ 0SM_BPM_WT0001N Yes Yes Yes Yes (Multiple)

For SP05 and SP06 SAP recommends to use both the old and the new web template in order to have the benefit of viewing the measured value trend per business process step

6.

For simplification we show in the following part the access of web template 0SM_BPM_WT0001N. Of cause the old web template can be accessed in the same way.

To access a web template there are two different ways. One is the more technical and easy view, which might be used for testing purposes. SAP recommends using the access via the Work Center “Business Process Operations”, which is described in section 2.3.2.

2.3.1 Technical View

The technical view is an easy way to display the web template from SAP support, e.g. because it does not require any HTTP connection to the customer.

A web template can be accessed in the BW client via transaction “SE38” using report “RS_TEMPLATE_MAINTAIN” (see Figure 15 and Figure 16).

Afterwards, the HTML coding of the web template is displayed.

There are two possible ways of displaying the BPMon Alert Reporting Analysis dashboard: directly via SAP GUI or in a web browser. By selecting ‘Execute’ (F8) the BPMon Alert Reporting Analysis GUI is displayed, by selecting ‘Preview in Browser’ (F9) the Alert Reporting Analysis is displayed in a browser window. The URL displayed there can be used for direct access to the dashboard later on (see Figure 17).

After this selection, you enter the Alert Reporting form where the name of the solution, the trending time period and the alert type can be selected. After pressing button “Execute” (see Figure 18), the Alert Reporting Analysis is visible on the screen.

5 In order to display and evaluate data, which have been transferred before Solution Manger 7.1 SP05,

please use web template 0SM_BPM_WT0001.

6 Please note that if you have referenced several steps to a monitoring object, than filtering for process and

step is not possible.


18 February 2014

Selection options for the BPMon Alert Reporting Analysis dashboard are monitoring type, monitoring object and alert type (see Figure 19).

Figure 15 - Executing the Web Template with Report RS_TEMPLATE_MAINTAIN in SE38

Figure 16 - Execute Web Template 0SM_BPM_WT0001N


February 2014 19

Figure 17 - Web Template 0SM_BPM_WT0001N

Figure 18 – Variable Selection for the BPMon Alert Reporting Dashboard


20 February 2014

Figure 19 - BPMon Alert Reporting Analysis Dashboard

2.3.2 Work-Center-integrated View

For end-users it is recommended to use the access of the web template via the Work Center “Business Process Operations”. Initially create a report entry which can be reused, without thinking about any technical details. It is also possible to preselect query variables, so that the user does not even need to click the execute button as shown in Figure 18.

To view a report entry, enter SOLMAN_WORKCENTER. Click on tab “Business Process Operations” and click the appropriate report in the area “Reports” (see Figure 20).

Initially the list of reports is empty. If so, customize the report entry according to the end-users needs once.

Hit button “Add”.

Enter in the popup in tab “Basic Information” as Template ID the name of the web template 0SM_BPM_WT0001N.

The field “Server” (<host name>:<port>) can be found in transaction SMICM.

o Choose from the menu “Goto” “Services”. View the details of the HTTP or HTTPS port. In the following screen you can find the host name and the port number of that system (see Figure 22).

o If single-sign-on and the https port are used, activate also the flag “Https”. Otherwise an authentication is required before the report is displayed.

By default “Server Type” is ABAP Server. Choose a description which fits best to describe the report.


February 2014 21

Figure 20 - Work-center-integrated view of the web template

Figure 21 - Add a new report in the BPO Work Center


22 February 2014

If you predefine variables, it might be helpful to name the description according to the default values.

On tab “Variables” you might predefine default values for the selection (see Figure 23). Make sure that the Parameter IDs are named as used in the queries assigned to the web template. Find the names of all variables used in the web template 0SM_BPM_WT0001N in the following list.

Variable Parameter ID

BPMon Solution 0SMD_VSOLU Single Value

Business Process 0SMDV_POBJI Single Value

Business Process Step 0SMDV_SOBJI Single Value

Calendar Week 0SM_RANG Interval

If you want to show always the last 4 days or the current and the previous week, you might modify the query (or copy the standard query and create do the modification in your own query) with SAP Exit variables

7,

which do not need a user input.

To identify the key values, which have to be entered in the fields “Low” and “High” of the variable execute the report once and select the value help for the variable (see Figure 24 and Figure 25).

If you entered for all variables predefined key values (see Figure 23), the variables screen will not be shown anymore before the report is displayed.

7 For example the variable 0SMD_2T of 0CALDAY shows the last two days. If you add another entry of this

variable with offset -2, you will get the last 4 days and so on.


February 2014 23

Figure 23 - Optionally predefine default values for the web template variables

Figure 24 - Variables screen of the web template

Figure 25 - View the F4-help to identify the key of the default values

2.3.3 View the Alert Data in BPO Dashboards

If BPMon Alert Reporting is setup correctly, the Infocube data can be displayed also via the BPO dashboards.


24 February 2014

As prerequisite the latest developments shall be installed with SAP Note 1806818 (For all support packages earlier than SP8 you need to install SAP Note 1752657 before).

The BPO Dashboards are setup in the BPO Workcenter (SOLMAN_WORKCENTER Business Process Operations) via the common task “Manage BPO Dashboards”.

Make sure that the Analytical Key Figure (AKF) Repository is up-to-date. If you have assigned an Analytical Key Figure Instance to a Panel and the Panel to a dashboard, you can view your dashboards via the common task “Display My BPO Dashboards”.

A detailed description of the BPO Dashboard functionality can be found in a separate document.


February 2014 25

2.4 Monitor the Data Transfer The BPMon alert transfer to BW is performed via the Extractor Framework (EFWK). General information, how the EFWK is working can be found in the documentation of Solution Manager – Extraction Framework.

For BPMon Alert Reporting there are two extractors, which can be monitored within the transaction SOLMAN_SETUP Solution Manager Administration (see Figure 26). In the Solution Manager Administration window select “Infrastructure” (see Figure 27).

Figure 26 - Solution Manager Configuration entry screen

https://wiki.wdf.sap.corp/display/LMAGENT/SAP+Solution+Manager+-+Extraction+Framework


26 February 2014

Figure 27 - Maintain Solution Manager Infrastructure

In the menu select Framework Extractor Framework (see Figure 28). To find the BPMon Alert Reporting Extractors, show in the extractor overview table the filter line and enter in column Name “*alert reporting*”. “BPMon Alert Reporting Master Data Load” (DSWP_BPM_ALERT_REPORTING_MDL) and “BPMon Alert Reporting Extractor (TD)” (DSWP_BPM_ALERT_REPORTING_EXTR) shall be green. If not, select the extractor and view the messages per extractor run and find out in which extractor phase the error occurred (see Figure 29).

Figure 28 - Status of Extractors


February 2014 27

Figure 29 - View the status of the BPMon Alert Reporting Extractors

2.5 Housekeeping

Please apply the housekeeping on BW Cube 0SM_BPM from the BPMon Analytics Cube 0SM_BPMRH as described in SAP Note 1514022.

Please make sure that the extractor for 0SM_BPM1 does not run too often. If you do not create any new data objects the extractor does not need to run at all and can be switched on if needed.

To archive the data of the cube 0SM_BPM1, you should do the following:

1) Call transaction RSA1.

2) Select the cube 0SM_BPM1.

3) Switch the cube to “Real-Time Data Can Be Loaded With Data…” with a right-click on the cube “Change Real-Time Load Behaviour …”

4) Delete all requests, which you do not need anymore.

- Right-click on the cube and select “Manage”.


28 February 2014

- Select those requests which shall be deleted and hit the button “Delete”.

5) Switch the cube back to “Read-Time Data Target Can Be Planned …” .

2.6 Adapt Customer Queries when using Multiple Alert Assignment

As described in the introduction section a major change in BPMon data model in SAP Solution Manager Release 7.1 allows one monitoring object to be assigned to several business process steps. If you make use of this feature, please adapt your own queries as described. Note that the required pre-query is available as of SP07.

Similar as in the predefined SAP Queries of the web template 0SM_BPM_WT0001N (see Figure 30), e.g. query 0SM_BPM_Q0001N, remove all characteristic restrictions regarding solution (0SM_SOLUT), business process (0SM_POBJN) and business process step (0SM_SOBJN) and use instead the variable Monitoring ID (0SMD_MIDPRE) as absolute filter restriction for you characteristic Monitoring Object (0SM_MONID).

Figure 30: Usage of the pre-query to enable access to alerts with multiple assignments

When executing the query in the selection screen an obligatory field for the solution and optional fields for the business process and the step will be displayed (see Figure 31).


February 2014 29

Figure 31: Selection fields added by variable 0SMD_MIDPRE for multiple alert assignments selection

These variables are filled from Infocube 0SM_BPM1 by the standard extractor DSWP_BPM_ALERT_REPORTING_HIER. The description texts of solution, process and step are filled by the extractor DSWP_BPM_ALERT_REPORTING_MD (see Figure 29). These extractors are part of the standard alert reporting functionality and are scheduled automatically after the alert reporting setup has been executed.


30 February 2014

3 Troubleshooting When activating or working with the BPMon Alert Reporting Analysis, you could sometimes face technical issues for which we want provide you – according to our experience – a short description how to handle and solve it.

If you face technical issues which are not included in this chapter, please feel free to create an OSS message on component SV-SMG-MON-BPM, providing a detailed description of your issue.

NOTE: To speed up message processing make sure beforehand that you have installed the latest fixes contained in the latest version of SAP Note 1796563 and SAP Note 1852509.

3.1 Problems during activation process in SolMan Setup

3.1.1 The activation displays red messages

The error messages are generated in a certain sequence. Some activation activities are not performed, as long as other activities fail.

The activation activities are performed in the sequence as described in section 2.2.1. Therefore you should in case of errors check the messages from top to bottom. It might be that the activation is running smoothly, after you have corrected the problem mentioned in the first error message.

Find as follows most of the error messages that could occur during the activation:

3.1.1.1 Error deleting job <jobname> (<jobcount>)

The system tries to de-schedule the ABAP program RDSWP_BI_BPM_EXTRACT, but had a problem to delete it. This job is no longer used and needed. The coding changed for SAP Solution Manager SP5 and higher releases in a way that the job does not transfer the alert data anymore.

Consequently it makes no sense to have this job still scheduled in the system.

3.1.1.2 Job <jobname> (<jobcount>) needs to be deleted.

If the activation has already been performed successfully, the ABAP program RDSWP_BI_BPM_EXTRACT has been de-scheduled. It might happen that someone re-scheduled it afterwards. That is why the message tells you to delete the scheduling once again. The activation routine does not remove the job once again, as there is no harm to run the program again (see also section 3.1.1.1).

3.1.1.3 Several messages regarding the RFC destination

According to the contents of the message, you might check the RFC connection or the authorizations once again.

3.1.1.4 Migration canceled, because development system involved.

It is not allowed to run BPMon Alert Reporting in a development system. Make sure that you activate BPMon Alert Reporting in Test or Productive systems only.

3.1.1.5 Migration to the new BPMon Alert Reporting incomplete. Please do not use the old BW re-

porting anymore.

As described in section 3.1.1 the activation is performed sequentially. If the activation is running into an error situation right in the beginning, alerts can be still transferred via the old BW Trend Analysis method. But from a certain point of progression this process can no longer be used. Therefore make sure that you solve the error situations and complete the activation as soon as you see this message.


February 2014 31

3.1.1.6 Migration to the new BPMon Alert Reporting has not been started, yet.

The old BW Trend Analysis still can be used. No data structures have been changed as the activation of BPMon Alert Reporting did not or was not able to start, yet.

3.1.1.7 Info Cube 0SM_BPM is no real-time cube.

The Extractor Framework requires the usage of real-time cubes. Otherwise no data can be transferred. It might happen that the activation did not change the cube 0SM_BPM to a real-time cube.

Check


2) Click on Info Provider in Section Modeling.

3) View the Info Cube “Business Process Monitoring Data” with the technical name 0SM_BPM for Info Area “SAP Solution Manager – Business Process Monitoring” and find out whether it is real-time (Column Object Information contains an icon showing a pencil writing on a notepaper).

How to solve

1) Do the activation in SOLMAN_SETUP a second time and check again.

2) If this does not help, implement SAP note 1727089 and perform the activation in SOLMAN_SETUP a second time.

Reason

In some cases the activation of BI Content retransfers the cube again into a normal cube, although the activation routine just changed the status to real-time and the status shall be kept in general. If you run the activation routine once again, the system does not refresh the BI Content once again, as it had done it right away, and transforms the cube to real-time mode again.

If this does not help, the note is changing the sequence of the BI Content load and the cube transformation to real-time mode. After implementation the cube shall stay with real-time property and the activation needs to be done only once.

Note: If the extractor complains about a non-real-time cube, although it is displayed with the real-time cube icon and the activation routine finished successfully, proceed with section 3.2.14.

3.1.1.8 Error when closing, performing or creating job ‘Conversion of ic 0SM_BPM to rtc’ number

xxxxxx (sy-subrc = yy)

This job (ABAP program SAP_CONVERT_NORMAL_TRANS) is scheduled in background in order to make the Info Cube a real-time cube. Please consider the information given in section 3.1.1.7.


32 February 2014

3.1.1.9 Error when deleting job chain 0SM_BPM_DELTA_P02 or 0SM_BPM_INIT_P01

The BW job chains are no longer necessary and should not be used anymore, as the BPMon Alert data are now filled via the EFWK. Therefore they should be deleted. Usually the activation routine deletes these jobs itself. It might be that there is an error, e.g. if the user does not have enough authorizations.

3.1.1.10 Job chain 0SM_BPM_DELTA_P02 and/or 0SM_BPM_INIT_P01 still exists.

With BPMon Alert Reporting these BW job Chains are no longer needed and prohibited to be used. Please refer to section 3.1.1.9.

3.1.1.11 DSO and PSA are superfluous. Feel free to delete them manually.

As the BPMon alert data are no longer loaded via these BW structures, they are of no use and can be deleted. If you do not delete them, there is no risk as long as the Info Cube is in real-time mode, because a real-time cube cannot be filled by those data structures.

3.1.1.12 Extractors DSWP_BPM_ALERT_REPORTING_EXTR, DSWP_BPM_ALERT_REPORTIN

G_MD and DSWP_BPM_ALERT_REPORTING_HIER have not been activated, yet.

Check

1) Call transaction SE16.

2) Enter table E2E_ACTIVE_WLI and hit Execute (F8).

3) Enter in the field EXTRACTOR the value DSWP_BPM_ALERT_REPORTING_EXTR.

4) Hit the “Number of Entries” button.

If no entry exists, check if section 3.1.1.13 is the reason.

How to solve

Make sure that at least SAP Solution Manager SP05 has been installed completely.

3.1.1.13 No Extractor Templates found for DSWP_BPM_ALERT_REPORTING_EXTR, DSWP_BP

M_ALERT_REPORTING_MD and DSWP_BPM_ALERT_REPORTING_HIER

Check


6) Enter table E2E_TEMPLEXTR and hit Execute (F8).

7) Enter in the field EXTRACTOR the value DSWP_BPM_ALERT_REPORTING_EXTR.

8) Hit the “Number of Entries” button.

If no entry exists, SP05 is not completely in the system.

How to solve

Make sure that at least SAP Solution Manager SP5 has been installed completely.

Reason

Before SP05 no extractors had been available.

3.1.2 Has the latest BI content been activated?

The structure of the cube has been enhanced to enable a unique alert identification. To enable that data which have been transferred to the cube before the upgrade to Solution Manager Release 7.1 SP5 the old web template 0SM_BPM_WT0001 remains as it was. The data transferred after the change to 7.1 SP05 can be viewed by new queries, which are displayed in a new web template. Of cause these new structures need to be activated from BI Content. With the SOLMAN_SETUP this is done automatically.

Check

1) Call transaction RSA1


February 2014 33


3) Right-click and display the Info Cube “Business Process Monitoring Data” with the technical name 0SM_BPM for Info Area “SAP Solution Manager – Business Process Monitoring” and find out whether the dimensions Alert Time and Metric are shown (see Figure 32).

4) If they are not shown, you do not have the newest BI Content activated.

Figure 32 - Dispay InfoCube 0SM_BPM

How to solve

1) Do the activation in SOLMAN_SETUP once again.

2) Alternatively you can also activate the BI Content for Info Cube 0SM_BPM with transaction RSOR.

3.1.3 Errors during Activation of Objects with Type Info Object

The activation of the characteristics 0SM_ALTYP, 0SM_MONID, 0SM_POBJN, 0SM_SOBJN and 0SM_SOLUT might lead to errors, if already master data have been loaded (see Figure 33).

Reason

You try to switch off some characteristic settings, which had been activated once in your configuration. In case you currently have data in that table structures, the system does allow those changes only with an explicit action by the user. Therefore the data of those structures have to be removed and reloaded.

As the current master data extractor loads the master data completely with the next collector run, there shall be no harm for the current data referencing.


34 February 2014

Figure 33 - Transaction RSOR displays errors during the activation of certain characteristics

How to solve

1) Go to transaction RSA1.


3) Right-click and display the Characteristic, which cannot be activated within Info Area “SAP Solution Manager – Business Process Monitoring”

4) View tab “Master data/texts”

5) Remove the flag „With texts“

6) Hit button “Activate”

This is deleting the master data table for the chosen characteristic.


February 2014 35

Figure 34 - Delete the master data

7) Now set again the flag „With texts“

8) Hit the button „Activate“ once again (make sure that „Texts language dependent“ is not set).

Now the problem shall be solved and the version shall be shown as active.

Figure 35 - Activate master data texts again

Repeat step 1) to 8) for the other characteristics which cannot be activated as well.


36 February 2014

The master data will be reloaded at the next master data collector run.

Attention: With this correction the business explorer tab has lost the text setting display and will display the key initially. Therefore please follow the instructions of section 3.2.13 for all characteristics you corrected here manually.

3.2 Problems after the activation

3.2.1 No data are shown in my dashboard

If there are no data shown in the dashboard, this can have many reasons.

1) No data for the selection in the cube 0SM_BPM

2) No data in the cube 0SM_BPM at all

a. Extractors are not active

b. No alerts occurred

c. Monitoring Objects have not been marked for the transfer to BW

3) No data in the referencing cube 0SM_BPM1 (SP07+)

4) The data have been loaded before the upgrade to SP05 and can only be displayed with the web template 0SM_BPM_WT0001 (see section 2.3)

Check

1) Call transaction listcube.

2) Enter Infocube 0SM_BPM.

3) Enter your selection criteria.

See whether the cube contains data for the selection.

3.2.2 Are the extractors really active?

Check


2) Display table E2E_ACTIVE_WLI with EXTRACTOR = ‘DSWP_BPM_ALERT_REPORTING_*’

3) If there are no entries, the extractors have not been activated.

How to solve

1) Review the log in SOLMAN_SETUP. Probably one of the migration steps before could not be performed, e.g. the cube has not been transformed into a real-time cube, yet.

3.2.3 The dashboard graphics do not look like in the screens above

Compare your screens with the screenshots Figure 1, Figure 2 and Figure 3. The look and feel is changed with SP06.

The changes belong to BW_CONTENT. Those changes cannot be delivered by SAP Note, but by SP only.

3.2.4 The extractor DSWP_BPM_ALERT_REPORTING_EXTR stops with “Illegal Input”

Check

Make sure that SAP Note 1796563 is implemented before. If the problem still exists, please do the following:

1) Call transaction SE16 for table DSWP_BPM_BI_EXTR

2) Enter the selection XFLAG <> ‘X’

3) Enter SM_CUVAU <> <space>

4) Hit Execute (F8)

5) If there are entries, see whether there are lower case letters inside the column SM_CUVAU.


February 2014 37

6) Call transaction RSA1 Modeling Info Provider

7) Search for 0SM_CUVAU and double-click on it

If the “Lowercase letters” flag is blank, this causes the problem.

How to solve

8) Change to edit mode, set the flag “Lowercase letters” to ‘X’ and activate the characteristic.

9) Activate in spite of yellow warnings.

10) Then run the extractor once again.


38 February 2014

3.2.5 Message ‘Chart “CHART_*”. Data Provider does not contain any data’ is shown

The following information messages are shown in the web template 0SM_BPM_WT0001N.

How to solve

Open the hourly drilldown by clicking on the little triangles in the data table.

To show the graphic in daily granularity right-click on the hours (here: value 15 or 16) and choose the menu path “Remove drilldown”.


February 2014 39

3.2.6 The web template does not display the recently transferred cube data

Check

Call transaction LISTCUBE and enter a selection condition of the recent alerts that have been transferred to the cube.

Hit execute, to see the alerts that have been transferred to the cube.

Check now whether these data are displayed in the web template (report RS_TEMPLATE_MAINTAIN and web template 0SM_BPM_WT0001N).

How to solve



3) Right-click and display the Info Cube “Business Process Monitoring Data” with the technical name 0SM_BPM for Info Area “SAP Solution Manager – Business Process Monitoring” and chose “Change”

4) Follow the menu path “Environment” “Info Provider Properties” “Change“.

5) In the popup on Tab “Query / Cache” set “Data Integrity” to 1 and hit save.

6) Activate the cube.

Now the alert data shall be displayed in the web template.


40 February 2014

3.2.7 The extractors DSWP_BPM_ALERT_REPORTING_* are in status red

Check

Make sure that SAP Note 1796563 is implemented before. If the problem still exists, please do the following:

- SOLMAN_SETUP Solution Manager Administration (see Figure 26).

- In the Solution Manager Administration window select “Infrastructure” (see Figure 27).

- As shown in Figure 29 view the status of the BPMon Alert Reporting extractors.

- Scroll to the right to see the extractor names.

If you are in SP05 or SP06 the extractors for the transactional data load (DSWP_BPM_ALERT_REPORTING_EXTR) and for the master data load (DSWP_BPM_ALERT_REPORTING_MD) shall have a green status.

How to solve

If any extractor is in status red, select the line and see the details of the extractor log together with the messages for each extractor run (see Figure 36).

If you do not understand how to resolve the error situation shown with a red error message in the extractor log, open a customer message.

NOTE: The extractor for the Alert Reporting Hierarchy assigning solution, business process and step to monitoring objects (DSWP_BPM_ALERT_REPORTING_HIER) shall have a green status in SP07. In earlier SPs this extractor is not used and therefore is displayed red.

If you are on SP07 and the extractor DSWP_BPM_ALERT_REPORTING_HIER is red, please call transaction SE16

- Enter DSWP_BPM_ALERT_REPORTING_HIER into the field EXTRACTOR

- Hit Execute (F8)

Make sure that the following fields are filled like this:

Field TARGETTYPE = CUBE

Field TARGETNAME = 0SM_BPM1

Field DATALOADER = SMD_DATA_LOADER100


February 2014 41

Figure 36 - Display of Extractors in the Solution Manager Administration

3.2.8 You expect more than 10000 alerts per run

Make sure that SAP Note 1796563 is implemented before this analysis.

Please check first of all, whether the high amount of alerts is really reasonable.

To avoid that the extractor does not cope the amount of alerts anymore, you should fine-tune the frequency of how often the extractor is running. Initially this parameter is set to 1440 minutes, which is once a day.

How to solve

The extractor routine processes by default maximum 10000 alerts per run.

To make the collector is running more often by setting the relevant configuration parameter manually, do the following:

- As described in section 2.4 enter the “Extractor Administration” via the “Solution Manager Administration”, “Infrastructure”. Find the BPMon Alert Reporting Extractor, e.g. by using the Filter.

- Mark the line.

- Switch to change mode and activate the “Expert Mode”.

- Within the selected extractor section view the tab “Extractor Detail” “Configuration”.

- Now you can modify the period manually.

- Save your changes.


42 February 2014

Figure 37 - Change the Extractor Configuration

3.2.9 No data transferred to BW although too alerts are to be transferred

Make sure that SAP Note 1796563 is implemented before this analysis.

Your extractor DSWP_BPM_ALERT_REPORTING_EXTR stuck with status red and no alerts being transported at all. This could happen, if there are too many alerts (see also section 3.2.8 how to avoid this problem being caused) to be transferred. Then the routine stops with a time-out and all data are rolled back.

Check

- Call transaction SE16

- Enter table DSWP_BPM_BI_EXTN

- Enter as selection criteria SM_XFLAG <> ‘X’

- Hit the button number of entries

The number shows how many alerts are waiting on the queue in order to be transferred to BW.

How to solve

Please check first of all, whether this high amount of alerts is really reasonable to be produced frequently.

If the system runs into a time-out with the default 10000 records, you should lower this number down to a reasonable amount.


February 2014 43

Usually it should not be necessary to adapt the default maximum number of alerts manually.

To try out which number is reasonable for your system run the main extractor with the active work-list item manually (Use the corresponding entry from table E2E_ACTIVE_WLI for your SID and the EXTRACTOR DSWP_BPM_ALERT_REPORTING_EXTR). The field EXTRACTORCLASS can be used for the maximum number of alerts, that should be transferred, before the alerts are stored in the transfer table as waiting.

The acceptable number of alerts should be set into the table E2E_ACTIVE_WLI into the field EXTRACTORCLASS. Please ask an expert for assistance.

Figure 38 – Sample SE37 Screen for Manual Extractor Call with max. 1000 Alerts transferred

3.2.10 The value helps in the selection screen do not display any or valid data

Check

Call transaction SE16 and view the number of entries for table /BI0/F0SM_BPM1.

If there are not entries in table /BI0/F0SM_BPM1 at all, call transaction SE16 for table E2E_ACTIVE_WLI.

- Enter in field EXTRACTOR DSWP_BPM_ALERT_REPORTING_HIER.

- Hit Execute (F8).

- Double-click the line of the SAP Solution Manager that sends data.

Check whether in field TARGETTYPE is the value CUBE.

Check whether in field TARGETNAME is the value 0SM_BPM1.

Check whether in field DATALOADER is the value SMD_DATA_LOADER100.

How to solve

If those values are not in, change the values.


44 February 2014

3.2.11 In BW only capital letters are stored

The Web Template shows two times the same value, e.g.in the unit of measure, one time with capital and small letters and one with capital letters only.

Check

- Has the data been written in that way also in the setup of the monitoring object? If not, check whether small letters in general have been deactivated in transaction RSKC.

How to solve

- Call transaction RSKC in the SAP Solution Manager.

- Enter “ALL” (NOT “ALL_CAPITAL”) as permitted characters.

- Hit Execute (F8).

For more information see also SAP note 173241.

3.2.12 The alert confirmation timestamp and user are not transferred

The transfer is done in a way, that every alert is transferred only once to the cube. In order to not create any new characteristic combinations, the characteristics of the alert are kept stable. Updates are done on the key figures only.

Consequently the characteristic fields containing the confirmation date, time and user are not filled anymore.

Nevertheless, the information how long it took until the alert has been confirmed is not lost, but is calculated before the transfer and is stored for yellow alerts in in key figure 0SM_COUNB (Number of minutes it took to confirm the yellow alert) and for red alerts in key figure 0SM_CONC (Number of minutes it took to confirm the red alert). If the value is 0 the alert is still unconfirmed.

The web template 0SM_BPM_WT0001N contains a query evaluating these key figures, showing the maximum time it took to confirm the alerts assigned to a monitoring object within a particular time bucket (days, hours).

3.2.13 In the Solution Value Help the Keys are visible without Descriptions

Check

In the selection screen of the web template 0SM_BPM_WT0001N you clicked on the value help in order to select a solution. Unfortunately you do not see the BPMon Solutions as below with a description text, but the Keys only.

How to solve

- Call transaction RSA1 Modeling InfoObjects


February 2014 45

- Search for Infoobject 0SM_SOL32

- Doubleclick on the Infoobject 0SM_SOL32

- Tab Business Explorer General Settings

- Change the value of the field “Display” to Text

- Change the value of the field “Text Type” to Long Text

- Activate the changes.

In relation with the issue described in section 3.1.3, the description texts might not be displayed also for the characteristics mentioned there. The correction instruction here will help also for those characteristics.

3.2.14 Extractor complains that the Cube 0SM_BPM1 or 0SM_BPM1 is no real-time Cube

Check

For both cubes 0SM_BPM and 0SM_BPM1 check whether they are displayed as real-time cubes in transaction RSA1. This is described in section 3.1.1.7. If cube 0SM_BPM is not shown with the real-time icon, make sure that the BPMon Alert Reporting activation ran successfully.

Cube 0SM_BPM1 is delivered as a real-time cube. Anyway it could be, that the data load behavior had been changed.

Check the load behavior as follows:

- Call transaction RSA1

- Click on Info Provider in Section Modeling.

- Find the Info Cube “Business Process Monitoring Data” with the technical name 0SM_BPM for Info Area “SAP Solution Manager – Business Process Monitoring” or “Business Process Monitoring Preselection” with the technical name 0SM_BPM1 and right-click on it.

- in the context menu choose “Change Real-Time Load Behaviour …”

Check whether the option box “Real-Time Data Target Can be Planned; Data Loading Not Allowed” is set.

How to solve

If this option box is not selected, change the selection as shown in the screenshot. Make sure that this setting is set for both cubes in that way.

With the next extractor run the extractor shall not complain anymore about a non-real-time cube.

Alert Reporting Analysis with SAP Solution Manager 7.1 SP05+

Documents