See every gap in your SAP.
Connect your live SAP read-only. Duvo scans the system and returns a risk-rated gap report in minutes, benchmarked to SAP Activate and Clean Core. Migration prep or a routine health check, ECC or S/4HANA.
- Read-only OData connection
- Risk-rated in minutes
- Benchmarked to SAP Activate and Clean Core
- Works with ECC and S/4HANA
From a real sample scan of a live SAP system.
How it works
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.
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.
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.
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.
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.
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.
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.
The critical findings up front
Every High-risk gap on the first page, in plain language the steering committee can read.
Every data set, every count
The full scan: 49 data sets, record counts, what was accessible, and a key observation for each.
Risk-rated, with recommended actions
Each gap categorised, rated High, Medium, or Low, and paired with the SAP action to remediate it.
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.