Introduce SAP EM as compared to Solution Manager's BPMon.
Business Process Monitoring is the proactive and process-oriented monitoring of a company's core business processes.
The goal is to maintain the health of a company's business processes by detecting and resolving issues as fast as possible - before they become critical for the business
Read FAQ on Solution Manager's BPMon here. See these useful blogs on BPMon: Functional Scope of Business Process Monitoring in SAP Solution Manager, Typical Use Cases for Business Process Monitoring in SAP Solution Manager
- Is known as Solution Monitoring in Solution Manager and uses the CCMS alert functionality
- Hands off data to SAP NetWeaver BI for process dashboard analytics
- Monitors the health of steps in a business process. e.g. If the response time for transaction VA01 has exceeded 10 seconds for more than 10 sales orders in the last hour then there may be a performance issue with the order creation step.
- The purpose of BPMon is to monitor critical points in the business process and evaluate their performance against pre-defined tolerances in order to uncover system issues before they become noticed by the users.
- It allows you to perform the above-mentioned monitoring across any process spanning your SAP landscape defined in Solution Manager.
- More suited to monitoring SAP NetWeaver suite
- Legacy SAP: limited to cross application and interface monitoring (ALE, IDoc, qRFC, BDoc)
- Non-SAP: Using the remote CCMS agent you can only monitor log files
- Process monitoring from a technical standpoint
- Generic Monitors:
- Background jobs
- Dialog performance
- Update errors
- Document volumes
- General Application log (SLG1)
- Interface Monitors:
- ALE/Idoc alert monitoring (per Idoc type)
- qRFC alert monitoring
- Bdoc alert monitoring (CRM)
- RFC availability monitorin
- SAP NetWeaver PI monitorin
- Customer specific Monitors:
- All alerts available via CCMS monitoring infrastructure
- Customer Exit in Application Monitoring Infrastructure
- Generic Monitors:
Supply Chain Event Management (SCEM) "is an application that supports control processes for managing events within and between companies." AMR Research, January 2000
- Monitors the status of an end-to-end process INSTANCE. e.g. The sales order 123 had to have a delivery created by 2PM today but it never did so it now has status "Delivery Creation Delay". In addition it monitors the data / measurements of a process instance itself to uncover further exceptions. E.g. If the product left warehouse A for delivery 123, via Carrier ABC for quantity 1,000 at temperature 32 deg F and it arrives at Warehouse B we can then check whether it arrived at the planned warehouse with the planned quantity (1,000) at the planned temperature (<36 deg F) using the correct carrier. If any of these differ then we may have uncovered a further exception.
- With SAP EM every instance of the business process is monitored regardless of whether it's in exception or not. Only the exception events are configured to trigger notifications or status changes.
- Monitors business events only - Not used for technical or system monitoring
- SAP EM receives events from SAP systems and non-SAP systems.
- SAP allows for users to access the data via a web dynpro with extensive authorizations and filtering built in to ensure only the correct people can view their applicable data.
- Process - Instance monitoring from a transactional data standpoint
In short BPMon is used to uncover bottlenecks at key points in your process with a focus on technology and system affectiveness whereas SAP EM is used to actually monitor the status of an end-to-end business process matching up the planned events and measurements with the actual events and measurements to uncover exceptions. Both tools uncover different exceptions at different levels but use similar mechanisms in alerts and workflows to notify people of these exceptions. They can be used in tandem and both would be beneficial to the business to highlight potential issues with the business.