Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
TomCenens
Active Contributor

As part of my blog series on SAP Solution Manager 7.1 features and functions, I decided to write this blog post to give a high level overview of the steps needed to set up Business Process Monitoring in SAP Solution Manager 7.1 (used SP12 here). It’s not my intention to detail everything out in this blog post but instead give a view on which high level steps are needed in terms of configuration.

For a detailed setup overview, check out the great presentation (BPM setup roadmap 81 pages) that you can find in the media library on https://service.sap.com/bpm or through the presentation material on business process operation - business process monitoring in https://service.sap.com/rkt-solman.

In a previous blog post on getting started with SAP Solution Manager I explained briefly the initial steps to get started with SAP Solution Manager. For Business Process documentation, as a prerequisite, you have performed the system preparation, basic configuration for SAP Solution Manager and the managed SAP system setup for the SAP systems involved in the monitoring scenario.

Quick configuration steps cheat chart


First step: preparation for the Business Process Monitoring scenario through SAP Solution Manager: Configuration workcenter


You start with the guided procedure for Business Process Monitoring  which you can access via the menu in the Solution Manager Configuration workcenter (or transaction SOLMAN_SETUP which is the same in the end).

This guided procedure will help you to get the prerequisites in place to set up a Business Process Monitoring scenario.

Prerequisite notes are checked for example during this guided procedure (via RTCCTOOL) and the detail log (link show) will show you what is missing in terms of SAP notes to ensure you have the latest corrections implemented.

Prerequisite before setting up a business process monitoring scenario


You need business process documentation in a solution within SAP Solution Manager (a structure that represents the business processes & business process steps) in order to do business process monitoring.

There are multiple ways you can achieve this but I won’t cover them all in this blog because it would take this blog too far off topic. If you already utilize business process documentation, you can leverage what you have already build. Otherwise, if you want to set up a simple Business Process Monitoring scenario (let’s call it a test) it doesn’t have to take a lot of time to get started.


You can create a Solution Manager implementation project using transaction SOLAR_PROJECT_ADMIN.  The minimal configuration there is that you give the project a title, you choose the language and you insert the logical components in the system landscape tab which represent the involved SAP systems for the business process steps.

Once that is done, you can create a business process structure using transaction SOLAR01. Once your structure is ready (just keep it simple to start) you need to insert the structure into a solution. That’s done using transaction SOLMAN_DIRECTORY. If you don’t yet have a solution, you also need to create a solution, this can be via the SAP Solution Manager Administration workcenter.

Setting up the business process monitoring scenario

In the business process monitoring setup, you continue the setup (follow the steps, hit create and follow through the configuration) and you can configure business process monitoring against business process steps.

After you run through the configuration steps, you can see the monitoring overview in the Business Process Operations (new) workcenter under Business Process Monitoring. Recently introduced is integration into the Monitoring and Alerting Infrastructure (MAI) which makes the technical architecture and the look & feel of the scenario, the same as for Technical Monitoring.



3 Comments
Labels in this area