Page tree
Skip to end of metadata
Go to start of metadata


In SAP Solution Manager 7.2 a new solution documentation and MAI as infrastructure for BPMon are mandatory.
When you upgrade your SAP Solution Manager from 7.1 to 7.2, you have to migrate your solutions. The migration consists of 2 parts – migrating the configuration storage as part of the solution migration and migrating to the MAI.

  • Migration to MAI
    If your solutions still use classic BPMon, you have to migrate your solutions to MAI. Remember that BPMon on MAI only works for managed systems with basis 7.0 or higher. If you already use BPMon on MAI for all your solutions in 7.1, this migration step does not have to be executed.
    You can choose when to execute the migration to MAI.  
    • Before the upgrade. This is the SAP recommended procedure.
    • After the upgrade as part of the content activation (overall solution migration).
  • Solution Migration (Content Activation) 
    For all solutions the solution documentation needs to be upgraded. This is called "Content Activation" and includes steps to be carried out before and after the upgrade. The migration of the BPMon configuration is part of this Content Activation. There are some manual activities (e.g. choosing the scope for the migration) and some automatic activities (e.g. technical migration of the BPMon configuration).

Migration for BPMon from 7.1 to 7.2.(Click picture to enlarge).

Before upgrading to Solution Manager 7.2 you should consider the impact that the upgrade has on your BPOps functions. While some functions will work as before in 7.2, for ithers the look and feel might change or a migration might be necessary. For details, please see the list below:

FunctionMigration requiredImpact of the Upgrade to 7.2
Business Process Monitoring (general)yes
happens via solution content activation and includes the migration to MAI and the

In general, BPMon in 7.2 works as it did in 7.1 (same monitoring functions available, similar detailed configuration etc.)

Switch of monitoring infrastructure (if classic BPMon was used before the upgrade) includes terminology changes (e.g. metrics) and changes in the way some consumption tools are used. Additionally, the data collection happens via the TMW destination for BPMon on MAI.

Changes in the general look and feel of some screens, user training required for the BPMon Setup and the BPMon consumption (major changes in the consumption come from the switch to MAI)

Changes in the authorization concept.

Changes to the BPMon Notifications layout.

Changes in the notification BAdIs may be required to ensure correct functioning after 7.2 upgrade.

BPMon Setupsee section "Business Process Monitoring (general)" Major changes in the BPMon Setup, end user training required
BPMon - Alert Inboxsee section "Business Process Monitoring (general)"

Switch to MAI results in a new alert inbox that behaves differently than the classic alert inbox. Here, end user training is required.

Minor changes if BPMon on MAI was already used in 7.1

BPMon - Monitoring Applicationsee section "Business Process Monitoring (general)"

New tool with BPMon on MAI, was not available like this for classic BPMon

Some canges if BPMon on MAI was already used in 7.1

Business Process Analytics

happens via solution content activation

additionally, twin cubes are mandatory in 7.2. For this, a separate data migration is required

Changes in the Setup require end user training.

Now changes for the consumption via Business Process Analytics.

BPO Dashboards displaying BPMon informationno migration possible

BPO Dashboards for BPMon information have to be manually reconfigured in the Dashboard Builder in 7.2. Old BPO dashboards for BPMon information will no longer work in 7.2

Note: BPO Dashboards for Analytics information will still work in 7.2

BW Alert Reportingno migration necessaryBW Alert Reporting only works for classic BPMon. For BPMon on MAI, this has been replaces by the OCC Alert Reporting. The upgrade to 7.2 has only a minor impact on the OCC Alert Reporting.

Migration Scenarios and Upgrade Paths

You have different options for migrating your BPMon configuration. Please see the attached presentation for your migration options.

Below you find the detailed description of the standard migration procedure. Please also refer to the presentation for content activation.

Detailed Migration Procedure (from BPMon Perspective)

Determine Scope for Migration

You have to manually decide which solutions will be needed in 7.2 and should thus be migrated. From BPMon perspective, these include:
    • Solutions with productively used BPMon configuration
      This means that the monitoring is active and users work with the alerts/metric information or the information is consumed via a dashboard.
    • Solutions with BPMon configuration that not yet used productively, but that will go live in the future (work in progress)
      E.g. if you currently have a project for the implementation of BPMon, the solution also needs to be migrated to 7.2.
There are two options to determine the BPMon related scope for the Migration:
Option 1:
On your 7.1 Solution Manager, execute transaction PREPARE_ACTIVATION and enter the guided procedure.

(Click picture to enlarge)

The guided procedure leads you through the overall preparation for the activation. Column "Business Process Operations" gives you an indication whether monitoring configuration exists in the solution.

(Click picture to enlarge)

Option 2:

You can also identify the scope via the solution list in the BPMon Setup. Solutions with a configuration icon contain BPMon or Analytics configuration. You have to decide whether this configuration will be needed in 7.2. If the configuration is needed, the respective solution should be included in the BPMon Setup.

(Click picture to enlarge)


Ensure Prerequisites before starting the MAI Migration on 7.1

The migration to MAI can already happen on 7.1. In order to do so, certain technical prerequisites have to be fulfilled before the migration can take place. 

  • SOLMAN_SETUP should be completed for System Preparation, Basic Configuration and Managed System configuration. Especially, the TMW
  • SOLMAN_SETUP completed for: MAI infrastructure (Section Application Operations ->System Monitoring), Business Process Operations.
  • Monitored systems should be on SAP_BASIS 7.0 or higher and ST-PI SP10 or higher.

Execute Migration to MAI

SAP recommends to migrate the relevant solutions to BPMon on MAI already in 7.1 if possible. This will save time in the upgrade to 7.2 since the migration to MAI is part of the critical path in the upgrade. The recommended migration procedure is:

    • Ensure technical readiness of Solution Manager for BPMon on MAI
    • Copy solution
    • Migrate copied solution via report R_AGS_BPM_MIGRATE_SOLU_TO_MAI
    • Activate the monitoring objects in the migrated solution
    • Deactivate the monitoring objects in the original solution
    • Deactivate and delete the original solution

MonIDs stay the same during the migration as of SP14 (on SP12 or SP13 implement SAP note 2345777 to ensure that the MonIDs stay the same), however, when you copy the solution, new MonIDs are created for the monitoring objects. If you follow the migration procedure above, dashboards that use the MonIDs as filter will not work after the migration and have to be manually adjusted. If you want to migrate to MAI, but want to keep your MonIDs, we recommend to use the following procedure:

    • Ensure technical readiness of Solution Manager for BPMon on MAI
    • Copy solution
    • Migrate copied solution via report R_AGS_BPM_MIGRATE_SOLU_TO_MAI.  This is a trial run to see if the migration will be successful and to get a feeling for the runtime of the migration.
    • Check the monitoring objects in the migrated copied solution. Activate the monitoring objects to see if you can activate. Afterwards, deactivate again, but keep the copied solution as a backup.
    • Migrate the original solution.
    • Activate the monitoring objects in the migrated original solution
    • Delete the copied solution

In case you do not want to migrate your solutions to MAI on 7.1, SAP recommends to do at least a trial-run for the migration in 7.1 to identify possible issues with the migration (e.g. incomplete configuration) before the upgrade to 7.2. If you do not want to upgrade to MAI on 7.1 the migration is part of the Solution Content Activation.
Please note: In case you want to use a new installation for Solution Manager 7.2, consider that between Solution Manager 7.1 systems, you can transfer BPMon configuration as part of the solution transfer. This transfer option is not yet available between Solution Manager 7.2 systems. Additionally, there is no option to transfer BPMon configuration between a Solution Manager 7.1 system and a Solution Manager 7.2 system. If you want to transfer BPMon configuration between Solution Manager systems, this has to happen on 7.1. All transfer involving a 7.2 system require the manual re-configuration of the monitoring on the 7.2 system.

For details concerning the migration to MAI on 7.1, check: Migration from classic BPMon to BPMon on MAI.

Upgrade to 7.2

After you have technically upgraded your SAP Solution Manager system, make sure that technically the infrastructures in Solution Manager 7.2 are ready to store the BPMon and Analytics configuration. For this, execute the steps in SAP Solution Manager Configuration (SOLMAN_SETUP), node “Business Process Operations” -> “Basic BPO Configuration” on your 7.2 System.

Especially important is that the MAI Content Update (Step 1.4. “Update Content”) has been executed and that the available monitors from the managed systems and from SAP Solution Manager have been loaded (Activity “Load Monitor Definitions” in Step “Configure Monitored Systems”)

SAP Notes to be implemented before the Content Activation

After you have upgraded your SAP Solution Manager system to 7.2, you need to implement the following SAP Notes before attempting the Solution Documentation content activation:

  • 2341333
  • 2333402
  • 2326286
  • 2366746

Execute Solution Documentation Content Activation on 7.2

The BPMon related migration is contained in the Solution Documentation Content Activation. To access, call transaction SOLMAN_SETUP and choose the relevant Post-Upgrade Activity.

 (Click picture to enlarge)

In the new screen, in step "Check Prerequisites", activity "Review Scope", you can review and change the scope for the migration (e.g. select/de-select solutions that should be migrated).

In the same step, in activity "Check Pre-requisites for BPMon Conversion" the system checks whether any of the selected solutions contain classic BPMon configuration. If such solutions are detected, the readiness of the MAI infrastructure to receive the monitoring configuration is checked.

(Click picture to enlarge)

In Step 2 "Activate Content", activity "Start Job for BPMon Conversion" you start a background job that converts all the BPMon objects into the format required in Solution Manager 7.2.

For monitoring objects configured for classic BPMon, this includes the migration to BPMon on MAI.

You can check whether the migration was successful via the following two steps:

  1. Check the logs in the content activation.
  2. In the solution documentation, randomly cross check for a couple of monitoring objects whether they were correctly created and assigned to the correct business processes.

Detailed information about the overall solution migration procedure (Content Activation) is available at Content Activation Wiki Page.

Note: After the completion of the migration, the monitoring objects are not active. You have to activate your monitoring objects before you can start using BPMon again.

Execute BPO Data Migration

In case you have used the classic Analytics cube in 7.1, you need to activate the Analytics twin cube and migrate your data from the old cube to the new twin cube. For this, activate the guided proceudre for BPO Data Migration.

Create Operations Branch

After you have executed the content activation, Best Practice is to manually create a branch of type "Operation" for your solution. This branch will allow you to easily configure BPMon on your productive managed systems. The branch can be created via tile "Solution Administraion".


  • Question 1: I'm currently on 7.1. We are planning to upgrade to 7.2 next year. Should I still configure Business Process Monitoring in 7.1 or wait until 7.2?
    • Answer: It depends on the upgrade path you choose and the urgency of your monitoring requirements. If you plan to upgrade the Solution Manager system, you can already start the configuration now, as the configuration get's migrated. It is recommended to use BPMon on MAI for new configurations (requires SP12 or higher)
      If you plan to have a new installation of the 7.2 system (instead of an upgrade), it does not make sense to start a full blown BPMon configuration in 7.1, as you have to manually reconfigure the BPMon configuration in the 7.2 system. In that case, monitoring configuration on 7.1 only makes sense for the most urgent monitoring requirements.
  • Question 2: I like the Solution Manager launchpad. Can I use this on 7.1?
    • Answer: The Solution Manager launchpad only becomes available with 7.2. On 7.1 you have to use the work centers.
  • Question 3: I have migrated to 7.2, but all of my monitoring objects are inactive. Did I do something wrong?
    • Answer: No. The monitoring objects are in status "inactive" after the migration. You have to explicitely activate the monitoring objects to start using them in 7.2.
  • Question 4: I have migrated to 7.2. All my monitoring objects are inactive. Can I find out which monitoring objects used to be active before the migration? 
    • Answer: No. At the moment, the information which monitoring objects were active before the migration is lost.
  • Question 5: If a customer directly upgrades Solman 7.1 classic BPMon to 7.2 via content activation migration steps, will the monitoring object be recreated internally, i.e. will the MONID of existing on Solman 7.1 still remain or will new MONIDs be created for the migrated monitoring objects? 
    • Answer: On SP12 or SP13, if you implement SAP note 2345777 or as of 7.1 SP14 (and in 7.2) the MONIDs do not change, when you migrate BPMon Classic to BPMon on MAI – unless you migrate the copied solution (a solution copy will assign new MonIDs to the copied monitoring objects).
  • Question 6: I have decided to include a BPMon solution with leading role "Quality Assurance" or "Development" in the content activation. Now I'm getting a warning "Solution ABC with BPMon for non-productive systems will not be included". What does this mean? Will the solution be migrated?
    • Answer: No. If the message reads "is not included", the BPMon configuration of the solution will not be migrated as part of the content activation. Please implement SAP Note 2391468 - Business Process Monitoring: Prepare Activation for Solution Documentation and afterwards repeat the step "Initialize list". Afterwards you will still get a warning that BPMon for non-productive systems has been selected for the content activation, but this time the BPMon configuration in the solution will be included in the content activation.

  • Question 7: I have upgraded to 7.2 and executed the content activation. If I check my monitoring objects, I find that the thresholds are gone. What do I need to do?
    • Answer: This is a bug. Implement SAP note 2288577 and repeat of the MAI repository migration by simply going into the SOLMAN_SETUP to solve the problem. 
  • Question 8: When I create the Operations Branch after the content activation, how can I copy the monitoring objects from the Production Branch into the Operations Branch?
    • Answer: You don't have to copy the monitoring objects. All relevant objects (including the business process documentation) should be "released" after the migration. This can either happen as part of the content activation or as a separate step after the content activation. After the release the monitoring objects and the business processes they are immediately available in all branches. If you create a new branch (e.g. an Operation branch) after the objects have been released, the monitoring objects and the business processes are also immediately available in this newly created branch.

  • Question 9: I want to include a solution in the content activation that has BPMon objects configured. But I don't really want to migrate these BPMon objects since I don't need them any more on 7.2. Is there a way I can run the content activation for this solution without migrating the BPMon objects?
    • Answer: No. If you don't want to include the BPMon Objects in the content activation, you have to delete the BPMon objects. If a solution is included in the content activation and the solution contains BPMon objects, these BPMon objects are migrated as part of the content activation (and exceptions in the BPMon migration halt the content activation).

  • Question 10: Do I need to have TREX installed in order to use BPMon?
    • Answer: Yes (if a non-Hana DB is used), in case they want to use a process diagram. Please keep in mind that TREX 7.1 is required for Solution Manager 7.2 which is currently only available on Linux and Windows.
  • Question 11: After 7.2 upgrade and content activation, will the process graphic created in 7.1 be automatically converted into process diagram in 7.2?
    • Answer: Kind of. There will be a process diagram in 7.2, but most likely you will have to manually adjust the diagram.

  • Question 12: If install a new 7.2 system and reconfigure BPMon, can the new 7.2  Solution Manager system work together with old 7.1 Solution Manager system for some time period to verify if the new 7.2 system can generate same alerts as in the old 7.1 system before deactivating the old 7.1 system? 
    • Answer: Yes. As long as the SID/installation number of the Solution Manager systems differ, a managed system can be monitored by more than one Solution Manager system. It does not matter whether these Solution Manager systems are 7.1 or 7.2.

  • Question 13: During the BPMon migration part of the content activation, do the managed systems containing the monitoring object have to be physically available?
    • Answer: It depends on the software status of your Solution Manager system. In earlier releases, this was required. Since this caused issues when managed systems had a down time at the time of the content activation execution, this was changed with later releases. The relevant coding changes were implemented already on 7.1 with SAP note 2513520. 

  • Question 14: How can I transfer my BPMon objects from a 7.1 Solution Manager to a 7.2 Solution Manager?
    • Answer: The only way this would be possible is if you upgrade the 7.1 system to 7.2 SP5 or higher and do the content activation as part of the upgrade for the solution containing the BPMon objects. Afterwards you can export the BPMon objects from the source Solution Manager and import them into the target Solution Manager (if the target Solution Manager is on SP5 or higher). There is no other option to transfer the BPMon objects between 7.1 and 7.2.

  • Question 15: The connectors BPM_AlCube (Alert Cube) and BPM_ATable (Alert Table) are no longer working in 7.2. Is this normal?
    • Answer: Yes. Those connectors connected to the classic BPMon infrastructure. Since this infrastructure is no longer available in 7.2, the corresponding connectors do not work any more.
      In case you were using these connectors for displaying BPMon information in dashboards, please note that in 7.2 the display of BPMon information in the BPO dashboards is no longer supported. Instead, use the cross-application dashboard frameworks Dashboard Builder or Focused Insights for creating dashboards displaying 7.2 information.

  • No labels