Variants & frequencies
How many paths does an order really take, and which few carry most of the volume? Per subprocess, every variant is listed with count, share and cumulative share — rare ones too, each on its own line instead of a catch-all row.
Process Discovery
Processes as they really run
Process Discovery reconstructs from the document chains in your SAP system how sales orders actually run — from quotation through delivery and billing to cancellation, credit memo and return. Not the intended target model, but measured behavior, with every variant.
What Process Discovery shows
The first version covers Order-to-Cash — purely from document data, with no workshop and no parameters.
Cycle times
Per variant, the average cycle time in calendar days from the first step to the last. The time from contract to call-off is shown separately, so it doesn't distort the cycle time.
Pivot by SAP characteristics
Subprocess and variant against company code, sales organization, order type or item category — and by how an order came in: IDoc, automatic or dialog. A filter applies across all views and never changes the process model.
From document to process model
Three terms carry the module — the same ones Conjola explains inside the module.
One sales order
A case is a sales order with every document whose predecessor fields point to it. Documents without an order reference aren't discarded; they're counted in the header of the overview.
The sequence of steps
Orders with the same sequence of steps form a variant — say order › delivery › billing, or with a cancellation and a new invoice. Open orders are shown separately as “in progress”, with their age.
Process model as a tree
The most frequent variants up to 95% of completed orders make up the subprocess's process model: a shared beginning is one path, and where they part there's a branch. Each variant also has its own model.
Next up
From the measured process into the process catalog, into test management — and into purchasing.
Adopt into the process catalog
A subprocess is to be adoptable into the process catalog as a draft, with the steps from its process model. Conjola suggests the feature per step from the transaction; a person has to confirm it.
Test cases from variants
The variants covering 95% of orders are to become test case suggestions — with a real order of the variant as the template for the test data.
Purchase-to-Pay
Purchasing follows as a source of its own, on the same principle of case, step and variant.
Why from document data — not from workshops
Modelled processes show how it is meant to be. Document data shows how it is.
Facts, not a sample
The basis is your real documents — no interview, no assumption. That way even rare variants come to light that would otherwise trip up a project.
The same answer for everyone
No analysis run with thresholds: variants are updated with every import and are there right away. Two people asking the same question get the same answer.
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo