It is important for the businesses to have a summary of what happened to executed business processes. Meaning the statistics i.e.the total number of business objects executed during a run; the behavior of each object, such as how many were successfully processed or how many ended with errors; what other messages were raised/issued which are not relevant to any of the processing objects. Businesses and users need more information in the alerts than just a single message. A single line message does not convey enough information on a business object (e.g. business partner, RFID, order number, etc.) moreover, it is impossible to store this information in every message logged into the system. Most applications are designed in such a way that they loop over a list of business objects and process them one at a time. The first message usually informs the user about the business object itself and then the system logs subsequent messages as the process goes on. It happens that an error message is raised at a very later stage of the process as compared to when the error has occurred. For example during a process, an information message was raised for a missing value which is not a required field at point A. Later on, this very same value is required and the system issues an error message at point B In this case, the error message is raised at point B that does not reflect the true problem. Here the message is clear that the business object cannot be processed at point B, but the actual reason is missing, even though that information is already logged in the system. The BPEM application will allow the system to raise an alert for this business object at the point A where the warning has occurred. Currently if a user try to view this information via the standard tool SLG1, he might not find that information at one place depending upon the way the messages are stored in the system. Usually one process generates several application logs for each type of messages raised during the execution of business processing (info, warning, error messages, etc.). Another weak point of the standard application log SLG1 is that the user for viewing statistics is uniquely dependent on special messages issued by the application without having the freedom of cross checking them all. In order to view the application log statistics, BPEM has solved the problem by extracting the statistics from the standard application log SLG1 using the generic tool EMMA (Enhanced Message Management Analysis) and delivering the information to the user in an organized manner. It is capable of displaying all the messages logged in the system for each processed business object with the option of including information that can be used for KPIs(e.g. starting & finishing time). BPEM is an independent standalone tool which offers three main components: 1. Message analysis BPEM offers a generic frame work where messages from all the business processes can be analyzed at one central place. There is no need anymore for navigating between SLG1 (application log), or WE02 (IDoc), or CRM middle ware, job log, system log, migration work bench, workflow, etc. (please see the attached slides). Messages are linked to the object for which it was raised during the application at a precise time and not independently. Additionally, BPEM offers a job statistical summary. 2. Case management A built-in case management that is uniquely based on customizing. Programming is only necessary if customizing does not offer you enough options. BPEM enables the creation of manual and automatic cases. The automatic case resolution option allows the resolution of a case as soon as it is created. Automatic distribution list based on rule/role resolution. 3. KPIs KPIs measure the business processes at the user level. Other benefits are: Searching the history of a business object over a period of time: you can view how many times a particular message/problem appeared over a certain period of time. This information can be used to audit the system as well to audit the business processes. Any information stored in the system under the format of an SAP standard message (T100) can be displayed in BPEM/EMMA. It does not require that the processing application writes the application or not. BPEM/EMMA also handles workflows and IDoc. BPEM delivers some example of methods for workflows, IDoc, job logs and system logs. How does BPEM/EMMA works BPEM/EMMA only requires to know where the entry for the executed business process and the logged information are stored. This information is read into the frame work by implementing the appropriate class method for the provided interface. BPEM is an ESA enabled application. Each component can be customized and implemented based upon the customer’s needs. BPEM/EMMA has proven to enable customers in US, Europe and Japan to improve their business processes by reducing error and resolution rate by the automation of error detection and alert/case resolution. The KPIs are mainly use to measure the performance of the business processes.