Handling Conflicts in Solution Documentation when using BPMon
In Solution Manager 7.2, the configuration of Business Process Monitoring (BPMon) is tightly integrated with the solution documentation. Usually, BPMon objects are created in the Operations branch and never released from there. This can lead to conflicts if the monitored business processes are changed in the Maintenance branch or Development branch and the change should be released.
The overall proceure in this case is as follows::
- Create business processes using the Development branch or Maintenance branch. You can also create business processes in the Operations branch directly in case the processes should be only used for monitoring and nothing else, but in most cases creating the business processes in the Maintenance branch or Development branch will be more applicable.
- Release the business processes from the Maintenance branch or Development branch so they become available in the Operations branch. Business processes created directly in the Operations branch should not be released to avoid all conflicts with the other branches.
- Configure BPMon for the business processes in the Operations branch. Generate and activate your monitoring. Do NOT release the configured monitoring objects.
- Some changes to the business processes (such as changing a step name) can be released from the Maintenance branch or the Development branch without problems. Other changes, such as the deletion of a step that has a monitoring object in the Operations branch, result in a conflict and cannot be released. In this case you have to identify the conflict and discard the creation of the monitoring object in the Operations branch. This will allow you to release the deletion of the step afterwards.
Wiki page https://wiki.scn.sap.com/wiki/display/SM/3.1.+Process+Management+with+BPMon explains in detail how to identify such conflicts and what to do in case you encounter such a conflict.