A scoping exercise that does not produce these 4 documents is not a scoping exercise — it is a workshop with no output. Each deliverable answers a specific technical question that the Prepare and Explore phases cannot answer for themselves without it.
Deliverable 1: Custom Code Migration Roadmap
Produced from SAP Readiness Check and Custom Code Migration Tool (CCMT) analysis. Contains every custom ABAP object in the current landscape, classified as Retire, Replace, Rebuild, or Redesign. For every Rebuild object: technology decision (SAP CAP, ABAP RAP, SAP Build), effort estimate (S/M/L/XL), and BTP service requirement. This document is the input to BTP subaccount design and BTP consumption modeling.
Deliverable 2: Integration Migration Plan
Contains every integration in the current landscape: RFC, BAPI, IDoc, middleware, EDI — classified into four categories: pre-built SAP Integration Suite package, custom integration flow development, retire, or Phase 2 defer. Each record includes the interface name, direction, owning team, business criticality, migration category, effort estimate, and target authentication model. This document is the input to the August integration architecture design.
Deliverable 3: Data Migration Strategy
Defines which master data objects and open item types will be migrated using SAP Migration Cockpit, the source data quality assessment findings per object type, the data cleansing responsibility matrix (which business team owns each remediation), the historical data approach (legacy read system, SAP Analytics Cloud, or archive), and the mock cutover cycle plan — minimum two full rehearsal runs before production go-live.
Deliverable 4: Phased Implementation Roadmap
Defines the process module scope per go-live phase, timeline ranges per SAP Activate phase key dependencies between scope items, team structure and resource requirements per phase, and a risk register covering the top scope, data, integration, and organizational change risks identified during scoping.