Configuring Subprocesses in SAP Build Process Automation
Modularising your Process Automations
As I have highlighted in my recent blog Introducing Subprocesses as Referenced Subflows in SAP Build Process Automation, you can easily modularize your process automation projects, create and reuse a set of common process activities in a subflow, and leverage them in one or across multiple master processes without duplicating efforts.
Today, I will describe how you can easily configure subprocesses as embedded and referenced subflows and dramatically simplify process models, thus increasing the understandability and clarity of your flows.
Configuration Ingredients of a Subprocess
In order to leverage subprocesses, you should consider:
- Subprocess Input to pass variables to the activities of the subprocess from the main process
- Subprocess Output to pass variables from the subprocess to the main process
- Configuration settings to build embedded or referenced subprocess with an API Trigger
- Requires a 2-step approval for all hardware (Manager and IT Services) in Organisation 0002
- Allows an accelerated approval logic for any requests in Organisation 0001 <2.000€ and the Cost Center Owner approval is all that is needed
- Demands an advanced approval logic for all hardware requirements >=2.000€ with a multi-step approval logic.
- Requires as a standard in Organisation 0001, a Cost Center Budget Officer reviews all requests before a business rule automatically shall evaluate and provide the decision logic for the above business requirements.
Stage 1: The Main Process with 2 Subprocesses
Fig4: The above data type definition is leveraged for the business rules as well as the Subprocess Input und Output definition.
Stage 2: Creating an additional Subprocess
Let me now further modularise the pretty complex main process, as (a) the main process still features directly approval process logic for Organisation 0002 and hence some steps that are duplicates, e.g. the action to create a Purchase Requisition in SAP S/4HANA and the business validation form and email-notifications.
Fig8: I create a new subprocess for 0002 2-step approvals and delete all unnecessary process steps that can be omitted.
Subprocesses at Runtime
Fig14: I created multiple line-items to order a couple of MacBooks and selected Organisation 0001. The Cost Center Budget Officer is asked to review the request to check if this is in budget.
Subprocesses as referenced subflows are a powerful addition to our process automation platform, providing users with the ability to create and reuse a common set of process automation steps (workflows, forms and approval tasks, bot automations, business rules) across multiple processes. With Subprocesses, you can streamline your process automations, reduce the risk of errors, and simplify maintenance. In upcoming blogs, we will explain how to configure process visibility for subprocesses and how we plan to enable for-each and par-for-each loops, send back and exceptions.
For an update on regular release updates, please have a look at What’s New for SAP Build Process Automation.
We hope you enjoy using this new feature and look forward to your feedback.
Please note that the example that I use above is a simple demonstration example, covering a departmental pre-approval of requisitions before Orders are created in SAP S/4HANA. It is not intended to re-build any as-is business application functionality.