SAP Workflow and S/4HANA
During a recent webinar on the status of the Workflow customer connection program (a product improvement program organized by SAP), SAP reported that we can expect many more improvements around SAP Business Workflow in the coming years. It was stated that SAP Business Workflow is and will remain the standard tool for automating (approval) procedures within the SAP Business Suite. This also remains the case for S/4HANA.
Alternatives
Various methods and tools are available on the market for the graphical representation and implementation of business processes. Some of these techniques are bound to a technical platform, while others are platform independent.
If we look at the above, we first need to look at the alternatives offered by SAP in the area of setting up workflow procedures. Currently there are a number of deployable alternative technologies within the SAP product portfolio:
- SAP Business Workflow, also known as SAP Workflow ;
- SAP NetWeaver Process Orchestration;
- SAP HANA Workflow.
SAP Business Workflow
SAP Business Workflow is an ABAP-based workflow engine which is a standard part of SAP NetWeaver, the basic platform for the SAP Business Suite. SAP Workflow is a platform for configurable "human centric" processes and workflows. Within the framework of the various solutions within the SAP Business Suite (ERP, SRM, PLM, CRM, etc), there has always been a need for a tool with which tasks can be offered to the right people at the right time, with the right information. Usually these processes require multiple approvals and/or steps.
Important use cases where there is a need for predefined and repeatable approval processes that depend on complex rules are procedures for processing and approving purchase orders, ATB's, incoming invoices, declarations, leave requests, timesheets etc.
SAP Workflow offers standard options for managing SAP Business Suite data objects within the application packages (ERP, SCM, CRM, etc.) at low effort and cost. SAP Workflow is most effective when the workflow is limited to a single SAP instance where the application information is located within this SAP instance.
SAP Workflow is based on the ABAP stack, the standard development platform for the SAP Business Suite. This does not change as soon as one upgrades to the S/4HANA on-premise edition. Also within the new generation SAP business suite the application logic is based on the same SAP NetWeaver Application Server (ABAP Stack) as before. This means that one can continue to use SAP Workflow within S/4HANA as well.
SAP NetWeaver Process Orchestration
SAP NetWeaver Process Orchestration combines the power of SAP NetWeaver Business Process Management (BPM), SAP NetWeaver Process Integration, and SAP NetWeaver Business Rules Management into an integrated proposition. Unlike SAP Workflow , these components are based on the Java stack instead of the ABAP stack.
As a workflow engine, SAP NetWeaver BPM is particularly relevant. SAP NetWeaver BPM is particularly suitable for modelling processes that are executed in multiple SAP or non-SAP systems. SAP NetWeaver BPM is based on the standard BPMN (business process modelling notation) notation. The process models described in BPMN are directly executable ("model to execute") within SAP NetWeaver BPM. This in contrast to the more process descriptive tooling like ARIS. For the time being, these process models are more of a graphical representation and therefore fall under the principle of "Business to Model".
By using a tool such as SAP NetWeaver BPM one no longer has to make a translation to a technical implementation. The (possible) differences between blueprint and delivered functionality are a thing of the past.
SAP HANA Workflow
SAP HANA Workflow is a new solution for developing simple SAP HANA workflows. HANA Workflow is part of SAP Operational Process Intelligence. It is a light-weight workflow solution for SAP HANA-native applications.
SAP HANA-native applications are applications using not only the SAP HANA database, but also the SAP HANA extended application services (or SAP HANA XS), a simple application server and basic development platform within SAP HANA.
Which tool when
As a guideline, we can state that when choosing the workflow engine to be used, the most important criteria are where the data is located and the degree of interwovenness with the application.
When entering a selection process to choose the right process modelling tool, it is advisable to consider the following aspects:
- Level of detail ("business to model" or "model to execute")
- Systems (SAP or non-SAP)
- Process type(s) (Standard, new, dynamic, user interaction)
- Information requirement (Management, operational)
SAP Workflow is close to the Business Suite data so that relevant data can be accessed and changed easily and without interfaces. Processes that take place within one SAP solution and are closely interwoven with the application are outspoken candidates for optimization using SAP Workflow.
Choosing this solution does not mean that you cannot use modern user interfaces such as SAP Fiori. In fact, the current set of standard SAP Fiori apps are partly based on SAP Workflow procedures. This will also be the case within S/4HANA. There is even a special space reserved for SAP Workflow notifications, including link possibilities to the task. See the following screenshot of the control view of Fiori 2.0.
If you have set up a SAP Workflow procedure in your current SAP system, it will continue to function after an upgrade to S/4HANA, and can be modified and expanded.
Dynamic processes that are only partially, or not at all, supported by standard SAP are more suitable for NetWeaver BPM. In the case of processes that transcend the system, NetWeaver BPM will also be preferred.
SAP HANA Workflow is the right choice if the application is a native HANA application. For the time being, it is (still) possible to develop complex applications to a limited extent, but if the application is built entirely within HANA XS, it may be an option to use this workflow engine. So far SAP HANA Workflow only supports user decisions.
A combination of these tools is also possible.
For questions or additional information on this subject, please contact Sander van der Wijngaart.