SAP Fiori Applications and Components
These are the main artefacts of flexible workflow in SAP Fiori applications:
My Inbox: can also be configured as:
An Outbox, showing tasks that the user previously completed. Very useful to follow the progress after approving (workflow log).
A Tabular view, showing task-specific attributes, such as plant, helping inboxes with many tasks to be sorted or grouped.
Application-specific views, filtering out tasks from other areas.
Manage Workflow tile: Each application area has its own view, so that there is no interference from or with other applications. This is part of the business roles.
Manage Workflow Scenarios: Helpful for importing and exporting between systems, as well as being used for applications, such as PLM for additional features.
Manage Workflow Templates: Sequences of steps defined by the customer, for example to rapidly build ad-hoc workflows in PLM.
Team and Responsibility Management to assign users to teams and assign their responsibility, as well as creating and managing teams.
Administration Tiles: An assortment of tools that a workflow administrator needs for day to day maintenance, such as dealing with tasks assigned to a colleague who has left the company.
The SAP Fiori Components are re-usable UI elements, incorporated into the business applications to ensure symmetry between the different applications using workflow. The workflow Instance Component, for example, show the progress and planned sequence of a purchase requisition workflow, and displays identically to show the progress of a Sales Quotation approval. This symmetry and familiarity help users working in overlapping processes.
The Workflow Types Determine the Way that a workflow is Defined and Executed:
Classical Workflow – the modeling and behavior is identical to SAP Business Workflows, such as SAP Business Suite.
Flexible Workflow:
Conditional Workflows – configured (strung together) in the Manage Workflow app.
Ad-hoc Workflows – Used, for example, by PLM where an engineer strings together a one-off sequence to determine the collaboration sequence of a change record.
Workflow Template – A static sequence of activities, selected and triggered by application logic (for example, Legal Contract Management – depending on the contract type), or as blocks added by the engineer in a PLM change record.
Comparison of SAP Business Suite and SAP S/4HANA
There are some differences compared the legacy releases of SAP Business Workflow in the SAP Business Suite with workflow in SAP S/4HANA. There are two variants of SAP S/4HANA: One is Cloud, and the other is On-Premise. The Cloud variant does not include the layers highlighted in green – the SAP Windows GUI, and hence the legacy Workflow Builder (transaction SWDD). Instead of a SAP Fiori app is used to configure the workflows, based on a delivered workflow scenario.
Note
Note
The Workflow Scenario Editor is used by SAP development to bundle the various workflow artifacts together so that they can be strung together later by the customer in the SAP Fiori Manage Workflows app or elsewhere (for example, Engineering Record).
This bundle (each workflow scenario) includes the step types, the agent determination rules (who does what), the conditions (which workflow or step is performed), the actions (for example, how to handle an approval being rejected, and the underlying business objects.
The scenario is typically modelled by the application.
In the application Manage Workflows, the workflows are configured (strung together) based on the kit defined by the workflow scenario. For example, a three-step approval process can be configured for a purchase requisition.
This is done by the Business Process Expert employee of the customer, depending on their business domain.
The metadata of the workflows, including the prioritization of the workflow, the status (active or not), and the validity date (for example, from the start of the next year), as well as deadlines are specified by the Business Process Expert during configuration.
Note
