I have discussed BPM importing into OPInt scenarios and configurations in my previous blog SAP Operational Process Intelligence with SAP BPM – Visualization and Monitoring (Part 1).
1. Goal: Apart from the default sub statuses for Critical and At Risk of the Goal, we also can set the custom sub statuses using our process events. For example, I've created a sub status called ‘Waiting at Compliance’ using the referenced sub process’ start event. See below
Design Time:
Runtime: Whenever the process reaches the step compliance in the main process, the OPInt scenario instance will show that the current instance status is ‘At Risk’.
2. Attributes: We can add all or some of the reporting data source fields of the processes as an attribute. They will be useful to navigate to the particular instance of the process/scenario.
Design time:
As show in the above image, I’ve added some fields from the main process’ reporting data source and some others from the sub process’ reporting data source.
Run time:
3. Measures: We can define the measures to be used in Indicators. We can either import the measures from calculation views, or can create new count/duration measures.
For example, I’ve created count measure to count the total number of requests pending at compliance step, using the start of the Compliance step in the main process.
4. Indicators: As I mentioned in the previous point, Indicators will be created based on the measures.
For example, I've created indicator ‘Requests Pending Compliance’ based on the measure ‘Total Compliance Pending’. We can also configure the Target value for Indicator. So based on the target value, status of the indicator will be changed.
Design time:
Run time:
5. Actions: These actions will be available on the scenario details page. We can define the URI to navigate to a particular URL.
For example I’ve configured the Comprise IT URL, NWA BPM process and SAP Help. So a click of the link will navigate to the corresponding URL.
Design time:
Run time:
6. Checklist: We can define the Checklist and also can add tasks to it. These checklist are used in addition to milestone for the phase. So users have to complete the task to reach the milestone.
I've created a Checklist without any tasks to it. We will see how these will be used for additional milestones in other sections.
7. Additional Milestones: As I mentioned earlier, each phase will have two mandatory milestones one for start and another for end of the phase. Apart from these two, we can also define additional milestones either after the start or end milestones.
I’ve created 3 additional milestones using events of the Create Grp Process sub process and 1 additional milestone using the checklist after the start phase of the Product Creation phase
Milestone with Process event:
Design time:
Run time:
Milestone with checklist:
Run time:
8. Business Situations: This feature is used to identify the risk or opportunity in the business and alert/notify the user with details. Business situations use stored procedures to detect the risk or opportunity. We can put our own logic in stored procedure to identify the situation. If you want to understand more about business situations then please refer blog 1 and blog 2
I've used a very simple example to detect the situation. Detection mechanism will identify whether supplier ‘S85001’ is available in the data base table or not. Once the procedure identifies the value, then OPInt will alert user. User then can see the details and navigate to the configured uri and can complete the alert.
Design time:
Run time:
Alert:
You can also see my other blog on SAP Fiori Launchpad KPI tiles with OPInt - SAP Operational Process Intelligence with SAP BPM – SAP Fiori Launchpad KPI tiles (Part 3)
- SAP Managed Tags:
