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.
Decide what belongs in your SAP migration.
Combine business process evidence with a bounded SAP system scan, then agree what to keep, change or retire before migration scope hardens.
Reviewed migration decision
Your team agrees where each requirement belongs.
Flatten
Adopt SAP Best Practice.
Extend cleanly
Use sanctioned SAP extensibility.
Retire
Remove obsolete requirements.
Move to the edge
Run special work outside the core.
What each source covers
Capture cross-market variants, roles, manual controls and workarounds without a live-system connection.
Inspect defined datasets for data and configuration issues, with risk-rated findings and recommended actions.
How each requirement is reviewed
What does the current SAP object or configuration support?
Use code, usage, configuration and data analysis to establish what the system does today.
Does the business still need the exception?
Review it with the people who run the process, including the edge cases it handles and the value or control it protects.
What never reached SAP at all?
Capture portal work, spreadsheets, messages, calls and approvals that code scans and event logs cannot show.
A genuine difference can use sanctioned on-stack or side-by-side extensibility. Special work outside the core can remain a human process, use an existing tool or run through controlled automation. Obsolete steps, controls and custom requirements can be retired.
Compress discovery and give Explore a confirmed starting point.
- 01Capture
Map both layers
Capture the business process without system access; add a bounded read-only system scan where it is useful.
- 02Reconcile
Agree the better process
Bring the business into the room, reconcile variants, and confirm what the target process must preserve.
- 03Decide
Disposition the exceptions
Flatten, extend cleanly, retire, or move to the edge, with the evidence and rationale behind each decision attached.
- 04Handoff
Export and hand over
Move BPMN 2.0 XML and supporting evidence into Signavio, the SI workstream, or the internal design authority.
- 05Sustain
Keep the map live
Use the agreed process record through Realize and after go-live instead of letting discovery become a dead deck.
The system evidence changes the conversation.
~95%
Sales pricing
Finished goods missing a base price.
0%
Supplier confirmations
Order acknowledgements on the latest purchase orders.
1,507
Procurement
Open purchase-order items still unresolved.
Benchmark one ECC sample scan
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.
Connect read-only and see where you stand in minutes.
- 01Connect
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.
- 02Scan
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.
- 03Report
Get a risk-rated report
Every gap is rated High, Medium, or Low and paired with the SAP action that fixes it.
Where the gaps hide in a live SAP.
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 to
SAP Activate methodology, SAP Clean Core, SAP master-data quality targets, SAP Best Practices and Notes
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.
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.
A report your team can act on the same day.
- 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.
Carry the agreed scope into your SAP programme.
Your process model, evidence and dispositions remain customer-owned and portable. Fit-to-standard workshops and your SI start from the agreed requirements and their rationale.
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.