Plan your SAP migration around how the business works.
Mainstream maintenance for SAP Business Suite 7 core applications ends in 2027, with optional extended maintenance to 2030. Duvo maps how your business processes actually run, exposes the gaps and gives your programme team and SI reviewed requirements, so you resolve process decisions before they become migration rework.
Example deliverable
A pricing gap in one ECC sample scan
Excerpt from the existing SAP sample findings. It describes one inspected dataset, not the typical SAP estate.
- Dataset
- Finished-goods materials in the sample system.
- Finding
- A base price was present on 11 of 218 finished-goods materials.
- Recommended action
- Review which finished goods are active and create the required base prices through the approved SAP change process.
- Handoff
- A risk-rated finding, its dataset and the action for the SAP team to validate. The scan itself does not change prices.
This read-only scan reports findings in the inspected dataset. It does not change the system.
Inspect the sample scan findingsWhat we need to start.
One process, a business owner and SAP counterpart. Walkthroughs need no system access; an optional scan needs approved read-only access to agreed datasets.
What is included?
A reviewed process or migration fact base, requirements with their rationale, and the agreed decisions to adopt standard practice, extend, retire or keep work outside the core. An included system scan adds risk-rated findings and recommended actions. Any BPMN 2.0 XML handoff is separately scoped and accepted with your SI or Signavio team. The initial scope is a defined process or assessment. It does not replace your SI, establish whole-estate readiness or include migration, custom-code remediation or production writes unless separately agreed.
What records and access are needed?
The process, markets and systems under review, the programme decision it must inform, and a business owner and SAP counterpart. Operator walkthroughs, interviews and relevant documentation, including work in portals, spreadsheets and email around SAP. For an optional system scan: a supported ECC or S/4HANA environment, approved read-only OData access and the datasets to be inspected. Business process discovery can start without SAP access. A system scan requires approved read-only access to the scoped datasets. Scan findings recommend action; they do not authorize configuration changes or production writes.
Who needs to be involved?
Business operators validate the process and exceptions. Your SAP team approves read-only access when a scan is included. The programme owner and SI review findings, choose dispositions and own implementation and change approval. Agree their participation and review effort before starting.
When will we receive the result?
Set the delivery date after the process scope, participants and handoff requirements are agreed. If a scan is included, the date also depends on approved connectivity and accessible datasets. Missing access or unresolved process variants remain explicit dependencies.
How do we review the result?
The programme owner can trace each disposition to process or system evidence; the SI or internal team accepts the agreed handoff. The scan names what was accessible and what was excluded. Any implementation scope has its own acceptance checks.
What happens next?
Accept the fact base or agreed change and hand it to your programme team. Continue with a defined implementation scope only where needed. Standalone SAP work is a valid purchase.