Skip to Content
Hi Process Observer community,
Today I want to show you another interesting approach for applying process mining techniques on top of log information for your business processes created with Process Observer. To do so, we will use the open-source process mining toolkit ProM that is provided by the Process Mining Group, Eindhoven Technical University. In a follow up article we are examining Process Mining with Process Observer and Fluxicon Disco.
Although the current ProM version is 6.2, we are using version 5.2, as some of the functionality that is used is available only in this version. You will find the link for downloading ProM 5.2 at together with some samples and documentation. You can find the latest version of ProM at
To export Process Observer log data from your SAP Business Suite system, you can use sample report POCR_LOG_MXML_EXPORT (or use transaction POC_LOG_MXML_EXPORT). For information about the installation of the report in your system, see note 1832016 (and update note 2011730). The report allows you to the specify start and end date and time as well as the Process Definition relevant for the export. Using further options, you specify exporting only those processes with the status ‘finished’, extract further Business Object (BOR) attributes – which may be useful for a more in-depth analysis in ProM, and to delete user information during the export.
In this example, we are exporting logged data from procurement processes, as defined in Instrumentation for Procure-to-pay process on item level in Process Observer.
The result is stored as a file in Mining eXtensible Markup Language (MXML) format on the local PC.
The exported file structure looks like this:
It is then imported for further processing in ProM using the ‘File – Open supported File…’ functionality of the ProM Workbench. Chose the import plugin for ‘MXML Log reader’.

The imported file is now visible in ProM and immediately allows you to see some statistics for the imported processes, therefore check the ‘Dashboard’ and the ‘Summary’ view. Note: The process observer instances are referred to as ‘cases’ in ProM, while ProM’s ‘events’ correspond to activities in Process Observer.

In the filter view, you can restrict your log even more:
The heuristics miner (path Mining – Log – Heuristics Miner) returns a model of the process execution and gives information about the frequency of the activities and transitions:
One way of  identifying process variants, is to create Markov Chains by selecting the ‘Sequence Clustering’ plugin in the Analysis menu. You can
then further inspect or view the created Markov Chains:
Alternatively, you can identify the most frequent path alternatives with their throughput times running the ‘Performance Sequence Diagram Analysis’ in the Analysis menu:
Finally, I would like to show you how you can identify paths that, on average, take too much time, the critical sub-paths, or the routes using ProM. To do so, you use the heuristic process model described above, and use the ‘Conversion – Heuristic – Heuristic Net to Petri Net’ function to get a Petri Net as a result. Then run ‘Analysis – Petri Net Model – Performance Analysis with Petri Net’, set the ‘Times Measured In’ to an appropriate value. Steps with long durations / high waiting times are now marked in purple:
When reviewing the ProM tutorials and playing around with the tool, you will find that you can do a lot more mining and analysis around your process logs, such as evaluating organizational-related information of the process, activity sequence, conformance checking, decision point analysis, and so on. Note that size of data sets that can be processed with ProM is limited; you may need to limit the data size of the export accordingly.
The ProM Toolkit has proven to be a useful and very versatile tool for process analysis with Process Observer. I hope this little introduction has given you some ideas, and I’ll be happy if one of our followers gives an example in their blog about how they’re mining and analyzing data.
Some disclaimer about the ProM Toolkit itself: It is an open source tool for which SAP takes no responsibility. The above article is for illustrative purposes only how it could be used in the Process Observer context.
Thank you for staying tuned to this series!
To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Tobias Trapp

    I love this blog entry because you bridged the gap between SAP technology and Open Source using XML technology. Moreover MXML possess extensions using semantic technologies and  I guess one could build awesome applications with it.

    But I have some remarks: OSS note 1832016 is not released externally. I found POCR_LOG_MXML_EXPORT in NW 7.31 SP 8 but without any example process I don’t get any results. So my question is: Is there an example process (SPFLI?) so that we can start using process observer?

    Best Regards,


    1. Bernd Schmitt Post author

      Hi Tobias,

      thank you for the hint. OSS note 1832016 wasn’t released by accident, but it is available now to the customers.

      Together with with Process Observer we are delivering a number of example process definitions that you can review and activate in transaction POC_MODEL.

      In detail:

      – ‘SALES ORDER PROCESS’ a very simplistic Sales Order Process (see also Monitor Sales Order Processing with Process Observer for Built-In Processes (POB))

      – ‘PURCHASE ORDER PROCESS’ a very simplistic Procurement Process

      So they are our SPFLI samples.

      – With OSS note 1813249 we delived a more sophisticated Procurement Process ‘PROCURE_TO_PAY’ which allows process tracking on item level and is a template for real productive usage. More information about this PROCURE_TO_PAY process, the predefined activities and KPIs can be found at Instrumentation for Procure-to-pay process on item level in Process Observer.

      Best Regards,


  2. Edison Lim

    Hello Bernd,

    I am interested in this and tried to create report POCR_LOG_MXML_EXPORT. Then, I found structures like  poc_s_workflowlog,  poc_s_process_export, and  poc_s_processinstance do not exist. The program is not compiling. What am I missing?

    Thanks and best regards,


    1. Bernd Schmitt Post author

      Hi Edi,

      please open an OSS ticket for component CA-EPT-POC, then a colleague can look at this. I assume the information about the creation of the structures is missing in note 1832016.

      Thank you and regards,


  3. Asma Siddiqa

    Hello Edision,

    Could you please raise an OSS ticket  for the component CA-EPT-POC as Bernd had pointed out earlier.

    We would need this ticket for our reference.

    Best Regards,



Leave a Reply