With this blog post, I am going to give an example on how one can integrate three of SAP's products - SAP Asset Intelligence Network(AIN) , SCP Workflow Service on SAP Cloud Platform and SAP Fiori My Inbox, in order to orchestrate business processes.
There is a lot of content on SAP Community to get yourself familiar with SAP AIN , SAP Workflow Service and SAP Fiori My Inbox.
For the purpose of this blog, I am going to specifically talk about enhancing the Equipment creation process in AIN with data quality and governance. More often than not, businesses would like to ensure the data that is entered in the system go through multiple level of reviews and approvals before it is finally published as a master data record. As of today, creating an application in the Equipments app automatically publishes this data. Using SCP Workflow and the publicly available AIN APIs, let's look at how to create automatic triggers for reviews and put manual approvals in place.
Note: In the 1911 release of SAP AIN , it is planned to have better process control using OOTB workflow support. Do take a look at the roadmap.
The sequence diagram below explains the scenario and interaction between components.
Disclaimer: This is just an example on how to leverage these technologies and I am going to explain the process and personas in layman terms. It may not have the exact mapping with real world specifics. Also, there are some javascript hacks that I put in place while extending the application to integrate into My Inbox.
We have two personas in our process for the creation of equipment master record on a manufacturers side.
1. Creator creates a new equipment using the Equipments application.
.
2. Creator clicks on Publish which automatically triggers the data governance workflow.
Notice the popup : "Equipment approval workflow triggered".
3. On triggering the workflow,
4. Upon Approval of the task by the reviewer,
5. Creator can enter additional data and click on 'Publish'. This time around 'Publish' saves and publishes the master data record.
6. On click of 'Complete' , the workflow is completed.
In the next part of my blog, I will get into the implementation details for putting this together.
There is a lot of content on SAP Community to get yourself familiar with SAP AIN , SAP Workflow Service and SAP Fiori My Inbox.
Overview:
For the purpose of this blog, I am going to specifically talk about enhancing the Equipment creation process in AIN with data quality and governance. More often than not, businesses would like to ensure the data that is entered in the system go through multiple level of reviews and approvals before it is finally published as a master data record. As of today, creating an application in the Equipments app automatically publishes this data. Using SCP Workflow and the publicly available AIN APIs, let's look at how to create automatic triggers for reviews and put manual approvals in place.
Note: In the 1911 release of SAP AIN , it is planned to have better process control using OOTB workflow support. Do take a look at the roadmap.
Let's get started with a sequence diagram:
The sequence diagram below explains the scenario and interaction between components.
Disclaimer: This is just an example on how to leverage these technologies and I am going to explain the process and personas in layman terms. It may not have the exact mapping with real world specifics. Also, there are some javascript hacks that I put in place while extending the application to integrate into My Inbox.
Technologies Used:
- SAP Asset Intelligence Network
- Equipments Application
- User Authorization Application
- AIN public APIs
- SCP Workflow Service
- SAP Fiori My Inbox
- SAPUI5 Extensibility.
- Extend Equipment application for
- Triggering workflow on "Publish" action.
- Integrating the application into Fiori My Inbox. (I had to also introduce some hacks for the integration which might not be necessary in most scenarios)
- Extend Equipment application for
Demo:
We have two personas in our process for the creation of equipment master record on a manufacturers side.
- Creator (Originator) : responsible for creation of record and enriching the data upon approval of the structure by the reviewer.
- Reviewer : responsible for reviewing the data and either approving/rejecting the record
1. Creator creates a new equipment using the Equipments application.
.
2. Creator clicks on Publish which automatically triggers the data governance workflow.
Notice the popup : "Equipment approval workflow triggered".
3. On triggering the workflow,
- system creates a task for the "Reviewer" which he can view in Fiori My Inbox.
- Also, notice that the "Equipments" application is integrated into the detail view of Fiori My Inbox and displays details specific to the equipment for which the workflow is triggered.
- What you see also is a "read-only" version of the equipment data for review only.
4. Upon Approval of the task by the reviewer,
- system creates a task for the original creator of the equipment to enhance the data.
- Also, notice that the "Equipments" application is integrated into the detail view of Fiori My Inbox and displays details specific to the equipment for which the workflow is triggered.
- What you see also is a "editable" version of the equipment data.
5. Creator can enter additional data and click on 'Publish'. This time around 'Publish' saves and publishes the master data record.
6. On click of 'Complete' , the workflow is completed.
In the next part of my blog, I will get into the implementation details for putting this together.
- SAP Managed Tags:
| User | Count |
|---|---|
| 10 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
