setupguide_bpanalytics_v2

Business Process

Analytics 2.0

with SAP Solution

Manager 7.1 SP05

Business Process Analytics -Setup and user Guideline

© Copyright 2014 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® andSQL 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 Server

TM 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 ofthe Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,WinFrame®, VideoFrame®, MultiWin® and other Citrix product namesreferenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

SAP AGNeurottstraße 16

69190 Walldorf

Germany

T +49/18 05/34 34 24

F +49/18 05/34 34 20

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 byNetscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,Management Cockpit, mySAP, mySAP.com, and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. MarketSet and EnterpriseBuyer are jointly owned trademarks of SAP Markets and CommerceOne. All other product and service names mentioned are thetrademarks of their respective owners.

Disclaimer

Some components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

http://service.sap.com//bpm

Setup Guide Business Process Analytics 2.0 with SAP Solution Manager 7.1 SP05

4 January 2014

TABLE OF CONTENTS

1 OVERVIEW, SETUP AND CONFIGURATION ...................................................................................... 7

1.1 INTRODUCTION AND MOTIVATION ................................................................................................... 7

1.1.1 What is Business Process Analytics? ..................................................................................... 7

1.1.2 Typical Use Cases .................................................................................................................... 8

1.1.2.1 Business Process Improvement ............................................................................................................ 8

1.1.2.2 Business Process Operations ................................................................................................................ 9

1.1.3 Benefits of Business Process Analytics ................................................................................. 9

1.2 ARCHITECTURE OF BUSINESS PROCESS ANALYTICS .................................................................11

1.2.1 Data Retrieval and Reporting ..................................................................................................12

1.2.2 Alerting based on BW .............................................................................................................13

1.3 TECHNICAL PREREQUISITES FOR BUSINESS PROCESS ANALYTICS .........................................16

1.3.1 Required Software Components and SAP Notes ...................................................................16

1.3.2 Administrative Requirements .................................................................................................16

1.3.2.1 Activation of Info Cube from BI Content ................................................................................................17

1.3.2.2 Activation of Services ...........................................................................................................................17

1.3.2.3 Checking status of Solution Manager Diagnostics Extractor Framework (EFWK) ...................................19

1.3.2.4 Authorizations ......................................................................................................................................20

1.3.3 Prerequisites in the Solution Landscape ...............................................................................20

1.4 DATA COLLECTION FOR BUSINESS PROCESS ANALYTICS .........................................................22

1.4.1 Update Repository and Select Systems .................................................................................23

1.4.2 Define Scope and Frequency of Data Collection ...................................................................24

1.5 THE BUSINESS PROCESS ANALYTICS APPLICATION ...................................................................32

1.5.1 Analysis Selection ...................................................................................................................32

1.5.2 Benchmarking and Analysis ...................................................................................................33

1.5.2.1 Benchmarking......................................................................................................................................34

1.5.2.2 Trend Analysis .....................................................................................................................................35

1.5.2.3 Age Analysis ........................................................................................................................................36

1.5.2.4 Detail Analysis .....................................................................................................................................36

1.6 SETUP FOR BUSINESS PROCESS MONITORING ALERTING .........................................................38

1.6.1 Motivation ................................................................................................................................38


January 2014 5

1.6.2 Prerequisites............................................................................................................................38

1.6.3 Procedure ................................................................................................................................38

1.7 MONITORING BASED ON DATA FROM BUSINESS PROCESS ANALYTICS ...................................42

1.7.1 Prerequisites............................................................................................................................42

1.7.2 Procedure ................................................................................................................................42

2 USING BUSINESS PROCESS ANALYTICS .......................................................................................44

2.1 GLOBAL TRANSPARENCY ...............................................................................................................44

2.2 BENCHMARKING OVER TOP N ORGANIZATIONAL UNITS .............................................................46

2.3 VALUE BENCHMARKING ..................................................................................................................48

2.4 ADVANCED BENCHMARKING ..........................................................................................................49

2.5 DETAIL ANALYSIS .............................................................................................................................52

2.6 TREND ANALYSIS .............................................................................................................................53

2.7 AGE ANALYSIS ..................................................................................................................................55

2.8 USING BUSINESS GRAPHICS INSTEAD OF BUSINESS OBJECTS XCELSIUS...............................58

2.9 KEY FIGURES AND KEY FIGURE VARIANTS ...................................................................................60

2.9.1 Creating a Variant: ...................................................................................................................60

2.9.2 Creating and Changing Key Figure Variant Categories .........................................................63

3 ROLES AND AUTHORIZATIONS .......................................................................................................65

3.1 AUTHORIZATION FOR DATA COLLECTION .....................................................................................65

3.2 AUTHORIZATION FOR FRONTEND (APPLICATION) ........................................................................66

3.2.1 User types: Administrator, Configurator, and End-User of Business Process Analytics ....66

3.2.2 Key Figures and Key Figure Variants .....................................................................................69

3.2.3 Applicable restrictions in Business Process Analytics .........................................................69

3.2.4 Available Roles for Business Process Analytics Usage ........................................................69

3.2.4.1 Template for: Administrator/Configurator: SAP_SM_BPOANA_ALL (Solution Manager) .........................70

3.2.4.2 Template for Administrator/Configurator: SAP_MANAGED_BPOANA_ALL (Managed System) ..............73

3.2.4.3 Template for End-User: SAP_SM_BPOANA_DIS (Solution Manager)....................................................74


6 January 2014

3.2.4.4 Template for End-User: SAP_MANAGED_BPOANA_DIS (Managed System) ........................................76

3.2.4.5 Visibility of Solutions: SAP_SV_SOLUTION_MANAGER (Solution Manager) .........................................77

3.2.4.6 Example ..............................................................................................................................................78

3.3 AUTHORIZATIONS USE CASE ..........................................................................................................81

4 DATA GROWTH AND HOUSEKEEPING ............................................................................................85

4.1 INTRODUCTION .................................................................................................................................85

4.2 INFLUENCING FACTORS – DATA GROWTH ....................................................................................85

4.3 IDENTIFYING TOTAL NUMBER OF ENTRIES IN ANALYTICS INFO CUBE ......................................86

4.4 SELECTIVE DELETION ......................................................................................................................86

4.5 AUTOMATIC HOUSEKEEPING ..........................................................................................................88

5 AVAILABLE BADI FOR RESTRICTION OF MASTER DATA LOAD/DESCRIPTIONS FOR SPECIFICSEMANTIC-IDS ..........................................................................................................................................89

5.1 OVERVIEW .........................................................................................................................................89

5.2 IMPLEMENTATION .............................................................................................................................89

6 APPENDIX ..........................................................................................................................................93


January 2014 7

1 Overview, Setup and Configuration

1.1 Introduction and Motivation

The economic environment of the financial crisis has lead to increased pressure for companies to reduce

costs. Therefore, many IT departments are focusing on cleaning up their existing SAP systems that are

already live for many years and trying to identify optimization or improvement potential in the business

processes running on these systems. Frequent key words are business process compliance, business

process excellence, business process governance as well potential for old data reduction. However, for

many companies this is like searching for the “needle in the haystack” because they do not know where to

start. From the perspective of IT-departments the challenge is that these are often supposed to come up with

improvements. At the same time, IT departments are heavily relying on the functional input from the business

departments. Another challenge for IT departments is ensuring the quality of operations and investing in

innovation while budget is tight.

1.1.1 What is Business Process Analytics?

On the one hand, SAP Business Process Analytics 2.0 is a tool within SAP Solution Manager, that helps a

business department (i.e. the Business Process Champion) as well as an IT department (i.e. the Business

Process Expert or the Business Process Operations Team) to make own proposals for process optimization

and stabilization.

On the other hand, data from SAP Business Process Analytics 2.0 can also be used for business process

operation. That is, this data supplies SAP Business Process Monitoring that allows automated early problem

detection (by providing automated alerting) as well as an effective problem solving (by showing the business

process context and by providing guided procedures). Hence SAP Business Process Analytics 2.0 helps IT

departments reducing manual labor for business process operations leaving more free resources for

investing in innovation.

SAP Business Process Analytics 2.0 evaluates key figures for business process operations. The main focus

is on key figures from the area of application monitoring (as it is called within Business Process Monitoring).

Application monitoring offers two main categories of key figures: throughput key figures and backlog key

figures. Throughput key figures give an indication about the volume of business documents that are created

per day. Backlog key figures give an indication, if business documents are not processed in due time. Key

figures from the area of application monitoring should allow you to answer questions of the following kind,


8 January 2014

e.g. for an Order to Cash scenario: How many sales orders are open (not or only partially delivered)? How

many sales orders cannot be processed any further, because they are incomplete, have a delivery, billing or

credit block? How many outbound deliveries are open (goods issue posting not complete)? How many

picking transfer orders are open (not confirmed) in your warehouse management system? How many

outbound deliveries are in status “Goods issue posted” but no invoice was created? How many invoices

have been created but were not printed? How many sales invoices were not posted to FI?

As can be expected from an analytical application, data is evaluated in a graphical way. There are three

methods of analysis: Benchmarking, Trend Analysis as well as Age Analysis. Benchmarking allows

identifying areas with high document volume as well as areas with potential for improvement in terms of

backlog. Trend analysis allows to investigate historical patterns as well as to make predictions for the future.

Age analysis allows determining, if the backlog is relevant for current operations or if the backlog rather

represents a potential for data archiving (if a delivery to a customer is overdue since 10 years, does the

customer still wait for a goods to be shipped?)

In addition to that, Business Process Analytics 2.0 supports root cause analysis for measured backlog. That

is, Business Process Analytics 2.0 allows to display a list of business documents that are in backlog with a

single click and to further navigate to the display transaction for a single document in the list (e.g. display

sales order).

1.1.2 Typical Use Cases

In order to use the potential of Business Process Analytics 2.0 successfully, the right people within a

company have to get involved. The first step is to define use cases that describe who will work with Business

Process Analytics in which way. To get started, two typical use cases - "Business Process Improvement" and

"Business Process Operation" are described in the following section.

1.1.2.1 Business Process Improvement

The use case "Business Process Improvement" addresses the Business Process Champion from the

business department as well as the Business Process Expert of the Business Process Operations team from

the IT department. From SAP's experience, the best results can be achieved, if these teams/persons from

business and the IT department work together. The target groups are neither end users who care about their

individual work lists nor business users who care about business KPIs such as revenue and profitability.

The objective is to get an overall picture of business process operation in all systems that are required to run

the business processes that are in focus and to subsequently discover potential for improvement, i.e.

improving business processes without (significantly) changing the business process logic or flow.


January 2014 9

In order to achieve this, the following steps have to be performed as preparation: The key figures that are

relevant for analysis are selected. Subsequently, the data collection for these key figures is scheduled so

that the data is transferred to SAP BW.

After the preparation is finished, the following steps have to be performed in regular intervals: The Business

Process Analytics Web Dynpro application is used to discover optimization potential by performing (internal)

benchmarking, trend analysis, age analysis and root cause analysis. Subsequently the findings are

discussed with the business department. Finally, measures for business process improvement are defined,

implemented and monitored.

1.1.2.2 Business Process Operations

The use case "Business Process Operations" addresses the Business Process Operations team within the

IT department. The Business Process Operations team works with Business Process Monitoring in SAP

Solution Manager. Data from Business Process Analytics that is stored in BW can be used as a data source

for Business Process Monitoring.

The objective is to automate labor intensive monitoring tasks in order to enable valuable IT resources to

provide more added values to the company.

In order to achieve this, the following steps have to be performed as preparation: The key figures that are

relevant for monitoring and alerting are selected. In addition to that, filter variants that differentiate e.g.

different organizational units or document types are defined. For these key figures along with their variants,

thresholds are defined, that allow deciding if e.g. a critical value for backlog has been measured. The steps

that have to be performed to resolve the error situation can be documented in guided procedures. If

everything has been set up correctly, the monitoring can be activated.

If a threshold has been exceeded, an alert is shown in the business process overview. In addition to that, the

responsible people can be notified automatically via e-mail notification, SMS or service desk message.

1.1.3 Benefits of Business Process Analytics

Business Process Analytics 2.0 enables business process improvement by performing business process

benchmarking, identifying potential for old data reduction, detecting gaps in process implementation as well

as identifying potential for improving business process standardization. In addition to that, Business Process

Analytics 2.0 can make a significant contribution to improve the technical performance of Business Process

Monitoring (especially in the area of Application Monitoring).

The Benchmarking functionality in Business Process Analytics 2.0 allows benchmarking over (internal)

organizational units. Thus, visibility and transparency can be improved.


10 January 2014

The identification of potential for old data reduction allows the clean- up of old and open business transaction

data. This leads to improved planning results, improvement of performance of related reports or processes,

higher reporting quality as well as higher end-user efficiency.

By detecting gaps in process implementation such as configuration issues and missing closing steps of open

documents, the process implementation can be optimized.

By detecting gaps in business process standardization such as organizational units or end-users which do

not follow the process template, potential for better end- user training can be identified.

Last but not least, the performance of Business Process Monitoring in the area of Application Monitoring can

be improved significantly. This can be achieved, because data that is stored in BW by Business Process

Analytics can be re-used by Business Process Monitoring which reduces the load on the managed system

(the system which is monitored by SAP Solution Manager).


January 2014 11

1.2 Architecture of Business Process Analytics

Company’s core business processes can be distributed across various systems such as ERP, CRM and

EWM (these systems are also called managed systems). In order to centrally analyze these business

processes, users need a system that is connected to all involved systems. This central system is SAP

Solution Manager (that is also called managing system). SAP Solution Manager can collect data from these

systems and make it centrally available for alerting and reporting.

Architecture Overview

In the case of Business Process Analytics 2.0, this data is usually stored in the SAP Solution Manager

internal BW. There is also the possibility to use an external SAP BW. However, a decision is required for all

BW data that is used in SAP Solution Manager (not just for Business Process Analytics). It is not possible to


12 January 2014

store some parts of the BW data on the SAP Solution Manager internal BW and other parts of the BW data

on an external BW.

The architecture of Business Process Analytics 2.0 consists of two main parts. The first part covers data

retrieval from the managed system to BW as well as reporting based on data within BW. The second part

covers alerting based on BW data. Of course, the data retrieval to BW is a prerequisite for the alerting based

on data in BW.

1.2.1 Data Retrieval and Reporting

The setup for data retrieval and reporting is performed in SAP Solution Manager. It specifies what data (key

figures) is collected, how often, and from which systems. According to this setup, the Business Process

Monitoring Infrastructure schedules the specified data collectors on the managed systems.

Data Retrieval and Reporting

On the managed system, the data collectors will be executed and the results of the data collection will be

stored in the Analytics Store. The Analytics Store consists of two parts. One part is the BW Delta Queue,

which is supplied with the result of the data collection run for later retrieval by SAP Solution Manager. The

BW Delta Queue contains semi-aggregated data that is later used for Benchmarking and Trend Analysis.


January 2014 13

This data remains in the BW Delta Queue until it is successfully stored into the Analytics BW info Cube –

either on the SAP Solution Manager or on the external BW system. The other part is a Detail List that is only

available for backlog key figures and contains the single items that are in backlog. In contrast to the BW

Delta Queue, the Detail List contains only the result of the most recent collector run. If a collector run

produces a new Detail List, the list from the previous run is overwritten. The Detail List contains non-

aggregated data that is used for Age Analysis and Detail Analysis.

SAP Solution Manager contains a framework for the extraction of data from the managed system to SAP

BW. This framework is called Extractor Framework (EFWK). The EFWK picks up data from the BW Delta

Queue on the managed system, stores the data directly in the BW Info Cube 0SM_BPMRH and reorganizes

data in the queue that has been successfully transferred without further processing in BW (PSA, DSO).

The reporting is done in the Business Process Analytics Application (based on Web Dynpro for ABAP) on

SAP Solution Manager. The Business Process Analytics Application can merge data from BW with data from

the Detail List in the Analytics Store on the managed system. Based on this data, Benchmarking, Trend

Analysis, Age Analysis as well as Detail Analysis can be performed.

1.2.2 Alerting based on BW

The setup for alerting based on SAP BW is performed on SAP Solution Manager. Alerting is only possible for

key figures that are available in BW.

In contrast to the setup for the data collection, the setup for alerting is not performed for a specific system but

for a business process step. It is to specify, which key figure should be monitored for which business process

step and with which thresholds. The reason for that is, that in case of an alert the business impact needs to

be visible immediately. However, in SAP Solution Manager, a business process step is always linked to a

system and therefore it is clear which managed system was the source for the data in BW. In other words,

the setup for alerting is done for a business process step (e.g. create sales order) on a managed system

(e.g. ERP), even if the data that is used for alerting is already stored on the SAP Solution Manager internal

SAP BW.

If new data for a key figure that has been selected for alerting arrives in the SAP Solution Manager internal

BW, it is checked if the thresholds for the key figure in question have been exceeded. If this happened, a

yellow or a red alert is raised. Otherwise, a green measurement indicates that everything is okay. The check

is performed on the Info Cube 0SM_BPMRH via the BPMon infrastructure that triggers the BPMon BW

Collector.


14 January 2014

Alerting based on BW

The following example will help to understand the advantage of this architecture from a performance point ofview:

An example for possible results for the key figure "Sales orders with delivery block" is shown in the figure"Results of a data collection run in Business Process Analytics". This figure shows the number of salesorders with delivery block by document type (A, B, C) and sales organization (0001, 0002, 0003). It is anassumption, that for each combination of sales organization and document type a different person isresponsible for analyzing the root cause of the delivery block (in this example this would be 9 differentpersons) and that these persons should be notified if the threshold for sales orders with delivery block in theirarea of responsibility is exceeded (e.g. the measurement for sales organization 0001 and document type B is100 and the threshold is 20). Without Business Process Analytics, 9 data collection runs would have to beperformed on the managed system. With Business Process Analytics, only one data collection run isrequired on the managed system. The subsequent 9 data collection runs are performed on the SAP SolutionManager internal BW. This is on the one hand better for performance, because the load on the managedsystem is reduced. On the other hand, the collection runs for alerting on BW can be performed very quicklydue to the architecture of the BW Info Cube.


January 2014 15

Results of a data collection run in Business Process Analytics


16 January 2014

1.3 Technical Prerequisites for Business ProcessAnalytics

1.3.1 Required Software Components and SAP Notes

In order to setup and use Business Process Analytics 2.0, the following releases of software components arenecessary as an absolute minimum:

- Solution Manager 7.1 SP 5 (ST 710 SP5, ST-BCO 710 SP3, ST A/PI Type P)

- Each connected managed system must have at least ST A/PI Type P installed.

All the available application monitors within the ST A/PI plugin are enabled to be used with Business ProcessAnalytics, with ST A/PI Type P we have collectors in Sales & Services, Procurement, Manufacturing,Plant Maintenance, Automotive, Retail, EWM, WM, CRM and SRM which can be used in BusinessProcess Analytics.

Please check the following consulting note (which is updated frequently) for all required SAP Note(s) inSolution Manager and in the selected managed system(s) and implement them:

- 1759233 (BPO Dashboards/BP Analytics: required SAP Notes for SP05/higher)

DISCLAIMER:

Please use this Setup-Guide for Business Process Analytics at your own risk. All ourrecommendations regarding the activation of this functionality are based on our general experienceand maybe are not valid for your specific implementation, especially when you are already using theBW component or Diagnostics in SAP Solution Manager. In this case, please consult and involve thepeople already working with BW or Diagnostics in the SAP Solution Manager system to make surethat all functions in BW or Diagnostics keep working.

1.3.2 Administrative Requirements

Within the technical activation of Business Process Analytics 2.0, two activities related to System

Administration have to be performed, the activation of the Info Cube used by Business Process Analytics 2.0

and the maintenance of authorizations to access the Info Cube and its data later on. We assume that the

managed systems you want to include in the reporting with Business Process Analytics 2.0 are connected

properly to your SAP Solution Manager (including necessary RFC connections within System Landscape

and the local BPM connection is working as described in SAP Note 784752).


January 2014 17

1.3.2.1 Activation of Info Cube from BI Content

The activation of the Info Cube has to be done in the Solution Manager Configuration. Please access viatransaction SOLMAN_SETUP the scenario “Business Process Monitoring” in the left window and select step1.1 “Configure Automatically” from the roadmap in the right window – execute activity “Activate BW Cubes” ifit is not yet executed. If the activity is already performed, it should have a green rating assigned, meaningthat the required Info Cube 0SM_BPMRH is already active and therefore available for the Data CollectionInfrastructure.

Activation of Info Cube 0SM_BPMRH in transaction SOLMAN_SETUP

1.3.2.2 Activation of Services

The Business Process Analytics functionality is designed as a Web Dynpro component, therefore theactivation of the corresponding HTTP Services:

/sap/bc/webdynpro/sap/ags_bpm_bi_navigator

/sap/bc/webdynpro/sap/ags_bpm_bi_analysis

/sap/bc/webdynpro/sap/ags_ai_chart

/sap/bc/webdynpro/sap/ags_ai_data_table

/sap/bc/webdynpro/sap/ags_ai_detail_list

/sap/bc/webdynpro/sap/ags_ai_general_settings


18 January 2014

/sap/bc/webdynpro/sap/ags_ai_personalization

/sap/bc/webdynpro/sap/ags_ai_start

/sap/bc/webdynpro/sap/ags_ai_variant_management

/sap/bc/webdynpro/sap/ags_bpm_setup

must be checked in client independent transaction SICF in the SAP Solution Manager. Please selectHierarchy Type “Service” and press the “Execute”-button:

Selecting HTTP Service Maintenance

Then follow the path /sap/bc/webdynpro/sap/ in the list “default host” and find the ten entriesags_bpm_bi_navigator, ags_bpm_bi_analysis, ags_ai_analysis, ags_ai_chart, ags_ai_data_table,ags_ai_detail_list, ags_ai_general_settings, ags_ai_personalization, ags_ai_variant_management,ags_ai_start and ags_bpm_setup. If the two entries are greyed out, please right-click on each of this entriesand select option “Activate Service”. Afterwards, the two entries should be active and shown in black color.


January 2014 19

Activating Services

1.3.2.3 Checking status of Solution Manager Diagnostics Extractor Framework (EFWK)

For the data transfer between managed systems and SAP Solution Manager, Business Process Analytics isusing the Extractor Framework (EFWK) from Solution Manager Diagnostics. In order to use it, its actualstatus has to be evaluated and missing parts have to be activated and configured in SAP Solution Manager.

First of all, it has to be checked in transaction SM37 in Solution Manager client if the reportE2E_EFWK_RESOURCE_MGR is running in SAP Solution Manager; otherwise it has to be scheduled torun each minute throughout the day.

This job is checking if data extractors defined within the EFWK in table E2E_ACTIVE_WLI are due toexecution regarding their actual status described in table E2E_EFWK_STATUS. If data extractors are due,they are executed in the managed systems via RFC call due to the settings in table E2E_RESOURCES – ifno data extractors are due, the report is finished immediately, generating no further workload.

In a second step, the settings in table E2E_RESOURCES have to be checked. This table should at leastcontain the RFC destinations NONE, SOLMAN_DIALOG_WORKPROCESSES and theSM_<SID>CLNT<Client No.>_READ connections from SAP Solution Manager to the managed systems forwhich Business Process Analytics should be set-up, as summarized in the following screenshot:


20 January 2014

Maintaining Resources of the Extractor Framework (EFWK)

In case entries are missing, please add them via button “Create” in the menu bar, the LASTUPDATE field isfilled with the time stamp information YYYYMMDDHHMMSS, use as a starting point the RESOURCECAPand RESOURCECOUNTER settings from the screenshot, they determine how many EFWK extractors canbe started in parallel for a specific destination.

1.3.2.4 Authorizations

1.3.2.4.1 System user for data transfer

If the EFWK is using a special RFC connection with name pattern “BI_CLNT<Client No.>” as described

before in a Solution Manager system, the available system user in this RFC connection (SMD_BI_RFC) in

BW client needs an extension of authorizations in standard role SAP_BI_E2E to access the Info Cube

0SM_BPMRH for data transfer and data query operations regarding the execution of Business Process

Analytics.

If the RFC connection “NONE” is being used for access to BW (see chapter 1.3.2.3), the end-user needs

additionally the role SAP_BI_E2E.

1.3.2.4.2 End-user for Business Process Analytics

Within Business Process Analytics 2.0, we introduce three different user types, the Administrator, the

Configurator and the End-User for Business Process Analytics. In Chapter 3, you will get a detailed overview

on the available roles and authorizations within Business Process Analytics.

1.3.3 Prerequisites in the Solution Landscape

In order to collect data for Business Process Analytics 2.0, a solution needs to be available. Either an

existing solution is selected or a new solution has to be created. In a solution, systems and corresponding

business processes can be bundled. This makes it possible to monitor productive business processes across

the relevant operational systems.


January 2014 21

In order to create a solution use transaction code SOLMAN_WORKCENTER. First of all, navigate to tab

(WorkCenter) SAP Solution Manager Administrator. On the menu, go to Solutions and then click “New”. In

the browser window, enter a name for the solution and define the original language. Then click the "Save

solution" button.

Create Solution

Within the Solution Landscape Maintenance the logical components have to be entered. Logical components

are used to determine which systems will be managed within the solution. Therefore the selections that are

made in the Solution Landscape Maintenance influence, which systems are later available for monitoring. To

use the F4-button should help to select the relevant logical component(s).

1

23

4


22 January 2014

1.4 Data Collection for Business Process Analytics

In the setup for data collection the following main steps have to be performed. Firstly, a decision has to be

made, from which systems (the so-called managed systems) data is collected. At the same time it needs to

be sure that SAP Solution Manager is updated with the actual list of application monitoring definitions (key

figures) available on the managed systems. Then the scope (which key figures) as well as the frequency

(how often should these key figures be collected) of data collection is specified. Finally the data is transferred

to BW.

It is of utmost importance to consider the impact that the settings for scope and frequency of datacollection have on data volume, performance and system resources (also on the managed systems!).In no case, the data collection should be scheduled too frequently. Please follow therecommendations given in the section below!

The Data Collection can be set up in the Business Process Monitoring Setup Session.

Call BPMon Setup Session via Solution Manager Workcenter


January 2014 23

1.4.1 Update Repository and Select Systems

Before the actual data collection settings can be entered, the systems from which data should be collected

have to be selected. The information, which data can be collected from these systems is often not available

on SAP Solution Manager. In fact, especially the application monitors available for Business Process

Analytics are delivered as add-on (i.e. ST-A/PI) on the managed systems.

To make the monitors available in the SAP Solution Manager, the monitor definitions need to be transferred

from the managed system to a central repository in the SAP Solution Manager System. To get the monitors

available it is required to select the managed system first and then to click the button “Load Monitor

Definitions”.

Load Monitors

After that, the logical component (i.e. system and client combination in the leading role for the solution) from

which data should be collected for reporting has to be selected. In order to do this, expand the node “Logical

Components” in the navigation context menu to view all relevant logical components and select the relevant

one for data collection.

Select Logical Component


24 January 2014

1.4.2 Define Scope and Frequency of Data Collection

Next, the monitoring object for the corresponding logical component (e.g. Sales Documents Items) can be

selected. Select the “Create” button in order to add a monitoring object to the logical component.

From here, the application areas for the corresponding logical components (e.g. Sales & Services,

Procurement) must be selected in order to view possible monitors. The application area is a filter that allows

restricting the list of monitors that is offered in the next step. Several monitoring types are available, including

interface and cross-application monitors. The following application areas can be selected:

Extended Warehouse Management

Manufacturing

Sales & Services

Procurement

Plant Maintenance

Automotive

Aerospace and Defense

Financials

Inventory Management

Logistics Execution

Quality Management

Industry Specific

Retail

Warehouse Management

Customer Defined

Marketing

Project Systems

Quality Management

Cross-Application

Interfaces

Data Consistency

21


January 2014 25

Application Areas

The areas selected make possible monitors available. A monitor (or monitoring object) represents a

collection of key figures that are usually related to the same business document type (e.g. sales orders,

deliveries, purchase orders). Use the drop-down of field “Monitor” in order to select the relevant monitoring

object. In field “Name”, you can change the name of the monitoring object. The “OK” button must be clicked

before the entry can be saved and the next steps completed.

Select one or multipleareas in order torestrict the number ofpossible monitoringobjects available.


26 January 2014

Selection of Monitoring Objects

At Logical Component level, the Monitoring Objects table is now updated with the newly created Monitoring

Object. To define the scope and schedule for the Monitoring Object, click on the relevant Monitoring Object

(e.g. SD – Sales orders items created) in the table.

Define Monitoring Object details

Click on the MonitoringObject to forward navigateto the details.


January 2014 27

The tab “Monitoring Configuration” shows all available key figures of the selected monitoring object. It is

required to mark the key figures that should be monitored.

Settings for the Monitoring Object

Under the same tab, for each key figure, it is possible to maintain a parameter set (a so called counter). This

counter is a further option that allows the user to select what data is really required. On one hand, this

counter allows to restrict the data collection according to the parameters that are offered for the key figure.

For example, a customer might want to analyze the backlog of sales document times only for a certain

market that can be determined from the sales organization (e.g. US* for the market). On the other hand, the

check-boxes for “Group by” allow the user to select upfront, which dimensions should be later on available

for reporting reasons (e.g. Benchmarking). At least one group by flag should be selected,


28 January 2014

Monitoring Configuration

Only for those fields, for which the Group by check box is selected, an analysis of the distribution of these

fields is possible. If you want to analyze, for example, the distribution of sales document items created

across the different sales organizations, the “Group by “-check box must be selected for the Sales

Organization field. In the Business Process Analytics application, such fields are available as so-called

dimensions.

In the field “Parameter Set” a name for the counter can be entered. A counter must be customized for each

key figure in the same way like described before.

Within the tab “Monitoring Schedule” the user can decide how often a data collection should run. In order to

do this, it can be selected in which intervals and on which weekdays a data collection is performed.

Therefore two scheduling types are available:

- on a weekly basis and

- on a monthly basis


January 2014 29

Backlog key figures should be scheduled in no higher frequency than once per day. If a high data volume is

expected, it should be considered to schedule such data collectors in a lower frequency. Throughput key

figures should be scheduled exactly once per day. Furthermore it is strongly recommend that the flag "Data

from previous day" is set in order to make sure that the data for a whole day is collected. Otherwise, the

result of the data collection depends on the time of execution. For example, if a collector for a throughput key

figure is scheduled without the flag "Data from previous day" and the collector runs at noon, only the

throughput from midnight until noon would be captured.

Definition of monitoring schedule

After that all entries should be saved and the Generation and Activation can be performed. Check the

messages in the activation protocol that give an indication if the data collection, as well as the data transfers

to BW, have been scheduled successfully.

Changing the “Monitoring Configuration” (Group-By flags and filter criteria) of active monitoring

objects will negatively affect the information value of your historical data!

As a consequence, the data might confuse the BP Analytics/BPO Dashboard user or lead to the

assumption that there is some inconsistency in BP Analytics or BPO Dashboards.

In case you change active monitoring objects where data was already collected, it will lead to the

following effects:


30 January 2014

1. When changing (remove or add) the Group By flags of an active monitoring object used in BP

Analytics, too high “Measured values” for Backlog key figures (including Exception key figures)

will be displayed in BP Analytics, when selecting a timeframe which begins before the flag was

removed and ends after the flag was changed. The correct aggregation for the uncheck Group-

By flag can no longer be executed by BP Analytics in this case.

2. When changing the filter criteria (like organizational units, document types, time periods) of an

active monitoring object, the data collection will of course consider different data and will be

retrieved accordingly by BP Analytics. The historical data and the “new” data will then both be

displayed for analysis type “Trend Analysis” in BP Analytics, but they are no longer comparable

with each other in a meaningful manner.

It is strongly recommended not to change the (Group-By flags and filter criteria) of active monitoring

objects, but to create a new monitoring object.

If you though need to change the active monitoring object, you must ensure from an organizational

point of view (for example by informing the end users accordingly), that the historical data displayed

in BP Analytics and BPO Dashboards will be not miss-interpreted by the end users.

If there were was no data collected for a monitoring object so far, the object can just be changed

without any negative impact.

In order to ensure the correct behavior when changing monitoring objects, please also apply the

most recent versions of the following ST-A/PI notes in your managed system (as listed in collective

note 1759233):

If ST A/PI version 01Q is used:

1807396 - Advanced Corrections for BPMon & BP Analytics - ST-A/PI 01Q

If ST A/PI version 01Q SP1 is used:

1869678 - Advanced Corrections for BPMon/Analytics 01Q SP1

If ST A/PI version 01Q SP2 is used:

1900144 - ST-A/PI Corrections for BPMon/Analytics 01Q SP2 (framework)

After the Generation/Activation, the BW Master Data should be loaded. This check shows an overview of so-

called Semantic ID’s that contain the master data for the dimensions that have been selected for analysis. In

the field “Load Status” you can see if Master Data has been loaded. In the field “Date” of “Last BW Master


January 2014 31

Data Load”, you see how current the master data in BW is. If the status is not Loaded or Scheduled or if the

Master Data is too old, you should load the master data by selecting the Semantic ID’s you want to load and

by pressing the button “Load BW Master Data”. The relevant Logical Component must be highlighted to carry

out this task.

Load Master Data


32 January 2014

1.5 The Business Process Analytics Application

Benefits and use cases of the Business Process Analytics 2.0 application have already been explained in the

section "Introduction and Motivation". This section now focuses on explaining how to run this application in

detail.

The Business Process Analytics application can be called as URL from the Business Process Operations

Work Center. You find the URL in the section "Common Tasks".

Business Process Operations Work Center

1.5.1 Analysis Selection

Firstly, the timeframe for analysis has to be selected. If you have selected the timeframe, press the button

"Apply Timeframe". Subsequently the solutions that are available in the selected timeframe are selected from

BW. Once the key figures are available, the button “Start analysis for the selected Key Figure” becomes

visible.


January 2014 33

Next, the key figure that you want to analyze has to be specified. You can filter the key figures for selection

by selecting solution, monitoring object name and system/client. Once you have done this, select the key

figure and press the button "Start analysis for the selected Key Figure" If you press this button, a new

window for benchmarking and analysis opens. You can open several windows for multiple key figures in

parallel.

Analysis Selection

1.5.2 Benchmarking and Analysis

In the heading of the Benchmarking and Analysis window all selections that are made in the previous window

are shown. Furthermore, the analysis types Advanced Benchmarking, Benchmarking, Trend Analysis, and

Age Analysis (by year and month) as well the button for Detail Analysis can be seen. These functions will be

explained later in further detail. First, in the "Filter" section, this section allows you to filter the data on the

characteristics of the key figure. It is possible to restrict the displayed data by selecting only specific

dimension values, for example only Sales Organization 0001 (see Chapter 1.4.2) or the Top N. The graphic

will then only display the items of this Sales Organization.

Secondly within the “Chart” section, it has to be decided which dimensions are required for further analysis.

The dropdown fields “Category Dimension” and “Drilldown Dimension” provide the list of options for

dimensions. The available dimensions are those fields where the “Group by” has been set in the Business


34 January 2014

Process Monitoring setup session (see Chapter 1.4.2) along with general and key figure specific

characteristics. It is also possible to sort the chart data by characteristics or measured values

Dimensions for Analysis

1.5.2.1 Benchmarking

Benchmarking allows users to perform a two dimensional analysis. In the example shown in the figure below,

the backlog of overdue schedule line items by Sales Organization and Sales document type is displayed. If

the key figure is a backlog key figure - as it is in this case - the most current measurement in the selected

timeframe is taken for benchmarking. Otherwise, a document that is in backlog for a longer period of time will

be counted several times leading to wrong results. If the key figure is a throughput key figure, all

measurements in the selected timeframe are aggregated. Therefore it is crucial during the set-up to schedule

a throughput key figure exactly once per day!

Within the chart area, one can select/deselect entries from the legend and the chart will be updated

simultaneously.

1. Top ‘N’ 2. Select the dimensions andsort by characteristics.


January 2014 35

Benchmarking over top 5 Sales Organizations

1.5.2.2 Trend Analysis

How the measured value for a key figure has developed within the selected timeframe is shown with trend

analysis in the figure shown below, the trend for the backlog of overdue schedule line items is displayed.

There is no difference in behavior for backlog key figures and throughput key figures.

Trend Analysis

Select/Deselectentries in Legend


36 January 2014

1.5.2.3 Age Analysis

Age analysis is only available for backlog key figures and allows you to determine how old the documents

that are in backlog are. With this information you can decide for example, if the backlog indicates an

operational issue or if the backlog rather represents a potential for old data reduction. In the figure shown

below you see the age distribution for the backlog of overdue schedule line items. Age analysis is only

possible for one dimension (see Chapter 1.4.2, definition of dimensions via Group-by flag), because the

other dimension is always calendar year or calendar month.

Age Analysis by year

1.5.2.4 Detail Analysis

Detail analysis is only available for backlog key figures and allows determining the root cause for potential

backlog. A click on the button "Detail Analysis" allows the user to get a logon screen for the managed

system. Once logged on, a list of the single items that are in backlog is available. The selections that are

made in the "Filter" section are used to filter this list so that only the items that fit to the selected filter criteria

are displayed. In the example shown in the figure below, a list of all schedule line items that are overdue is

shown.


January 2014 37

Detail List

From this detail list, the user can navigate to the business transaction by clicking on a single item of the list,

in order to determine the root cause why this document is in backlog. In the figure shown below, the Sales

Document 10 is displayed in transaction VA03 that is opened automatically by clicking on the Sales

Document 10 in the detail list.

Display of a single item in the associated Business Transaction


38 January 2014

1.6 Setup for Business Process Monitoring Alerting

1.6.1 Motivation

Alerting based on BW data from Business Process Analytics 2.0 can be used to define a monitoring on theanalytical data collected by Business Process Analytics 2.0to react on specific exceptions in the BusinessProcess execution flow. If a specified threshold is exceeded, an alert is generated in the BPMon Operationssession and several auto-reaction methods can be defined (e.g. automatic mail notification). The analyticaldata is already available in the BW of SAP Solution Manager so that the workload regarding data collectionfrom backend systems can be reduced.

1.6.2 Prerequisites

In order to use Alerting based on data from Business Process Analytics, the data collection for Business

Process Analytics had to be configured and activated before on the level of logical components in the

BPMon Setup session so that data is already available in the BW Info Cube when data for alerting is

executed. This already available setup session including configuration for logical components should be

selected and can be changed to add the BPMon Alerting setup. To define the application monitoring objects

relevant for a business process step within the business process it is required to start the business process

monitoring setup session for the relevant solution. To make sure, that all monitors are available, the latest

ST-A/PI release can be downloaded from SAP Service Marketplace (quick link: /supporttools. This ST-A/PI

tool needs to be implemented on the managed system and its coding uncommented via RTCCTOOL.

1.6.3 Procedure

Access the BPMon Setup session via the SAP Solution Manager Workcenter for Business Process

Operations (see Chapter 1.4) and start the BPMon setup within the node of business scenarios, select first

the relevant business process, then the relevant business process step(s).

Click the “Create” button in order to add a monitoring object to the business process step. See Chapter 1.4.2

for details. From here, select the application area for the corresponding monitoring object (e.g. Sales &

Services), then select a monitoring object which is already defined on the level of the logical component,

press ok. The available monitoring objects for BW data are shown and can be selected. You will be asked if

you want to create a reference. Highlight the relevant monitoring object and click “Yes” to confirm. The new

monitoring object will be added to your process step.


January 2014 39

Available monitoring objects for creation with reference

The newly created monitoring object will then appear under Monitoring Objects tab. The parent monitoring

object is visible in the Details section.

Within the selected monitoring object, all available key figures can be selected from the value help. Please

select only those key figures for Alerting which you already configured before for data collection on the level

of the logical components, because otherwise no data will be available in the BW Info Cube and hence the

alert status of this monitoring object will remain grey – which means undefined.


40 January 2014

Selection of Key figures

The alerting based on BW data will be executed right after the data collection for Business Process Analytics

is finished for the referenced monitoring object, so you do not need to maintain an additional monitoring

schedule on this level. A counter per key figure must be defined next. Maintain the parameter set (counter).

Here additional restrictions for several fields can be made. After the parameters are maintained, define the

appropriate threshold values. Please respect, that only such fields are offered, that have a “Group by” flag in

the counter of the BW selection.


January 2014 41

Define Counter and Thresholds

To finalize the BPMon process, save the data and generate the customizing and then the activation of the

monitoring.

Generation/activation of the solution


42 January 2014

1.7 Monitoring based on Data from Business ProcessAnalytics

1.7.1 Prerequisites

An activated Business process monitoring solution that monitors at least one key figure is required to get

alerts within a monitoring session.

1.7.2 Procedure

To get information of the monitoring session it is required to look at the process overview:

Process Overview

The status of the whole process is shown with an alert icon. The alert rating can be “green”, “yellow” or “red”.

“Green” is the lowest rating and “Red” the highest. The highest rating of a key figure defines the status of the

whole process. With a click on the alert icon a more detailed view is offered. The below screenshot shows an

example of the Alert Inbox:


January 2014 43

Alert Inbox


44 January 2014

2 Using Business Process Analytics

Business Process Analytics 2.0 offers a comfortable User Interface to select key figures, performsophisticated analyses and store the key figure selection as Variants. This chapter guides you step-by-stepthrough a typical example on how to use Business Process Analytics 2.0.

The key figure used throughout our example is “Overdue Schedule Line Items”. At the free key figureselection screen, first select a time frame for analysis, and then click on “Apply Timeframe”. All key figuresavailable for selection are now shown. You can filter the available key figures by Solution, Monitoring ID, orSystem. Further, you can filter on key figure level on name, description, category, application area ordescription.

Now select your key figure and click on “Start analysis for the selected Key Figure”.

Figure 1: Selection of key figure “Overdue Schedule Line items” on free selection screen

2.1 Global Transparency

Global transparency can be obtained by performing benchmarking over organizational units and documenttypes to identify organizations and process variants with potential issues, anomalies, untypical patterns orunexpected behaviors.

1. Select time frame fortrend analysis

2. Select Solution, MonitoringID & System

3. Select key figure4. Press start Analysis


January 2014 45

The following figures show how to perform benchmarking over sales organizations, starting with the globaloverview, then narrowing down to the top five sales organizations.

Figure 2: Global benchmarking over all organizational units (Sales Org and/or Plants)

Figure 3: Resulting chart

2.Select necessary filtercharacteristics for org units anddocument types and add them tofilter area.

3. Arrange filtertables accordingto your needsusing the arrows

4. Choose Sales Org asCategory Dimension

5. Press Update

1.Choose Analyticsfunction “Benchmarking”


46 January 2014

2.2 Benchmarking over Top N Organizational Units

Instead of showing all available organizational units, the selection can be restricted by using the “Top N

Filter”. Our example shows how you can perform benchmarking over the top 5 sales organizations.

Figure 4: Setting a filter on the top 5 sales organizations

In the bottom part of the screen, press update.

1. Set Top N Flag

2. Enter 5

3. Click Set


January 2014 47

Figure 5: Resulting chart, showing only the top 5 sales organizations

In order to check the process variants for those top 5 sales organizations, you can add the sales documenttype as drilldown dimension.

Figure 6: Adding the sales document type as drilldown dimension

2. Add Sales Doc Type asDrilldown Dimension

3. Update Chart

1. Leave Top 5 filters on Sales Orgs.


48 January 2014

Figure 7: Resulting Chart showing drilldown on document types

2.3 Value Benchmarking

In addition to perform benchmarking on the number of documents, Business Process Analytics 2.0 allows to

benchmark on the basis of monetary values. In order to protect this sensitive data from unauthorized access,

this functionality is subject to authorization checks (see Section 3.2.4).

The following example describes how to perform Value Benchmarking over Sales Organizations.


January 2014 49

Figure 8: Performing Value Benchmarking over sales organizations

Figure 9: Resulting chart showing the value of documents per sales organization

2.4 Advanced Benchmarking

The functionality “Advanced Benchmarking” allows selecting each of the characteristics that appear ascolumns in the detail list as Category or Drilldown Dimension.

1. Choose „Advanced Benchmarking

2. Choose Value Benchmarking

3. Set Reference Currency

4. Remove Drilldown Dimension5. Update


50 January 2014

For example, with Advanced Benchmarking you can benchmark on the top Materials as described in the

following example.

Figure 10: Selecting top ten materials for advanced benchmarking

Figure 11: Resulting chart showing the number of documents for the top ten materials

Please note that the sequence (from left to right) of the “Top N” filters is important and will be considered forthe calculation. For example, if you would like to see the top 10 materials within the top 5 sales

2. Choose Number of Documents

3. Select Material Description out ofthe available characteristics and moveit to the filter area (Drag & Drop)

4. Set top 10 filter on materials andarrange the Filter characteristics

5. Choose Material Descriptionas Category Dimension

1. Choose „Advanced Benchmarking“

6. Click Update


January 2014 51

organizations, you need to arrange the sales organizations on the left side followed by the materialdescription. If you would like to see, however, the top 5 sales organizations within the top 10 materials, youhave to arrange it the other way round.

Important: Please be aware that especially for some of the characteristics available for AdvancedBenchmarking, the number of distinct values can be very high. For this reason, there is an inherent filter inthe “Personalization” settings. By default, the maximum number of values in the Category Dimension isrestricted to 30 and the maximum number of values in the Drilldown Dimension is restricted to 20.

If you would like to change these settings, please click on link “Personalization”.

Figure 12: Where to find the “Personalization” Settings

Then, go to on tab “Chart”, and change the values according to your needs. The maximum number of valuesyou can enter is restricted to 50 for the Category Dimension, and to 30 for the Drilldown dimension. Thisensures that the chart can be displayed.

Figure 13: Personal chart settings


52 January 2014

2.5 Detail Analysis

There are two possibilities to display the detailed list of documents collected for a key figure, either web

based, or directly on the managed system. In order to display the detail list on the managed system, please

go to “Personalization” and tick off the “web based Detail Analysis” (default setting). This ensures that you

jump from BP Analytics into the managed system to see the detail list there.

Figure 14: Personalization settings

Figure 15: Button “Detail Analysis” to display list of documents

1. Personalization

2. Turn off the flag to workwith the detailed list in themanaged system

Perform DetailAnalysis


January 2014 53

Figure 16: Result: list of documents displayed on managed system

2.6 Trend Analysis

Please note that the Trend Analysis is based on our BP Analytics Info Cube. Therefore you can only perform

the trend analysis only for characteristics for those you have set the “Group by” Flag in the data collector.

Figure 17: Selections for trend analysis

1. Choose “Trend Analysis“

3. Choose the first Drilldown dimensionlike Sales Org (if you only would like tosee the trend for the Sales Orgs)

4. Click Update

2. Choose the scale for thetime window (Calendarday, weeks or months)


54 January 2014

Figure 18: Resulting chart displaying the trend per calendar day for the top 10 sales organizations

You can also work with a second drilldown dimension. With this function, you are able to see trend charts for

combinations of two dimensions, such as Sales Organizations and Document Types or Sales Organizations

and Plants.

Figure 19: Selecting a second dimension for trend analysis

1. Choose the second Drilldown dimension like SalesDoc Type and use the Top N Filter here (e.g. Top 2, ifyou would like to see the trend for the Top 5 Sales Orgsand the Top 2 Doc Types)

2. Click Update


January 2014 55

Figure 20: Resulting chart showing trend for all combinations of Sales Organizations and Document Types

2.7 Age Analysis

The Age Analysis is now based on the Detailed List stored in the managed system in table PTAB. This

means that the Age Analysis will now also be available for all fields in the detail list.

Here you see thecombinations.


56 January 2014

Figure 21: Selections for Age Analysis

Figure 22: Resulting chart showing the age of the backlog per Sales Organization by year

1. Choose “Age Analysis“

3. Choose e.g. “Sales Org” asDrilldown Dimension

4. Click Update

2. Choose “Monthly” or “Yearly”


January 2014 57

Figure 23: Chart showing the age of the backlog per Sales Organization over the last 12 months

You can also Work with additional filters, e.g. perform an Age Analysis over the top 10 Plants (yearly based)

within the top 5 Sales Organizations and set a filter on individual Document Type “TA”.

Figure 24: Selections for Age Analysis with additional filters

2. Filter on DocType TA

3. Choose “Plant” as Drilldown Dimension

1. Top 10 Plants within Top 5Sales Orgs

4. Click Update


58 January 2014

Figure 25: Resulting chart Age Analysis by year using additional filters

2.8 Using Business Graphics instead of BusinessObjects Xcelsius

There are two different rendering engines that can be used to display the graphics in Analytics. By default,

Business Objects Xcelsius (Flash version) is used. If you would like to use Business Graphics instead, go to

“Personalization”, tab “Chart”, and select Rendering Engine “Business Graphics”.


January 2014 59

Figure 26: Changing the rendering engine

Then all Charts will be displayed with Business Graphics:

Figure 27: Chart using Business Graphics

2. Choose “Business Graphics” insteadof “Business Objects Xcelsius“

1. Personalization


60 January 2014

2.9 Key Figures and Key Figure Variants

With Business Process Analytics 2.0, Key Figure Variants are introduced. A Key Figure Variant allows

quick access to a pre-defined, stored data selection (like a view). This data collection is restricted to a certain

solution, application area, key figure and system/client combination. Variants can be assigned to Variant

Categories.

A Variant Category is a container for Key Figure Variants which belong together in a logical context. For

instance, a Variant Category could be used for regions (EMEA, US, APJ) or the SAP applications modules

like SD, MM, FI, etc.

Key Figure Variants and Variant Categories are subject to authorization checks (see Section 3.2.4). Only the

Analytics Administrator/Configurator should be authorized to create variants. The End-user can merely see

and work with the Key Figure Variants/Variant Categories he is authorized for.

2.9.1 Creating a Variant:

Imagine you would like to create a Variant for Key Figure “Orders (GI date in past but not delivered)” such as

only the data for Sales Organization “BL Sales Org Germany” and the top five Sales Document types is

displayed.

1. Select the key figure “Orders (GI date in past but not delivered)”

2. Make the above mentioned selections in the following screen

3. Click on “Save Variant”


January 2014 61

4. Choose a name and description for your variant:

5. You can assign the Variant to an existing category:


62 January 2014

Please see section 2.9.2. on how to create a new Variant Category or change the existing

assignment

6. You can now find your Variant under tab “Key Figure Variants” or “My recently used Key Figure

Variants”:


January 2014 63

2.9.2 Creating and Changing Key Figure Variant Categories

You can create your own Key Figure Variant Categories, edit the Category description, and change the

Variant assignment to the Variant Categories as follows.

1. Go to tab “Key Figure Variants”. Select “Manage Variant Categories and Variants”

2. On the first tab, you can create a new Key Figure Variant Category by simply entering a name and

description, then clicking on “Create”.

3. On the second tab, “Variant Maintenance”, you can edit the description of existing Variants by

selecting the Variant, clicking on “Edit descriptions”, making your changes, and clicking on “Apply”.


64 January 2014

4. On the third tab, “Variant Assignment” you can add or remove Variants from Categories: select your

Category, mark the Variant you would like to add or remove, and choose the corresponding action. A

Variant can be assigned to more than one category.


January 2014 65

3 Roles and Authorizations

With Business Process Analytics 2.0, we introduce a completely new authorization concept. In this version,

we offer additional transparency on sensitive information such as user information and document value(s)

which should only be accessed by specific users. This authorization concept introduces three different user

types, the Administrator, the Configurator and the End-User for Business Process Analytics.

In the following chapters, you will get a detailed overview of the available roles and authorizations for

Business Process Analytics 2.0.

The authorization concept includes dedicated roles related to two specific working areas:

- Setup of the data collection for Business Process Analytics

- Setup and usage of Business Analytics Frontend Application.

3.1 Authorization for data collection

The roles needed to configure the necessary data collectors for Analytics in the Business Process Monitoring

setup user interface are described in detail in SAP Note 784752. Please check this note for relevant

updates.

The configuration task is in most of the cases assigned to the Business Process Analytics Configurator.

Please find additional information regarding our general role concept in chapter 3.2.

The setup of Business Process Analytics takes place on the SAP Solution Manager system in the Business

Process Monitoring (BPMon) setup user interface. Users that are working with Business Process Analytics

configuration need the following roles to access the necessary Work Center functionalities:

- SAP_SMWORK_BASIC (basic role in order to use Work Centers)

- SAP_SMWORK_BPM (in order to use Work Center: Business Process Operations)

- SAP_SMWORK_SM_ADMIN (in order to use Work Center: SAP Solution Manager Administration

for creating new Solutions)

- SAP_SOLMAN_DIRECTORY_ADMIN (in order to set-up BPMon)

- SAP_SV_SOLUTION_MANAGER (in order to set-up BPMon)


66 January 2014

In order to test the applied configuration in Business Process Analytics, the user will additional need the

authorization object SM_BPM_AUT extended by value 40 (BPA – Business Process Analytics) in the

following roles to enter Business Process Analytics in the Work Center Business Process Operations:

- SAP_SV_SOLUTION_MANAGER (in order to access Business Process Analytics)

- SAP_SV_SOLUTION_MANAGER_DISP (Display authorization for all sessions in operations and

operations setup)

- SAP_OP_DSWP_BPM (in order to set up Business Process Analytics)

- SAP_SM_BPOANA_ALL ( as described in chapter 3.2.4.1)

For determining and setting up a meaningful Business Process Analytics Solution, the users need to have

following authorizations in the managed systems:

- Access to transaction ST13 – To ensure that the configuration does not negatively impact the

performance of the monitored managed system. The runtime of backlog key figures should be

checked with ST13, if the runtime is longer than 2 minutes than set the flag ‘DC in Background’

under Tab ‘Monitoring Schedule’ in the Business Process Analytics configuration.

- SAP_MANAGED_BPOANA_ALL ( as described in chapter 3.2.4.1)

The system user in the managed system which is used in the corresponding RFC connection

SM_<SID>CLNT<CLIENT>_READ from Solution Manager to get the data for Advanced Benchmarking and

Age Analysis available in Business Process Analytics needs the role SAP_MANAGED_BPOANA_DIS

assigned as described in chapter 3.2.4.4.

3.2 Authorization for Frontend (Application)

3.2.1 User types: Administrator, Configurator, and End-User of Business Process Analytics

In this chapter, we introduce all relevant user types which are available in Business Process Analytics and

give a short overview regarding their work environment.

An Analytics Administrator has full authorization for Business Process Analytics, hence there should be no

limitation in his functionality (all authorization fields contain “*”). In general, the Administrator is allowed to

use all Analytical Functions and he has unlimited access regarding data, solutions, and systems, e.g. he can

execute free data selections.


January 2014 67

Figure 28: Business Process Analytics Administrator Screen (free selection functionality)

The Analytics Configurator has in general fewer authorizations than the administrator but more

authorizations than the end-user. For example, his access can be limited to specific Solutions (e.g., regional

distribution: EMEA; ASIA, etc.), System/Client combinations, Application Areas or Monitoring Objects. The

Configurator is usually responsible for configuring Key Figure Variants and Variant Categories (see Section

3.2.2).


68 January 2014

Figure 29: Business Process Analytics Configurator Screen. He can access the free selection, but is

restricted to certain Solutions, Systems/Clients, as well as Application Areas.

The Business Process Analytics End-user uses predefined Key Figure Variants (see Chapter 3.2.2) as

views on the data that have been created by the Analytics Administrator or the Configurator. He has the

possibility to restrict these variants further for more detailed selections. The End-user is only a consumer of

Analytics with very limited authorizations and no free selection is possible.

Figure 30: Business Process Analytics End-user Screen. Only Key Figure Variants assigned to him are

displayed.


January 2014 69

3.2.2 Key Figures and Key Figure Variants

With Business Process Analytics 2.0, Key Figure Variants are introduced. A Key Figure Variant allows

quick access to a pre-defined, stored data selection (like a view). This data collection is restricted to a certain

solution, application area, key figure and system/client combination. Variants can be assigned to Variant

Categories.

A Variant Category is a container for Key Figure Variants which belong together in a logical context. For

instance, a Variant Category could be used for regions (EMEA, US, APJ) or the SAP applications modules

like SD, MM, FI, etc.

Key Figure Variants and Variant Categories are subject to authorization checks. Only the Analytics

Administrator/Configurator should be authorized to create variants. The End-user can merely see and work

with the Key Figure Variants/Variant Categories he is authorized for.

3.2.3 Applicable restrictions in Business Process Analytics

The access to data in Business Process Analytics can be restricted in the following areas via available

authorization objects:

Solution

Key Figure Variant

Key Figure Variant Category

System ID/Client

Analytical Function

Application Area

Key Figure/Key Figure Groups (e.g. KPSD0001*)

These authorization objects are explained in detail in the next chapter.

3.2.4 Available Roles for Business Process Analytics Usage

In SAP Solution Manager, all users working with Business Process Analytics need to have the authorization

object SM_BPM_AUT extended by value 40 (BPA – Business Process Analytics) in the following roles:

- SAP_SV_SOLUTION_MANAGER (in order to access Business Process Analytics)


70 January 2014

- SAP_SV_SOLUTION_MANAGER_DISP (display authorization for all operations and operations

setup)

- SAP_OP_DSWP_BPM (in order to set up Business Process Analytics)

Users also need to access the Business Process Operations Work Center in SAP Solution manager in order

to work with Business Process Analytics. Therefore the following roles need to be assigned:

- SAP_SMWORK_BPM (in order to use Work Center: Business Process Operations)

- SAP_SMWORK_BASIC (basic role in order to use Work Centers)

In addition, each user needs to have either the role SAP_SM_BPOANA_ALL or the role

SAP_SM_BPOANA_DIS assigned to their user profile, depending on the user type he represents in

Business Process Analytics.

In the managed systems, each user needs to have either the role SAP_MANAGED_BPOANA_ALL or the

role SAP_MANAGED_BPOANA_DIS assigned to their user profile in order to access available business

data (e.g. detail list, execution of transaction ST13), depending on the user type he represents in Business

Process Analytics. The roles in the managed system are shipped with ST-PI plugin (first with ST-PI

2008_1_* SP06). In case these roles are not available in the system, all value and user specific business

data is not displayed in the tools.

Additionally, in case the user should be allowed to do manual analysis in the managed system, he should be

granted access to transaction ST13 and to the respective business transactions.

3.2.4.1 Template for: Administrator/Configurator: SAP_SM_BPOANA_ALL (Solution Manager)

The template role SAP_SM_BPOANA_ALL is used for both the Administrator and the Configurator. The

Administrator User has full authorization in all authorization fields (*). By default, the Configurator User has

the same authorizations as the Administrator User. For example, his authorizations can be restricted in the

following areas, according to his responsibility and tasks:

Analytics Details, e.g. the Configurator has access only to certain Analytical Functions, Application

Areas, Key Figures, or Systems/Clients.

Analytics Category Usage, e.g. the Configurator has change authorization for Variant Category A,

and change/delete authorization for Variant Category B and C.

Analytics Variants Usage, e.g. the Configurator can create, display, and change all Variants of

Variant Category A, and change, display, and delete Variant a,b,c,d,e,f of Variant Category B.


January 2014 71

The authorization object Analytics Configuration determines if the user is considered as

Administrator/Configurator (value 02) or as End-user (value 03). Only the Administrator/Configurator has

access to the free selection tab (see Figures 1 and 2). Furthermore, only the Administrator/Configurator has

the authorization to maintain connector instances and to access Business Process Analytics via the BPO

Dashboards for a specific analytical key figure which is defined in both tools.

The Configurator role is defined by maintaining the values of the following authorization objects included in

role SAP_SM_BPOANA_ALL, multiple entries per authorization object are possible:

SM_BPM_ACF (BPM: Analytics Configuration)

o Activity (Change (02), Display (03))

Activity 02 (change) identifies user as administrator/configurator

SM_BPM_ANA (BPM: Analytics Detail)

o SYSCLNT (accessible System(Client) as managed system),

o APP_AREA (accessible BPMon Application Area), e.g. ERP_SD

o BPM_OBJECT (accessible key figure), e.g. KPSD000101

o ANALYTFUNC (accessible Analytics Function), e.g. FREE_SELECTION,

BENCHMARKING, BENCHMARKING_ADV, BENCHMARKING_ADV_USR,

BENCHMARKING_ADV_QTY, BENCHMARKING_ADV_VAL, DETAIL_ANA,TREND_ANA,

AGE_ANA, AGE_ANA_QTY,AGE_ANA_VAL

With this authorization object, you can define for a specific system(client) combination which

analytical function could be executed with which key figures (application areas)

If analytical function BENCHMARKING_ADV_USR is granted, the user can see user-related

business data in the Advanced Benchmarking functionality in Business Process Analytics.

If analytical function BENCHMARKING_ADV_VAL is granted, the user can see value-related


SM_BPM_CDS (BPM: Analytics Category Usage)

o Activity (Create (01), Change (02), Display (3), Delete (06))


72 January 2014

o KFVCAT (Name of accessible Analytics Variant Category)

These settings influence which key figure categories a user can see in tab “Key Figure

Variants” and “My recently used Key Figure Variants” and what he can do with them

SM_BPM_VDS (BPM: Analytics Variant Usage)



o BPMVARIANT (Name of accessible Analytics Variant)

These settings influence which key figure variants a user can see in tab “Key Figure



January 2014 73

Figure 31: Standard authorizations of role „SAP_SM_BPOANA_ALL”

Please note: an Analytics Variant Category is an organizational grouping of Analytics Variants. On

authorization level, differing Values can be maintained for different Variants and Variant Categories.

3.2.4.2 Template for Administrator/Configurator: SAP_MANAGED_BPOANA_ALL (Managed

System)

On the managed system, data collection can be executed manually by using report “tbi_reports” via

transaction ST13. In order to control access to direct data collection on the managed system, role

SAP_MANAGED_BPOANA_ALL was introduced that allows restricting authorizations on different levels.

Multiple entries per authorization object are possible.

Relevant authorization objects of role SAP_MANAGED_BPOANA_ALL are as follows:

SM_BPM_DET (BPM key figure display in Detail List)


74 January 2014

o APPARA_MS (Application Area (BPMon)): *

o OBJECT_MS (BPM: Object): *

o FUNC_MS (BPM: Analytical Function): *

Within this authorization object you can define which analytical function could be executed

with which key figures (application areas)

If analytical function “*” is granted, the user can see user and value related business data in

the Advanced Benchmarking functionality in Business Process Analytics and in transaction

ST13 – tbi_reports in the managed system.

The Analytics Administrator has in general full authorization in all authorization fields (*), while the Analytics

Configurator has customized authorization due to his responsibilities and tasks.

3.2.4.3 Template for End-User: SAP_SM_BPOANA_DIS (Solution Manager)

The standard role SAP_SM_BPOANA_DIS restricts the End-User to perform only basic Analytics

functionalities (Age Analysis, Benchmarking, Trend Analysis), and to only display Analytics Variants and

Variant Categories. Moreover, the End-user cannot see the free selection tab, but only the Variants and

Variant Categories he is authorized for. The standard role allows the End-user to see all existing Variants

and Variant Categories without restriction.

The End-user role can be adapted according to the user’s responsibilities and tasks by maintaining the

values of the following authorization objects. Multiple entries per authorization object are possible:


o Activity (Standard: Display (03))

Activity 03 (display) identifies user as end-user





January 2014 75

These settings influence which key figure categories a user can see in tab “Key Figure






These settings influence which key figure variants a user can see in tab “Key Figure



o SYSCLNT (accessible System(Client) as managed system),

o APP_AREA (accessible BPMon Application Area), e.g. ERP_SD

o BPM_OBJECT (accessible key figure), e.g. KPSD000101

o ANALYTFUNC (accessible Analytics Function) , e.g. FREE_SELECTION,

BENCHMARKING, BENCHMARKING_ADV, BENCHMARKING_ADV_USR,

BENCHMARKING_ADV_QTY, BENCHMARKING_ADV_VAL, DETAIL_ANA,TREND_ANA,

AGE_ANA, AGE_ANA_QTY,AGE_ANA_VAL

Within this authorization object you can define for a specific system(client) combination

which analytical function could be executed with which key figures (application areas)

If analytical function BENCHMARKING_ADV_USR is granted, the user can see user related


If analytical function BENCHMARKING_ADV_VAL is granted, the user can see value related



76 January 2014

Figure 32: Standard authorizations of role “SAP_SM_BPOANA_DIS”

3.2.4.4 Template for End-User: SAP_MANAGED_BPOANA_DIS (Managed System)

If the Analytics End-user should be allowed to perform data selection directly on the managed system, his

access can be restricted, e.g. to certain application areas or key figures. Multiple entries per authorizationobject are possible.

Relevant authorization objects for role SAP_MANAGED_BPOANA_DIS are:

SM_BPM_DET (BPM key figure display in Detail List)

o APPARA_MS (Application Area (BPMon)): e.g. ERP_SD

o OBJECT_MS (BPM: Object): e.g. KPSD000101

o FUNC_MS (BPM: Analytical Function): e.g. BENCHMARKING_ADV_USR,

BENCHMARKING_ADV_VAL

Within this authorization object you can define which analytical function could be executed

with which key figures (application areas)


January 2014 77

If analytical function BENCHMARKING_ADV_USR is granted, the user can see user related

business data in the Advanced Benchmarking functionality in Business Process Analytics

and in transaction ST13 – tbi_reports in managed system.

If analytical function BENCHMARKING_ADV_VAL is granted, the user can see value related

business data in the Advanced Benchmarking functionality in Business Process Analytics

and in transaction ST13 – tbi_reports in managed system.

This role needs to be assigned to the system user in the managed system which is used in

the corresponding SM_<SID>CLNT<CLIENT>_READ – RFC connection from Solution

Manager to get the data for Advanced Benchmarking and Age Analysis available in


3.2.4.5 Visibility of Solutions: SAP_SV_SOLUTION_MANAGER (Solution Manager)

A further possibility to restrict the access of a user is via authorization object D_SOL_VSBL of role

SAP_SV_SOLUTION_MANAGER. This authorization object determines which solution(s) are visible to the

user.

Steering the user authorizations through the visibility of solutions adds an additional level of distinction to the

authorization concept. According to the customer’s requirements, it might thus be useful to create more than

one solution for Business Process Analytics.

Authorizations object details:

D_SOL_VSBL (Solution Manager - Visibility of Solutions)

o Activity (Create (01), Change (02), Display (03), Delete (06),Assign (78)

o Solution

These settings influence which solution a user can see in the UI


78 January 2014

Figure 33: Excerpt of authorizations of role SAP_SV_SOLUTION_MANAGER

3.2.4.6 Example

The Configurator of a company is allowed to access all Analytics Functions. But he should only see

Application Area ERP_PUR on System/Client EP1/001, and Application Area ERP_SD on System EP2.

Furthermore, the Configurator should only see all key figures of Monitoring Object Sales Documents

(KPSD0001*) of Application Area ERP_SD on System EP2. They use SAP Solution Manager SMP for


The End-User should not be allowed to access the free selection screen at all, but can access the Analytic

Functions Age Analysis (AGE_ANA), Benchmarking (BENCHMARKING), and Trend Analysis

(TREND_ANA).

Both the Configurator and End-user should only see solution EXAMPLE_SOLUTION_1 (Object ID

000001234567890)

Relevant authorization objects and values are as follows:


January 2014 79

Configurator:

Role SAP_SM_BPOANA_ALL

SM_BPM_ACF

o Activity 02,03


o SYSCLNT EP1(001)

o APP_AREA ERP_PUR

o BPM_OBJECT *

o ANALYTFUNC *


o SYSCLNT EP2(001)

o APP_AREA ERP_SD

o BPM_OBJECT KPSD0001*

o ANALYTFUNC *

Role SAP_SV_SOLUTION_MANAGER


o Activity 03

o Solution 000001234567890

End-User

Role: SAP_SM_BPOANA_DIS

SM_BPM_ACF

o Activity 03


80 January 2014


o ANALYTFUNC AGE_ANA, BENCHMARKING, TREND_ANA



o Activity 03

o Solution 000001234567890

System user for read access

The system user SM_SMP which is available in the RFC-connection SM_EP1CLNT001_READ, needs the

following additional authorization in system EP1 (001):

SM_BPM_DET

o APPARA_MS: ERP_PUR

o OBJECT_MS: *

o FUNC_MS: BENCHMARKING_ADV_USR, BENCHMARKING_ADV_VAL

The system user SM_SMP which is available in the RFC-connection SM_EP2CLNT001_READ and needs in

system EP2 (001) the following additional authorization:

SM_BPM_DET

o APPARA_MS: ERP_SD

o OBJECT_MS: *

o FUNC_MS: BENCHMARKING_ADV_USR, BENCHMARKING_ADV_VAL


January 2014 81

3.3 Authorizations Use Case

Analytics Champion Inc. is a production company that is operating in two regions (EMEA, AMER). The

company is running their business processes on one SAP ECC system (AC1/001) which is connected to

SAP Solution Manager SMP. Analytics Champion Inc. is in the process of implementing Business Process

Analytics and would like to establish an appropriate authorization concept.

The global responsibility for Business Process Analytics is assigned to a single Analytics Administrator. His

tasks include the definition of the global Analytics strategy and granting authorizations for Configurators and

End-users. He has the complete view on all Analytics relevant data stored in SAP Solution Manager.

The Administrator wants to use Business Process Analytics for the three business areas: Sales,

Procurement, and Financials. For each business area, one Analytics Configurator should be nominated. The

configurator is responsible for setting up the data collection for Analytics in the Business Process Monitoring

set-up session (selecting and setting up key figures). His tasks also include the definition of Variants for the

End-users as key figure views on specific data in Business Process Analytics. The configurator view is

restricted to his respective business area, as configured by the Administrator.

According to the company’s global strategy for Business Process Analytics, the end-users are working with

specific variants that have been created according to the business area and region they are working in.

In summary, the roles and responsibilities of the different Analytics users are as follows:

- Analytics Administrator:

o assigning authorizations to configurators and end-users

o reporting of BP Analytics results (Advanced Benchmarking, Benchmarking, Age Analysis,

Trend Analysis, Value Benchmarking)

o creating new solutions

o global setup and reporting tasks of BP Analytics

o manual execution of all data collectors in ST13 on satellite system

- Analytics Configurators:

o selecting and setting up Analytics key figures for their business area

o defining Variants and Variant Categories for End-users

o assigning key figure categories and Variants to End-users

o manual execution of data collectors for selected business area in ST13 on satellite system


82 January 2014

- Analytics End-users:

o operational reporting based on the available variants in their working area

o manual execution for specific data collectors in ST13 on satellite system

In order to fulfill their responsibilities, the users need the following roles to be assigned to their user profile in

SAP Solution Manager SMP:

In order to work as an Administrator, the Analytics Role SAP_SM_BPOANA_ALL has to be assigned. The

Administrator has full authorization in all relevant authorization fields (*)










o KFVCAT (Name of accessible Analytics Variant Category): *


o SYSCLNT (accessible System (Client) as managed system): e.g. AC1(001)

o APP_AREA (accessible BPMon Application Area): *

o BPM_OBJECT (accessible key figure): *

o ANALYTFUNC (accessible Analytics Function): *




January 2014 83

o Activity (Create (01), Change (02), Display (03))

o Solution: *

Example of Authorizations for a Configurator (responsible for Sales):


SM_BPM_ACF








o KFVCAT (Name of accessible Analytics Variant Category): *


o SYSCLNT: AC1(001)

o APP_AREA: ERP_SD (ERP_PUR or ERP_FI for the other Configurators)

o BPM_OBJECT: *

o ANALYTFUNC *



o Activity: Display (03)

o Solution: *


84 January 2014

In order to get an overview of the roles needed to do the set-up of the data collection for Analytics in the

Business Process Monitoring set-up session (selecting and setting up key figures), please look at SAP Note

784752 for more details.

Example of authorizations for an End-user (using Variant SL_OVERDUE in Category EMEA)

This variant has been configured by the Analytics Configurator for business area Sales and limits the view on

the sales organizations in EMEA for key figure Overdue Schedule line items. Within this variant, specific

analytical functions can be used, without having authorization to see value and user information.

Role SAP_SM_BPOANA_DIS

SM_BPM_ACF

o Activity (Display (03))


o Activity (Display (03)

o KFVCAT (Name of accessible Analytics Variant Category) : EMEA

o BPMVARIANT (Name of accessible Analytics Variant): SL_OVERDUE


o Activity (Display (03))

o KFVCAT (Name of accessible Analytics Variant Category): EMEA


o SYSCLNT: AC1(001)

o APP_AREA: ERP_SD

o BPM_OBJECT: KPSD000303 (Overdue schedule line items)

o ANALYTFUNC: AGE_ANA, TREND_ANA, BENCHMARKING_ADV



o Activity: Display (03)

o Solution: 000001234567890 (available solution containing EMEA data)


January 2014 85

4 Data Growth and Housekeeping

4.1 Introduction

If you use Business Process Analytics productively, it is important to think about data growth caused in SAP

Solution Manager by executing key figures in the Solution Landscape. Data growth has a strong influence on

response time (query performance) in the user interface “BP Analytics” when executing analytical functions.

Our best practice is to have a clear housekeeping strategy right from the beginning of your productive usage

of Business Process Analytics. For the data collected for Business Process Analytics on daily/weekly basis

the following questions should be answered carefully:

- Which key figures should be collected because there is a need for them and how often?

- How long should the historic key figure data be stored and be available in Business Process

Analytics for further Reporting for each single monitoring object?

The measured values which are collected by key figures from the managed systems are stored as entries in

the Analytics Info Cube 0SM_BPMRH – that means each single execution of a key figure will increase the

number of entries there. According to our general experience, we face first performance issues in the

response time of Business Process Analytics if the number of entries in the Info Cube exceeds 30 million.

Business Process Analytics does not offer an automatically activated housekeeping mechanism from scratch

which deletes historic data on a regular basis. The requirements for housekeeping (so e.g. which data to

keep for how long for Analysis) are usually very customer-specific.

But Business Process Analytics offers the possibility to set-up and use an automated housekeeping process.

In this chapter it will be described how to configure this automated housekeeping process.

4.2 Influencing factors – data growth

First of all, we should describe which factors influence the data growth. If you configure and activate a key

figure for usage in Business Process Analytics, you need to specify how often this key figure should be

collected and which “Group-by-fields” for category/drilldown analysis should be available. Both factors

influence the data growth directly.

Our best practice recommendation in this situation is

- Please configure and “Activate” only key figures which are needed for your actual analysis target

- Please schedule a key figure as less as possible (e.g. for most business key figures collecting data

maximum once per day is strongly recommended).


86 January 2014

- Please check only the really required “Group-by-field” of a key figure. Please evaluate carefully

which “Group-by-field” is required. The more “Group-by-fields” are checked, the faster the data is

growing in the Analytics Info Cube 0SM_BPMRH.

The reason for this recommendation should be already clear - for each key figure execution and for each

value combination of its used “Group-by-fields” a measured value entries is written into the Info Cube – and

with this recommendation at hand you create as less entries in the Info Cube as possible.

Example:

Configuration of key figure “Overdue schedule line items” with “Group-by-fields” sales organization and

distribution channel selected.

If you have Sales Organization 1000 and 2000, as well as distribution channel 03 and 04 maintained in the

target managed system, you will receive for each key figure data collection four new measured value entries,

for each single combination of the “Group-by-fields” a single one.

Therefore we could estimate the following rule of thumb for a rough estimation:

KPI entries per week = # No. um executions per week

* values of generic parameter 1 (e.g. “Sales Organization” )

* values of generic parameter 2 (e.g. “Distribution Channel” )

* …..*

* values of generic parameter 20

4.3 Identifying total number of entries in Analytics InfoCube

If you want to estimate the number of entries in the Analytics Info Cube 0SM_BPMRH, you can check the

number of entries in the fact table of this Info Cube:

Enter Transaction SE16 and check table /BI0/F0SM_BPMRH. Via “Number of Entries” the number of entries

in the Analytics Info Cube 0SM_BPMRH can be determined.

4.4 Selective Deletion

A selective deletion of specific entries in the Analytics Info Cube 0SM_BPMRH – for example for a specific

monitoring object, a specific key figure or a calendar week interval is possible to reduce the number of

entries in the Info Cube or to remove data which is not needed any more in a manual step.


January 2014 87

Another use case of selective deletion might be the need to reduce the amount of data in the Analytics Info

Cube manually, because the automatic housekeeping is not executable due to the high amount of data in the

Info Cube (more than 100 million entries in the Info Cube). In this case, manual deletion would be a first step

in the housekeeping process which is followed by the configuration of the automatic housekeeping for further

usage.

The selective deletion is accessible via the BW administration workbench in the SAP Solution Manager

(transaction RSA1) and is described in detail within the following document “Dynamic Selective Deletion from

Infocubes” available at SAP SDN:

http://scn.sap.com/docs/DOC-12215

The additional data you need like monitoring id or technical name of a key figure used in Business Process

Analytics and be retrieved from the Analytics selection screen, if the display of technical names is turned on

in the user’s personal settings).

Please keep in mind that The Info Cube 0SM_BPMRH is a real-time Info Cube – you have to change its load

behavior from “can be planned” to “can be loaded” BEFORE you start selective deletion and from “can be

loaded” to “can be planned” AFTER you finished your deletion operation (WITHOUT writing the status

changes to a transport request) as described in the following screenshots:

Figure 34 a: Access the load behavior in the BW Admin Workbench


88 January 2014

Figure 35 b: Change the load behavior in the BW Admin Workbench

Figure 36 c: Temporarily status change must not be saved on a transport request

4.5 Automatic Housekeeping

The automatic housekeeping is a reorganization process on a regular daily basis which deletes automatically

historic data according to specified rules – for example “delete all data older than x days”.

The automatic housekeeping makes use of the functions from the Extractor Framework (EFWK) in SAP

Solution Manager and is described in detail – including configuration and maintenance – in SAP Note1514022 and the PDF document attached to it.

It is important to know that the automatic housekeeping process can only be used successfully if the Info

Cube 0SM_BPMRH has definitely less than 100 million entries. If this threshold is exceeded, selective

deletion from the Info Cube needs to be done in a first step before the automatic housekeeping should be

configured.


January 2014 89

5 Available BAdI for restriction of master dataload/descriptions for specific Semantic-Ids

5.1 Overview

Within Business Process Analytics, we offer a BAdI definition within an Enhancement Spot in Package

AGS_BPM_RI which can be implemented to exclude specific semantic-ids from loading of master data

(descriptions).

This functionality is beneficial in case you would like to avoid, for example, that customer names can be seen

in Business Process Analytics. In case you exclude the semantic-id ERP_KUNNR from master data load, all

users in Business Process Analytics can only see the customer numbers but not their names.

5.2 Implementation

If you are not familiar with the SAP Enhancement Framework which is used, we recommend reading the

related Weblog series in the SDN to get a more detailed description:

http://wiki.sdn.sap.com/wiki/display/ABAP/The+new+Enhancement+Framework+and+the+new+kernel-

based+BAdI

The important objects we are dealing with in the implementation of this functionality are

On SAP side:

Enhancement Spot (container for the enhancement options)

Enhancement option ( for example a kernel-BAdI definition)

On customer side:

Enhancement Implementation (container for the enhancement implementation elements)

Enhancement Implementation Element ( for example a BAdI implementation )


90 January 2014

So if you want to implement a kernel-BAdI, then you need an Enhancement Implementation, as the BAdI

cannot exist on its own. When creating the Enhancement Implementation, we need to supply the

enhancement spot. Once we have the link between the two containers, we can link our Enhancement

Implementation Element to the Enhancement option.

The easiest way to create an Enhancement Implementation is to call transaction SE80, choose the

Repository Browser, choose Package and enter AGS_BPM_RI and then double-click on the Enhancement

Spot:

In this figure, we see that the Enhancement Spot ENH_AG_BPM_RI has four BAdI Definitions. We double

click on the fourth BAdI Definition BADI_AGS_RI_MASTERDATA_LOAD and then on the button “Create

BAdI Implementation”. On the pop-up window “Select or Create Enhancement Implementation” we choose to

create a new one named Z_EI_AGS_BPM_RI:


January 2014 91

When prompted for a package, create a new one or choose an existing one. (The package assignment as

well as the first letter in Z_EI_AGS_BPM_RI reminds us that the enhancement implementation is the

transportable DDIC object.) We are then prompted to enter the name and description of the BAdI

implementation as well as the class, where we will write our ABAP coding:

If choosing to create a new empty class we get to the following screen:


92 January 2014

Here we see that our Enhancement Implementation Z_EI_AGS_BPM_RI contains only one BAdI

Implementation EIE_AGS_RI_MASTERDATA. We are finished with the difficult part, i.e. we have set up the

structure for the BAdI.

Now we only need to write the ABAP-lines. We double click on Z_CL_MASTERDATA_LOAD and then

double click on the method IF_BADI_AGS_RI_MASTERDATA_LOAD~ADJUST_SEMID_TAB where we

implement the coding:

After activation of the class Z_CL_MASTERDATA_LOAD and the Enhancement Implementation

Z_EI_AGS_BPM_RI, we are finished.


January 2014 93

6 Appendix

List of all 32 currently available Application Areas:


94 January 2014

List of all available Analytic Functions: