Workflow & automation

SAP workflows that work in day-to-day use

We design approvals and workflows in SAP, from the standard Flexible Workflow to targeted extensions and custom scenarios.

Arrange a conversation What we do

How far we go

Flexible Workflow on three levels

Most organisations use a fraction of what the Flexible Workflow can do and reach for custom development for the rest. We work on all three levels and tell you which one your situation actually needs.

Configured in standard SAP

Activating scenarios, setting start conditions, defining step sequences and amount limits, determining agents by role or through Teams and Responsibilities, defining deadlines and reminders. All in the administration app, without a line of code.

Extended for the exceptions

When the delivered conditions are not enough: custom start conditions and custom agent determination through the extension points provided for it. Substitution, escalation, special approvals, different rules per plant or material type. We extend only where the standard provides for it.

Fully custom built

For processes where SAP ships no scenario, we build our own: our own steps, our own agent determination, our own tasks in the inbox, in the /M2D/ namespace. On the same workflow engine as the standard, so your users have nothing new to learn.

What we do

From the rule through to the document

We work with the standard first. The Flexible Workflow can do more than most organisations make use of.

As-is analysis of your approvals. Who approves, from what amount, in what order, and how much of that exists only on paper.
Measurement. Throughput and waiting times, rejection rates, workarounds. So that the discussion is about figures, not opinions.
Designing the scenarios. Levels, conditions, amount limits, substitutions, escalation and deadlines, configured in standard SAP wherever possible.
Visibility for the users. In the classic GUI too, where your teams actually work.
Testing and rollout. With the people who will use it afterwards, not just with the project team.

Our principle

Standard first. Extensions where they add value.

Not every requirement needs development. Where the standard is enough, we use it; where an extension adds value, we build it upgrade-safe.

Where it usually goes wrong

The workflow runs and gets bypassed

Too many levels

Every approval anyone ever asked for is still in there. The result is documents that spend a week in transit and managers who sign off blind.

Nobody knows where it is stuck

The document says “in approval”, but who has it, since when and why is often not immediately visible to the user. So people pick up the phone.

No substitution arranged

Holidays, illness, someone leaving. Without a substitution rule the process stops, and next time it gets bypassed by email.

No figures

How long does an approval take on average? How many are rejected, and why? Without an answer to that, every change is guesswork.

How long does an approval take at your company?

If you do not know the answer, that is already a finding. Let us talk about it.

Arrange a conversation