Skip to Content
Author's profile photo Bernd Schmitt

Architecture of Process Performance Monitoring in S/4HANA

In the first blog post about Order Order-to-Cash Performance Monitoring in S/4HANA we introduced the performance monitoring for order-to-cash processes in the S/4HANA Cloud & On-Premise Edition . This post discusses the architecture and concepts that are used.


The following diagram illustrates the components used and the content delivered:


Process Observer is used for the recording of the process execution in the S/4HANA system. The following content was created for this purpose:

1. Process Configuration:

The relevant steps and performance KPIs are defined and added as a process definition to Process Observer. See:


2. Application Events:

BAdIs are implemented to events about sell from stock execution.


The recorded process information is stored in Process Observer’s process log.

We define an analytics layer on the of the process log using Open CDS views.

For the UI visualization; we use:

3. Consumption View:

A join combining application data with process KPI data. It provides attributes for drilldown and filtering. The consumption view is exposed as an OData service.


4. SAP Smart Business:

In SAP Smart Business we define KPIs, evaluations and drilldowns. Finally, the Smart Business evaluations are made available as tiles in the Fiori Launchpad.


The process is now ready to be monitored.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hello Bernd,

      Could you please help me in letting me know how Process performance can be configured in S4HANA 1709.It would help if you can provide some details


      Chandra Rekha

      Author's profile photo Bernd Schmitt
      Bernd Schmitt
      Blog Post Author

      Hi Chandra,

      the general process how you instrument your own process process is described in a sample here for SAP Business Suite:

      So actuall it is similar to its configuration in Business Suite. Implemantation guide was cleaned up a bit, so you may find the referenced configuration steps slightly moved.


      1. If you need new application events to be monitored as part of your process, add them as a "task" (combination of "business object type" and "task type") in the facade layer  (quick navigation with T-code POC_FACADE)
      2. Implement the new application events (in exit/BAdI) either using direct event API , or map an existing BOR event using transaction POC_BOR, or use the generic BOR event.
      3. If within your process instance the business object instance changes you must make sure that business object predecessor information is given.
      4. Define you process and its the activities, and assign the events to the activities.

      After activation, this should allow your process gets logged and can be reviewed in the process monitor (transaction POC_MONITOR).

      You get a standard configuration for O2C monitoring in S4HANA (for 1610 and higher), if you follow this given installation information.

      To some extent you can also adapt the delivered CDS views and Fiori apps to your custom processes, you find information here.

      Regards, Bernd