New to Workflow in SAP S/4HANA – Release 1905
For Those Unfamiliar with Workflow in SAP S/4HANA
The wholehearted adoption of flexible workflow by the SAP S/4HANA applications is cause for celebration and cause for a new blog to coincide with the 1905 Release of SAP S/4HANA Cloud. Crystal-balls can reasonably predict that these features will be visible in the next SAP S/4HANA On Premise Release, too.
The S/4HANA 1905 Release News will describe the new adopters, such as the process for releasing Sales Orders, so this blog will only describe the technical changes from the flexible workflow point of view.
To recap, flexible workflow is the new capability engineered specifically for SAP S/4HANA, which uses some underlying SAP Business Workflow framework (such as the workitems, which you’ll still find in SWI1), but a radically different way of designing, executing and storing the workflow definitions. In a nutshell, the workflows are configured using the Fiori Manage Workflow Apps, and not in the Windows GUI Workflow Builder (SWDD). This allows a business process specialist to configure the workflows directly without technical assistance from basis consultants or the IT department – saving costs, and enabling full and dynamic control of the processes.
Fig 1: An SAP S/4HANA Workflow
(See images at the end of the blog for closeups or if you want to download images)
The screenshot shows a workflow created to release a purchase requisition item, and I’m sure you will see at a glance that this is a two-step approval, for purchase requisition items above 250€, where the second approval is only necessary for requisition items above 1000€. You may also spot that I have assigned the approvers by name, whereas in practice I’d probably use pools of users defined in the Teams and Responsibilities App, or the procurement-specific BADI.
The rest of this blog shows the enhancements that have been made to the workflow tooling. In some cases the enhancement is automatically available wherever workflow is used by the applications, in other cases the application has to enable the feature for their application in order for it be be available, and to avoid disruption. This means that not all enhancements described below are visible in all applications that already use flexible workflow.
Improvement – the Possible Workflows are Sorted by Ranking by Default
In SAP S/4HANA, rather than create one complex workflow to cover all situations, you simplify creation and also maintenance by configuring many small workflows, each to cover one situation. The precondition based on attributes provided by the application (or extensions that you have configured in your Cloud tenant) determine which of the individual workflows are triggered. Only the first matching workflow is triggered and the others ignored, so ranking plays an important role.
My pet nag was that sorting was not possible according to rank in previous releases. I’m very happy to say that this has now been corrected, and is now the default view.
Fig 2: The workflows sorted according to evaluation order.
Improvement – The Instance-View is Unrestricted
When a human workflow is launched, there is the inevitable suspense about what the final outcome is or how far it has progressed. SAP S/4HANA applications can embed the view of the workflow progress directly in their main application, irrespective of how the workflow has been defined in the Manage Workflow Fiori App. This allows anyone who is able to look at the original request to see how far the workflow has progressed, and what other steps are necessary before the workflow completes. Ergo – Process transparency!
Fig 3: The purchase requisition approval progress embedded in the purchase requisition itself.
This view has proved so useful that its enablement has been extended to allow it to be embedded in multiple views of the same object. So an application, such as Procurement, that provides simplified as well as professional views can embed the workflow progress in each of them.
Improvement – Final Comment Displayed in Progress View
Typical of an approval process, and nearly all the SAP S/4HANA workflows are approval or release processes, is that when the request is rejected, the approver can add a comment explaining why. Sometimes there is even a legal requirement for this. Because it is of such significance, the final comment is displayed in the workflow progress view as an active link so that it can be read.
Fig 4: The final comment is displayed – in this case the reason why the request was rejected.
Improvement – Deadline-Handling
Deadlines can now be specified when creating a workflow and the deadline is displayed in the workflow progress and also in the My Inbox app.
Fig 5a: The upcoming deadline displayed in the workflow progress indicator
Fig 5b: The overdue deadline displayed in the workflow progress indicator
Fig 5c: The overdue deadline displayed in the My Inbox
The deadline-handling is only available if the application has enabled it in their scenario, specifying what time-points are relevant. This is normally from the start of the process or the creation of each approval item in a multi-step approval, but it could also be more sophisticated and application relevant. For example, in the case of a (fictional) leave request, the timer could be specified as a week before the vacation requested is due to begin. This is then reflected in the Manage Workflow App, and the relevant timer can be selected.
Fig 6: The deadline timer can be selected when configuring the workflow in the Manage Workflows App.
The next screenshot displays the view of the developer who develops the workflow scenario. This is hidden from view to the SAP S/4HANA Cloud users, but should help explain the mechanism to those of you developing your own scenarios in SAP S/4HANA On Premise – treat it as a lab preview.
Fig 7: Behind the scenes with the workflow scenario development.
Improvement – Workflow Outcome Email Notifications
What was available in previous Releases, was that when a task (work item) is created, a notification is propagated by Fiori Notifications and also email (SMTP) to users that receive the task in their My Inbox, so that they are informed right away, even those users who only sporadically access their SAP software. In the 1905 Release an additional mechanism is available, if it has been enabled by the SAP S/4HANA application, so that emails are sent when the process completes. For example (fictional example), when a leave request is approved, the requester receives an email informing them that they can book their vacation. Alternatively, if the request is rejected, than an email with a different conciliatory text is sent to the requester.
Mail templates, one for each outcome, can be assigned to the workflow scenario, and each customer can adjust the text/layout according to their individual needs using the standard Output Management App. Once enabled, the business process specialist configuring the workflows can select who receives these messages. For example, those involved in a complex approval chain may need to be informed when the document is finally released (or not) so that they do not need to keep returning to the request to determine its status.
Miscellaneous Detailed Screenshots for Improved Viewing…
Fig 1: Detail
Fig 1: Detail
Fig 1: Detail
Fig 4: Detail
Fig 5: Detail
Fig 6: Detail
Fig 7: Detail
Good stuff as always! The email notifications with custom templates in particular plug a big gap in the S/4 workflows.
Yep Mike, I'm looking forward to this arriving in the On-Premise Release too, so experts like you can get their hands on it., too. Currently its use depends on whether or not the S/4 apps have enabled it in this release. So as I warned at the beginning, these features have to be adopted to become visible.
The small win of sorting by order pleases me too!
Thanks Alan for this nice blog as all your previous blog. Deadline is a really effective in business decision.
Anjan, I totally agree,
Thanks Alan for the great blog! Now the wait for the features to make their way to on premise....And be on a project to be able to use them...
How about approval scenario setup based on document chronology and their statuses e.g. I like to setup flexible Scenario like this;
This way it will enable us to deploy end-to-end release strategy from Sales Oder Approval until Billing Approvals.
I know, technically it is not possible yet since there are no possible start conditions available that establishes the link between documents from Sales Order to Purchase Requisition and onward to Purchase Order until Billing Approval.
Do I have to create my own custom flexible workflows (may be copy existing standard template) and create own custom start conditions? If yes, I would have do for all standard workflows to provide those start conditions that links one to the other. So It would not be possible to use standard workflow templates any more.
Is there any BadI option for start condition that I may use, in run time I would check the conditions using business document data.
Any comment would be appreciated.
Eventing enables this, It could even trigger a different workflow, if the requisition is changed significantly.
I think, it is just not enough. If I have to trigger manually one (Standard) or the other (custom) workflows by events, there won't be any use of standard Flexible Workflow Scenario in "Manage Workflow App" for Purchase Requisition, Purchase Order etc.
I should have made it clear that Manage Workflow handles the whole thing, including the internal eventing. You don't need to worry about a thing and certainly don't need to combine standard and custom workflows.
Maybe we need a blog about this.
Thank you for the Blog. This is very useful and concise information.
Are there any KPIs for Deadline-Handling?
Thank you Bindu,
What exactly do you need? Could you describe an example?
Here are some examples:
With Deadline handling, are there any measures that help to determine which Approvers usually miss the deadline for approval? Which suppliers are associated with the late approvals? Are the deadlines usually missed for Project (account assignment 'P') approvals instead of inventory?
Hope this is helpful.
Hello Alan, Bindu,
This is exactly what we are also looking for. We are on 1909 OP. Were you able to find a way to do this or did you develop a custom report?
That makes sense. You can create custom reports based on the CDS views associated with the workflow scenario. I.e. by combinding the generic CDS view for a workflow scenario, together with the scenario-specific view (e.g. procurement) you should be able to achieve this.
Thanks for the detailed inputs on using Flexible workflows. In our case, the requirement is to setup a workflow during Vendor Creation. But i don't see any Workflow for Vendor creation / approval post Vendor creation.
How can we approach such scenarios when there are no Flexible workflow available?
Appreciate your thoughts in this regard.
I believe there is currently no flexible workflow available for Vendor Creation but I'm happy to take this further. In which area of SAP S/4HANA do you see this need? Procurement for example?
Super post Alan. Thank you.
Hi Alan ,
Currently there is no flexible workflow for sales order approval(1809 on premise) . So can we create flexible workflow from scratch .
Appreciate if you can provide some inputs on this
It's already available in the SAP S/4HANA Cloud version. So you could predict its availability in the On-Premise Release, or there is nothing stopping you creating your own scenario.
Thanks for these good news, I have been working on S4H 1809 on premise and flexible workflow were hard to sell.
No deadline monitoring, sending an email after a rejection / final approval had to be done outside of the flexible workflow.
However there is one thing that I still don't understand, when I wanted to change a workflow definition in the old days I always copied the standard template, and everything was working fine.
Now with flexible workflow for purchase order per example, I had to make additional conditions I found a way with programmed binding to make it work on my workflow copy of the standard (in the programmed binding I generate my own class which is then available in the workflow container with all its attributes and method).
It works great except for the display on either the fiori apps or the ME23N transaction where the display of the process (agent) is not working, in me23n I have even found why the workflow template for purchase order is hard coded (include LMEGUICK7 class lcl_1241_view_mm method transport_from_model)
So my question is with flexible workflow if we want to modify the standard template is there an undocumented customising table somewhere to link a template to an object or do we have to modify directly the standard (and in this case what are the risk after an upgrade and if we apply a note ?)
Great to hear from you again.
You can extend a workflow scenario adding new condition attributes without having to copy the scenario. If I could figure how to append a file to this I'd upload a how-to presentation.
Applications should not hard-code the scenario ID into the code, but I agree this has happened on occasion and your input is useful input to development.
First, thanks a lot for this blog, it is very helpful to see the progress and "road-map" of this solution.
Anyway, I would like to ask if there is a plat to extend flexible workflow also for other business processes, i.e. sales document processing, especially sales quotation what is a very often document type relevant for approval. Or can this be covered by custom development, are there any limit to extend Flexible Workflow within this direction?
Thanks a lot!
Best regards, Pavel
The SAP S/4HANA roadmap should satisfy your needs.
And happily as you can see from one of my more recent blogs (process exceptions) sales documents are indeed supported.
Thanks a lot for your prompt reply.
I missed your blog about within process exceptions and also work with the information coming from S/4HANA Best practices 1809 OP where SAP_BR role consists only by Credit Memo request in case of Sales configuration. So is there a standard app for other sales document flexible workflow configuration in 1809?
Thanks & regards, Pavel
This comments section has somehow gone off-topic from 1905 features so I just wanted to let you know I can't reply here but suggest using the forum instead. That's where the experts gather ?? ??
All the best,
thanks a lot for this blog. You wrote to Stéphane Bailleul on 25th September about the possibility to add the custom conditions to the workflow scenario. Where can I find the how-to presentation?
It is really nice document, thanks for sharing.
Thank you for sharing nice blog on flexible workflow. However I have few queries:
Thanks for the explanation, our client needs to release in SAP just services entry sheet created from a plant maintenance order PR.
The rest, that are created from Ariba Buying, will be released in Ariba.
For that condition i need to add a custom logic to identify where the purchase requisition come from, is there any BADI to implement?
Great blog. Thank you for the good information.
Will it be possible for you to share the different Function Modules we have for us to work on any enhancements around Flexible Workflow?
We are trying to trigger the flexible workflow when Purchase Requisitions are created via MRP Live (MD01N) using the BADI MD_PURREQ_POST. But still having issues with this. Any insight will be of great help.
Is there a report which I can run which shows the status of all Requisition Workflow steps, so I can see in one report if an item is overdue based on the deadline management? I haven't been able to find an answer to this....
Do you have a consolidated place like a URL where I can get all I need to know about flexible workflows and start building them?
Also, I am more interested in how to leverage the flexible workflows to build something totally custom-like we do with classical workflows. Please help!
Is there any in-app extensibility possible in sap core for standard flexible workflows delivered?