Workflow & automation

SAP workflows that work in everyday business

We design and implement approval and workflow processes in SAP, from the SAP standard through targeted extensions to individual scenarios. The Flexible Workflow is our speciality: configured in the standard, extended for your exceptions, clean-core compliant.

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 case actually needs.

Configured in the standard

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.

Built entirely ourselves

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 use of it.

Mapping your approvals as they are. 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 runs on figures rather than opinions.
Designing the scenarios. Levels, conditions, amount limits, substitutions, escalation and deadlines, configured in the standard 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-ready.

1
Check the standard
We first check every requirement against what the SAP standard can do.
2
Extend sensibly
Where the standard is not enough, we rely on clean extensions that stay as upgrade-ready as possible.
3
Recommend clearly
We recommend the solution that makes sense technically and for the business, not the one with the most development effort.

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 confirm them blind.

Nobody knows where it is stuck

The document says „in approval“, but with whom, since when and why is written nowhere. So people start phoning around.

No substitution arranged

Holidays, illness, someone leaving. With no 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