Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
This is the third part of a Blog Series, where I will guide you through how you can leverage oData Services to load data into SAP Signavio Process Intelligence to investigate your Business Processes. As an example, we use S/4HANA Cloud as a source system and load data via oData Connector from SAP Signavio Process Intelligence.

The steps will be split into several posts (links will be added as soon as all blogs are published):

In the parts already concluded, we did setup the Communication Arrangement in S/4HANA Cloud (Public Edition) and the connection & source data in SAP Signavio Process Intelligence. We are now able to consume data from our oData Endpoint and load it into SAP Signavio Process Intelligence and use it there.

Add to Pipeline

As mentioned in the first part of the series, let’s imagine our Business Scenario is an investigation on “Procure To Receipt” Process, we already have Purchase Order Data extraction but want to add now the “Goods Receipt” for respective Purchase Orders. As you can see below, we already have Purchase Order Data collected. So, let’s add the “Goods Receipt” Data via the “Material Documents” information

Add connection and Source Data

As we still working on consuming data via an oData connection, we go to tab “Other” and pick again the oData protocol.

Add connection - oData Protocol

Now we can pick out of the source data which is already configured. So, we pick the “Material Document” connection we created in the last blog.

Add connection - Add created Material Document

With that, we did in principle add our “Material Document” data to our pipeline – so multiple data sources into one data pipeline.

Pipeline after adding Material Document

Extend the Business Object

In a next step, we need to extend our Business Object “Purchase Order” – we want to add the Goods Receipt as an event in the pipeline. We click on the “Process data model tab”.

Extend Business Object Purchase Order

We see, there are already two events created out of our Purchase Order Data: “Purchase Order Creation” and “Purchase Order Change (last)”. We click on the three dots and choose “Edit” and “Add event collector”.

Add new event collector

We give the collector a name and now need to implement the logic for our event log for “Goods Receipt” event. We need to specify the case_id, the eventname and of course the (event)time. Please note that this is only a simple example, of course more logic can entered into the SQL code. As we have header data and item data, we as well join these two tables to be able to consume both.

Add event Goods Receipt

After saving, we can run T&L (we did already extract the data in our second part of the blog – so no need to extract again). We can monitor the progress in the pipeline logs below the pipeline overview.

Create Investigation

As a last step, we can now add an investigation to our Process. We can click on our Process “Procure To Receipt” to navigate to the Process itself.

Go to process

On the next screen, we can create a “New Investigation”.

Create new investigation

We need to give a name, define the parameters and the Process Intelligence is creating the investigation for us. If we want to add a conformance check, we have the possibility to map our events to the To-Be BPMN Model of our process. Let’s pick the default “Average Cycle time” for the metrics bar. With “Go to Investigation”, we can enter the investigation.

Define investigation

The Process Discovery is created automatically, and we can now start to investigate the cases, add additional widgets and leverage the capabilities of SAP Signavio Process Intelligence. (Note: for this example, no data validation has been conducted)

Process Discovery

That concludes the series. We have created a Communication Scenario in S/4HANA Cloud (Public Edition) and exposed a respective oData Service, then connected SAP Process Intelligence to this service and configured the data extraction. We did add this to our Business Object as a new “Goods Receipt” event and finally did an exemplary investigation on the Process.

I hope, this series was helpful for some of you and provided you a starting point into SAP Signavio Process Intelligence.

Like what you’ve read? Feel free to share on Facebook, Twitter, or LinkedIn using the super-easy share buttons at the bottom! And don’t forget to follow SAP Signavio @ SAP Community for more content like this.