The written process is incomplete
Local variants, workarounds, and manual controls stay invisible until somebody tries to execute the target design.
Migration readinessThe clean core you want. Without the fight you expect.
Duvo builds an evidence-backed process fact base across SAP, non-SAP systems, people, documents, handoffs, and workarounds before Explore begins. Fit-to-standard workshops start from what is real, and your SI starts from a confirmed backlog.
No system access needed to startOptional read-only SAP scanSAP and the work around itBPMN 2.0 XML exportCustomer-owned fact base
Before Realize
The blowups do not start in Realize. They start in discovery.
When the programme begins from workshops and an idealized process, the exceptions surface after scope, design, and SI effort have already hardened.
“Special” is not yet a disposition
A custom requirement can be valid, obsolete, or simply outside SAP. The programme needs evidence before deciding where it belongs.
The SI meter starts before the fact base exists
Senior workshop time gets spent reconstructing the current state instead of confirming the target process and implementation backlog.
Two operating layers
The work runs inside SAP and around it.
Code analysis and system scans can explain what exists inside SAP. They cannot reconstruct supplier portals, spreadsheets, email chains, calls, approvals, and judgment around it. A migration needs both layers.
Around SAP · business layer
Capture the process SAP never recorded.
Walkthroughs, interviews, and documents reveal the SAP steps, non-SAP work, local variants, manual controls, exceptions, and workarounds the target design must account for.
- No live-system connection
- Cross-market variants
- Roles, decisions, and exceptions
Inside SAP · system layer
Inspect the live system for visible gaps.
A bounded read-only workstream within the migration scope checks defined SAP datasets for data and configuration issues, then returns a risk-rated report with recommended remediation actions.
- Read-only OData
- ECC and S/4HANA
- Risk-rated action plan
Clean-core decisions
Three questions decide what belongs in the core.
The system can answer the first question. The business process evidence answers the other two. Together they turn “our process is special” into a decision the programme can govern.
What does the current SAP object or configuration support?
Use the appropriate code, usage, configuration, and data analysis to establish what the system is doing today.
Does the business still need the exception?
Test the requirement against the people who run it, the edge cases it handles, and the value or control it protects.
What never reached SAP at all?
Capture the portal work, spreadsheets, messages, calls, and approvals invisible to code scans and event logs.
Disposition
Every requirement gets one of four dispositions.
Flatten
Adopt the SAP Best Practice where the old exception no longer earns its keep.
Extend cleanly
Keep a genuine difference through sanctioned on-stack or side-by-side extensibility.
Retire
Remove obsolete process steps, controls, or custom requirements instead of migrating them by default.
Move to the edge
Keep special work outside the core in a human process, an existing tool, or controlled automation where appropriate.
Mapped to SAP Activate
Compress discovery. Give Explore a confirmed starting point.
Start with one consequential process, reconcile the variants, agree the dispositions, and carry a customer-owned model into the wider migration programme.
Map both layers
Capture the business process without system access; add a bounded read-only system scan where it is useful.
Agree the better process
Bring the business into the room, reconcile variants, and confirm what the target process must preserve.
Disposition the exceptions
Flatten, extend cleanly, retire, or move to the edge, with the evidence and rationale behind each decision attached.
Export and hand over
Move BPMN 2.0 XML and supporting evidence into Signavio, the SI workstream, or the internal design authority.
Keep the map live
Use the agreed process record through Realize and after go-live instead of letting discovery become a dead deck.
What one bounded read-only scan surfaced
The system evidence changes the conversation.
These anonymized findings came from one ECC scan across defined datasets. They do not describe every SAP estate; they show why migration scope needs system evidence alongside wider process discovery.
~95%
of finished goods missing a base price
0%
supplier confirmations recorded
1,507
open purchase-order items still unresolved
System scan workstream
Connect read-only. See where you stand in minutes.
No IT project, no install. A read-only connection to your live SAP, a scan across the areas where data and config quietly drift, and a report you can act on the same day.
Connect read-only
A read-only connection to your live ECC or S/4HANA through SAP’s own API. Nothing is written back, and there is no project to stand up.
Scan the live system
Duvo queries 49 data sets across master data, procurement, pricing, and warehouse, then measures each one against SAP’s own benchmarks.
Get a risk-rated report
Every gap is rated High, Medium, or Low and paired with the SAP action that fixes it. Minutes, not weeks.
What it reads
Where the gaps hide in a live SAP.
Duvo reads the live configuration and data across the modules where quality and config quietly slip, measured against SAP Activate, Clean Core, and SAP’s master-data quality targets.
Business Partner master
Tax numbers, bank data, contacts, roles, and completeness against SAP’s data-quality targets.
Customer (sales)
Sales-area assignment, dunning, partner functions, and classification.
Supplier (procurement)
Purchasing-org assignment, withholding tax, Ariba integration, and confirmations.
Product master
Finished-goods and component split, descriptions, sales config, and custom objects.
Procurement
Purchase-order activity, open items, pricing elements, and supplier confirmations.
Sales pricing
Base-price coverage, condition validity, tax conditions, and quantity scales.
Benchmarked toSAP Activate methodologySAP Clean CoreSAP master-data quality targetsSAP Best Practices and Notes
What a scan finds
Real gaps, risk-rated, with the fix attached.
A sample scan of an SAP system surfaced twelve gaps. The five below were rated High or Medium, each paired with the SAP action to remediate it.
HighProcurement
Supplier confirmations at 0%
Zero order acknowledgements on the latest purchase orders, against SAP’s 95%+ benchmark for critical materials.
Recommended action
Activate supplier-confirmation tracking on critical purchase-order items.
HighSales pricing
Base price missing on ~95% of finished goods
A base price is set on only 11 of 218 finished-goods materials. Without it, the system blocks standard order creation.
Recommended action
Run a bulk price change to create base prices for every active finished good.
HighBusiness Partner
Tax data only 29% complete
Tax numbers are present on 122 of 419 partners, against SAP’s 100% target, creating compliance and tax-determination risk.
Recommended action
Run the completeness check and enrich missing tax data through the governance workflow.
HighProcurement
17-month activity gap, 1,507 open items
No purchase-order creation for 17 months, with 1,507 open items still on the books. A likely freeze or migration event not reflected in the data.
Recommended action
Reconcile open items against goods receipt, then close or cancel stale orders.
MediumClean core
14 custom product groups, 9 custom materials
Custom-built objects sit outside SAP’s clean-core guideline, the rule for keeping custom code out of the system’s core.
Recommended action
Assess each custom object against the clean-core matrix before you scope the move.
What you get
A report your team can act on the same day.
Not a dashboard to interpret. A clear, benchmarked document: where you stand, what is at risk, and the SAP action for each gap.
01Executive summary
The critical findings up front
Every High-risk gap on the first page, in plain language the steering committee can read.
02Discovery log
Every data set, every count
The full scan: 49 data sets, record counts, what was accessible, and a key observation for each.
03Gap analysis
Risk-rated, with recommended actions
Each gap categorised, rated High, Medium, or Low, and paired with the SAP action to remediate it.
04Action plan
Sequenced across 30, 90, and 180 days
Immediate, short-term, and medium-term actions mapped to SAP Activate, so your team starts with a backlog, not a blank page.
SAP-native handoff
Built to feed the SAP programme, not fight it.
Duvo does not replace the system assessment, Signavio, or the SI. It supplies the missing process context and keeps the resulting fact base portable.
SAP system assessment
Run the code, usage, and readiness tools appropriate to your estate. Duvo process discovery answers the business questions those tools cannot.
SAP Signavio
Export the agreed process as BPMN 2.0 XML so the governance layer stays yours and the model enters the tool your programme already uses.
SAP Activate and your SI
Give Discover and Explore a reviewable fact base so fit-to-standard workshops confirm evidence and Realize starts from a clearer backlog.
Joule and standard SAP agents
Keep the process context usable as SAP expands standard agent coverage, so edge work can move back to standard when the business is ready.
What changes for the programme
The fact base changes who controls scope.
01
Fit-to-standard becomes confirmation
Workshops open on evidence: what each exception does, what it costs, and where the agreed requirement should live.
02
You own the fact base
The process model, evidence, and dispositions stay portable into Signavio and readable by whichever SI builds the target state.
03
Scope stays yours
Each surfaced requirement has evidence and a disposition. You decide what enters migration scope and retain the rationale for what does not.