What happens to SAP Business Workflow when you move from ECC to S/4HANA?

The engine survives the conversion. The approval design, the inbox and the in-flight work items are where the decisions sit.

By Chris Benson — 30 years in SAP SD6 min read

The short answer

Classic SAP Business Workflow still runs in S/4HANA: the workflow engine, the Workflow Builder, work items and agent determination carry over in a system conversion. What changes is everything around it. For several core approval processes, such as purchase requisitions, purchase orders and supplier invoices, SAP now offers flexible workflow, configured by business users in Fiori apps rather than built in the Workflow Builder, and the end-user inbox moves to the My Inbox Fiori app. Custom workflows that depend on changed business objects, such as customer and vendor masters replaced by Business Partner, must be found and tested, and in-flight work items need a cutover plan. Treat workflow as a fit-to-standard decision, not a technical carry-over.

Does classic SAP Business Workflow still work in S/4HANA?

Yes. The workflow runtime, workflow definitions, tasks, organizational agent assignment and the work item history all exist in S/4HANA, and a system conversion brings your workflow definitions across with the rest of the repository. A mature ECC estate usually has a mix of SAP-delivered templates, copies of those templates modified years ago, and fully custom workflows triggered by events or by custom code. All of that technically survives.

Surviving is not the same as being the right design. Many ECC workflows were built because the standard approval capability of the day was too rigid: a release strategy that could not express a cost-center rule, an invoice block that needed a second approver above a threshold, a master data change that legal wanted to see first. S/4HANA closes some of those gaps in standard, which makes each custom workflow a candidate for retirement rather than an automatic carry-over.

What is flexible workflow, and should you move to it?

Flexible workflow is SAP's newer approach for a set of standard approval scenarios, including purchase requisitions, purchase orders and supplier invoices, with coverage that SAP extends release by release. Instead of a developer building steps in the Workflow Builder, a process owner defines conditions, approvers and order of steps in a Fiori app. The approval logic becomes visible configuration that the business can read and maintain.

The question to ask of each existing approval is whether its rule can be expressed in the standard conditions available on your target release. If it can, moving to flexible workflow usually reduces custom code and makes the policy auditable. If it cannot, the rule either stays in a classic workflow or, when it is genuinely differentiating and changes often, moves side-by-side to a platform such as SAP Build Process Automation. Check the scope of flexible workflow for your specific release and scenario before committing; it differs by process and by version.

  • Rule expressible in standard conditions: move to flexible workflow and retire the custom template.
  • Rule is stable but not expressible: keep the classic workflow, then test it against the S/4 data model.
  • Rule is differentiating and changes often: consider a side-by-side approval that calls released APIs.
  • Rule nobody can explain and nobody triggers: retire it, after confirming usage in production.

Which custom workflows are most likely to break?

The risk concentrates where the workflow touches something S/4HANA simplified. Customer and vendor master workflows are the obvious example, because Business Partner is the leading object for both in S/4HANA, so workflows built on the old customer and vendor objects, events or change documents need review. Credit release is another, since classic SD credit management is replaced by FSCM credit management with its own documented credit decision and approval mechanism. Workflows that read changed tables directly in custom steps, or that are started from user exits, inherit every remediation those objects need.

Usage data matters as much as the code scan. Workflow event linkages are often left active long after the process changed, and some templates have not produced a work item in years. Counting work items by workflow definition over a full business cycle tells you what the business actually depends on, which is the list worth testing hard.

How should the inbox and agents be handled?

For approvers, the visible change is usually the inbox. The SAP GUI Business Workplace still exists, but the S/4HANA user experience routes approvals through the My Inbox Fiori app, with mobile access and approval actions on the item. That is a training and role-design topic, not just a technical one: approvers need the right Fiori catalogs and authorizations, and substitution rules have to be recreated or verified.

Agent determination deserves its own test cycle. Workflows that resolve approvers through organizational management, responsibility rules or custom function modules depend on master data that is frequently out of date in a long-running ECC system. A converted workflow that routes a purchase order to someone who left two years ago is a go-live incident waiting to happen.

What do you do with in-flight work items at cutover?

Plan to drain them. In the weeks before cutover, agree with each process owner which approvals must be completed, cancelled or recreated, and set a freeze date for starting new long-running workflows. Work items that span the conversion can behave unexpectedly if the object, task or agent rule underneath them changed, so the cleanest cutover is one where the open-item count per workflow is close to zero and every remaining item has a named owner.

Write the acceptance criteria before the test cycle: which approval scenarios, which thresholds, which approvers, and what evidence proves the right person received the right item. Where approval configuration itself changes as part of the migration, it should travel through normal customizing transports and your change board. Our own approach to agent-assisted configuration follows that rule: the agent drafts a governed customizing transport in a development system, the change board decides whether it lands, and nothing touches production on its own.

Frequently asked

Do we have to rebuild our custom workflows for S/4HANA?

Not as a rule. Classic workflows carry over in a system conversion and many will run after remediation of the objects they touch. The better question is which ones should be rebuilt as flexible workflow, moved side-by-side or retired, and that decision should be made per workflow using production usage data and the standard capability on your target release.

Is the classic MM release strategy still available in S/4HANA?

Release strategies remain available in S/4HANA on-premise and private cloud editions, and many organizations keep them through a conversion. SAP positions flexible workflow as the forward path for purchasing approvals, so plan the transition deliberately rather than by default, and confirm the current guidance in SAP's documentation for your release.

How do we know which workflows are actually used?

Measure it from the system. Count work items by workflow definition and task over at least a full business cycle, including year-end, and compare that list against active event linkages and custom triggers. Definitions with no work items in that window are retirement candidates once a process owner confirms they are no longer needed.

See your own Clean Core Score.

Run the free S/4 readiness scan in under a minute — no system access required.

Keep reading