How to handle BPMON solutions during Solution Manager upgrade
This blog provides information about handling the BPMON solutions during upgrade of the Solution Manager (from 7.0 to 7.1), and will be useful for SAP functional and Technical consultants(Basis) consultants during Solution Manager upgrade, in case BPMON functionality is being used. There are a lot of other Solution Manager functionalities which must be tested, which is out of scope of this blog.
1. Pre-upgrade testing is Solution Manager Development system
Before the upgrade starts it is necessary to record the AS IS BPMON functionality. step Results should be recorded in both SOLMAN development as well as SOLMAN Production system.
In the development system, an existing active BPMON solution(if any) can be used for testing, or new solution created and activated. The Solution can be set up between SOLMAN Development and ERP UAT testing system, on account of data availability for testing. The idea is to test run the BPMON solutions in Development system, and eliminate all the Bugs in the test environment, in order to ensure minimal disruption in the productions system. Results must be recorder for the following scenarios: e-mail alerting, analytics and modification of KPIs and the threshold values.
The expectation post upgrade is to have the functionalities working in a similar manner post SOLMAN upgrade, though the steps to achieve the functionality may change.
2. De-activating of Solutions in the SOLMAN Development systems
Before upgrading the Solution Manager it is vital to deactivate the active Solution. If the upgrade is performed when the BPMON solutions are active it can result in technical issues, which will result in in-correct data collection post upgrade.
3. Upgrading Solution Manager Development system to 7.1 version
The Solution Manager will be updated by the Basis Technical team. As a part of the upgrade there are several activation steps that are required to be performed by the Basis team for activating the BPMON functionality. New authorization will be required to be given to BPMON consultants to run the solution as well as analytics reports in the upgraded version. We also need to do a minimum system requirements check from BPMON perspective and apply any patch upgrades or SAP note implementations as applicable. The details about the Basis steps as well as authorizations objects are specified in the link http://service.sap.com/bpm.
Once the Upgrade has been completed, the BPMON Solutions must be activated. The steps for activating solutions in SOLMAN 7.1 will be different from those in SOLMAN 7.0. For example, the transaction code DSWP is no longer available in the newer version of SOLMAN 7.1; instead we need to go through transaction SOLMAN_WORKCENTER.
4. Post upgrade testing in development system
It is required to test the scenarios specified above post upgrade and record the results. There may be some missing authorization issues, and new authorizations may be required to be given. If Basis team unable to fix all the issues, it may be required to approach SAP by raising OSS messages. All the issues faced and corrective actions taken must be recorded.
Once all the scenarios have been tested successfully, the next step would be to move the changes to production environment. Remember to de-activate the BPMON solutions in the production system prior to upgrade, for the reasons mentioned before.
5. BPMON Testing post upgrade in Solution Manager Production system
Once the SOLMAN production system has been upgraded, BPMON solutions must be activate in the production system. Required authorizations must be provided to BPMON users. After activation, we can proceed to complete the testing similar to the testing done in the SOLMAN development system.
It will also be required to train the end users for the new ways of working for managing and using the BPMON set-up. The BPMON solutions can then be handed over to end users.