SAP S/4HANA Solution Design: [Programme or company name]
Solution design for an SAP S/4HANA implementation or transition,
written at the end of the Explore phase of SAP Activate and kept
current through Realize and Deploy. It records the deployment option
and transition path, the enterprise structure, the end-to-end process
design, the results of fit-to-standard, delta requirements and the
backlog, master data and finance design, the clean core and
extensibility approach (clean core levels A to D), integration through
SAP Integration Suite, data migration with the SAP S/4HANA Migration
Cockpit, analytics, output and forms, roles and authorisations, SAP
Fiori user experience, system landscape and transport management,
non-functional design, cutover and run. Phase names follow SAP
Activate (Discover, Prepare, Explore, Realize, Deploy, Run). Replace
every [bracketed] value and every row marked Example.
Document control
| Field | Value |
|---|
| Document ID | [SAPSD-001] |
| Programme | [Programme name] |
| Product and edition | [SAP Cloud ERP (SAP S/4HANA Cloud Public Edition) / SAP Cloud ERP Private (SAP S/4HANA Cloud Private Edition) / SAP S/4HANA on-premise] |
| Commercial offer | [RISE with SAP / GROW with SAP / Licence and own operation] |
| Release | [For example 2602 (Public Edition) or 2025 FPS01 (Private Edition, on-premise)] |
| Transition path | [New implementation / System conversion / Selective data transition] |
| SAP Activate phase | [Explore / Realize / Deploy] |
| Version | [0.1] |
| Status | [Draft / In review / Approved / Superseded] |
| Owner | [@sap-solution-architect] |
| Approvers/reviewers | [@business-process-owners], [@enterprise-architect], [@security-architect], [@sap-basis-lead], [@design-authority-chair] |
| Last updated | YYYY-MM-DD |
| Classification | [Internal / Confidential] |
| Related documents | [Fit-gap analysis], [Integration design], [Data migration strategy], [Cutover plan] |
Approvals
| Role | Name | Decision | Date |
|---|
| Business sponsor | [@name] | [Approve / Approve with conditions / Reject] | YYYY-MM-DD |
| Design authority | [@name] | [Decision] | YYYY-MM-DD |
| Finance process owner | [@name] | [Decision] | YYYY-MM-DD |
| Security and compliance | [@name] | [Decision] | YYYY-MM-DD |
| SAP technical lead | [@name] | [Decision] | YYYY-MM-DD |
Revision history
| Version | Date | Author | Change summary |
|---|
| 0.1 | YYYY-MM-DD | [@name] | First draft at start of Explore |
| 0.9 | YYYY-MM-DD | [@name] | Example: Explore quality gate version: fit-to-standard complete, backlog baselined |
| 1.0 | YYYY-MM-DD | [@name] | Example: Approved by design authority for Realize |
Contents
1. Introduction and scope
1.1 Purpose and outcomes
This document defines how SAP S/4HANA will support [Organisation]'s
in-scope processes. It is the design baseline that the build team,
testers, data migration team and support organisation work from.
| Outcome ID | Business outcome | Measure | Target |
|---|
| OUT-01 (Example) | Faster month-end close | Working days to close | From 8 to 4 |
| OUT-02 (Example) | Standard processes across all companies | Share of processes run on one global template | 90% |
| OUT-03 (Example) | Upgradable core | Extensions at clean core level C or D | 0 at go-live |
| [OUT-NN] | [Outcome] | [Measure] | [Target] |
1.2 Scope
| Dimension | In scope | Out of scope |
|---|
| Companies and countries | Example: 6 company codes in 4 countries | Joint ventures |
| End-to-end processes | Example: Source to pay, order to cash, plan to produce, record to report | Recruit to retire (stays on current HCM) |
| Users | Example: 1,200 named users, 150 in warehouses | External partners |
| Legacy systems replaced | Example: SAP ECC 6.0 EHP8, two local accounting packages | Plant maintenance tool (phase 2) |
| [Dimension] | [Value] | [Value] |
2. Deployment option and transition path
2.1 Deployment options
| Criterion | SAP Cloud ERP (Public Edition) | SAP Cloud ERP Private (Private Edition) | SAP S/4HANA on-premise |
|---|
| Operation | SAP-operated, multi-tenant SaaS | SAP-operated, single-tenant, usually contracted through RISE with SAP | Customer or partner operated |
| Release cadence | Two releases per year (YYMM names, for example 2602) | Base release with feature package stacks; customer schedules upgrades | Same releases as Private Edition |
| Extensibility | Key user, ABAP Cloud developer extensibility, side by side on SAP BTP | Same plus classic ABAP, governed by clean core levels | Full technical freedom, governed by own policy |
| Configuration | Guided configuration and scope items | Full configuration (customising) | Full configuration |
| Typical fit | New implementations that adopt standard processes; GROW with SAP | Conversions and complex enterprises; RISE with SAP | Customers with operating constraints that rule out SAP-operated cloud |
Since 2025 SAP markets the cloud editions as SAP Cloud ERP and SAP
Cloud ERP Private within SAP Business Suite, while technical and
implementation documentation still uses the S/4HANA Cloud edition
names. Check the current names at sap.com and learning.sap.com.
2.2 Transition path
| Path | What it means | Choose when | Main risks |
|---|
| New implementation | Fresh system, standard processes, selected data migrated | Legacy design is not worth keeping; high appetite for standardisation | Change management; data migration volume |
| System conversion | Existing SAP ERP system converted technically to S/4HANA | Processes and custom code are mostly worth keeping | Carries technical debt forward; simplification items |
| Selective data transition | New target shell with selected configuration, code and data moved | Mixed needs, company carve-outs, merging systems | Needs specialist tools and partners |
2.3 Decision
| Item | Value |
|---|
| Selected edition | Example: SAP Cloud ERP Private under RISE with SAP |
| Selected path | Example: New implementation with selective history load |
| Main reasons | Example: 60% of ECC custom code unused; finance wants a new chart of accounts; 3 industry extensions not possible in Public Edition |
| Rejected options | Example: Public Edition (industry gaps FG-021, FG-034); system conversion (keeps unused code) |
| Decision record | [ADR-NNN] in the Architecture Decision Log (architecture/architecture-decision-log) |
2.4 Time constraints
SAP announced in February 2020 that mainstream maintenance for SAP Business Suite 7 core
applications, including SAP ERP 6.0 with enhancement package 6 or higher, runs to the end of 2027
(lower enhancement packages ended at the end of 2025), with optional extended maintenance to the end
of 2030 at a premium, and committed to S/4HANA maintenance until at least 2040. In 2025 SAP added
the SAP ERP, private edition, transition option for large customers that cannot finish their move by
2030, with conditions (move to SAP ERP, private edition on SAP HANA before the end of 2030, minimum
system size of 2 TB, the Max success plan, and mitigation for products outside the option as
described in SAP Note 3591251); an update in October 2026 states that subscriptions may run to the
end of 2035 with further prerequisites. Since S/4HANA 2023, base releases follow a two-year cycle
with seven years of mainstream maintenance each. Check the current dates in the SAP Support Portal
and SAP Note 3591251 before you plan.
| Constraint | Date | Plan impact |
|---|
| Example: ECC mainstream maintenance end (EHP 6 or higher) | 2027-12-31 | Go-live before this date, or budget extended maintenance; check the enhancement package level first |
| Example: Target go-live | YYYY-MM-DD | [Impact] |
| [Constraint] | YYYY-MM-DD | [Impact] |
3. Enterprise structure
| Unit | Purpose | Count | Naming rule | Design notes |
|---|
| Company code | Legal entity with own financial statements | Example: 6 | 4 characters, country prefix | One per legal entity |
| Controlling area | Management accounting scope | Example: 1 | Global | All company codes share one fiscal year variant and chart of accounts |
| Plant | Production or logistics site | Example: 9 | Country plus number | Plant equals physical site |
| Storage location | Stock place within a plant | Example: 24 | Plant plus number | Warehouse management only in 3 plants |
| Sales organisation | Selling unit with legal responsibility | Example: 4 | One per selling company | Distribution channels: direct, distributor |
| Purchasing organisation | Negotiating unit | Example: 1 central plus 2 local | [Rule] | Central contracts, local call-offs |
| Profit centre | Internal reporting | Example: 30 | Business line plus region | Mandatory for segment reporting |
| [Unit] | [Purpose] | [n] | [Rule] | [Notes] |
4. End-to-end process design
4.1 Process catalogue
| Process ID | End-to-end process | Level 3 process | SAP scope item or process variant | Companies | Owner | Systems involved |
|---|
| E2E-OTC-01 (Example) | Order to cash | Sell from stock | [Scope item ID] | All | [@sales-ops-lead] | S/4HANA, CRM, tax engine |
| E2E-OTC-02 (Example) | Order to cash | Service contract billing | [Scope item ID] plus EXT-BIL-001 | DE01, FR01 | [@billing-lead] | S/4HANA, metering platform |
| E2E-STP-01 (Example) | Source to pay | Procurement of direct materials | [Scope item ID] | All | [@procurement-lead] | S/4HANA, supplier network |
| E2E-RTR-01 (Example) | Record to report | Period-end closing | [Scope item ID] | All | [@controller] | S/4HANA, consolidation |
| [E2E-NNN] | [Process] | [Process] | [Scope item] | [Companies] | [@owner] | [Systems] |
Link the reference model used in SAP Signavio Process Navigator
rather than copying it.
4.2 Process flow for a critical process
Draw one sequence per process that crosses systems; Example below.
4.3 Local variants
| Variant ID | Process | Country or company | Reason | Legal reference |
|---|
| VAR-001 (Example) | Billing | FR01 | Electronic invoicing obligation | [National law and date, check current status] |
| [VAR-NNN] | [Process] | [Scope] | [Reason] | [Reference] |
5. Fit-to-standard results
| Process area | Workshops held | Requirements | Fit | Fit with configuration | Process change | Extension or add-on | Rejected or deferred |
|---|
| Order to cash (Example) | 6 | 84 | 52 | 18 | 5 | 6 | 3 |
| Source to pay (Example) | 5 | 61 | 40 | 14 | 3 | 3 | 1 |
| Record to report (Example) | 4 | 47 | 30 | 12 | 1 | 2 | 2 |
| Total (Example) | 15 | 192 | 122 | 44 | 9 | 11 | 6 |
| [Area] | [n] | [n] | [n] | [n] | [n] | [n] | [n] |
Source: Fit-Gap Analysis [FGA-001]. Example fit rate including
configuration: (122 + 44) / 192 = 86%.
6. Delta requirements and backlog
| Backlog type | Count | Estimated effort (person-days) | Release 1 | Later release | Specification |
|---|
| Configuration items | Example: 44 | 120 | 44 | 0 | Configuration workbook |
| Workflows (W) | Example: 2 | 20 | 2 | 0 | WRICEF specification |
| Reports (R) | Example: 3 | 18 | 2 | 1 | WRICEF specification |
| Interfaces (I) | Example: 14 | 210 | 12 | 2 | WRICEF specification and Integration Design |
| Conversions (C) | Example: 28 objects | 160 | 28 | 0 | Data Migration Strategy |
| Enhancements (E) | Example: 4 | 85 | 3 | 1 | WRICEF specification |
| Forms (F) | Example: 9 | 54 | 9 | 0 | WRICEF specification |
| [Type] | [n] | [n] | [n] | [n] | [Spec] |
Interface, conversion and form objects also arise from requirements
classified as fits (a standard payment run still needs a bank
interface), so the WRICEF counts here exceed the gap count in section 5.
Backlog tool: [SAP Cloud ALM / Jira / Azure DevOps], project [key].
Each item carries the fit-gap ID, process ID and clean core level.
7. Master data and finance design
7.1 Master data objects
| Object | System of record | Create and change process | Owner | Key design decisions |
|---|
| Business partner (customer and supplier roles) | Example: S/4HANA | Central team with approval workflow | [@mdm-lead] | One business partner per legal entity; number ranges aligned with legacy numbers where possible |
| Product (material) | Example: PLM for engineering data, S/4HANA for logistics views | Workflow from PLM release | [@product-data-lead] | Global product type list; units of measure standardised |
| General ledger account | Example: S/4HANA | Finance controllership | [@controller] | One operational chart of accounts; country charts for statutory reporting |
| Cost centre and profit centre | S/4HANA | Controlling team | [@controller] | Hierarchies aligned with management reporting |
| [Object] | [System] | [Process] | [@owner] | [Decisions] |
S/4HANA requires the business partner as the leading object for
customers and suppliers; in a system conversion, plan customer-vendor
integration early. Master data governance beyond this system is
designed in the Master Data Management Design
(architecture/master-data-management-design).
7.2 Finance design decisions
| Decision | Choice | Reason |
|---|
| Ledgers | Example: Leading ledger IFRS, extension ledger for local GAAP in 2 countries | Parallel accounting required |
| Currencies | Example: Company code currency, group currency, hard currency for 1 country | Group reporting and inflation reporting |
| Fiscal year variant | Example: Calendar year, 12 periods plus 4 special periods | Same for all companies |
| Profitability analysis | Example: Margin analysis on the universal journal | Real-time margin by product and customer |
| Asset accounting | Example: Depreciation areas for IFRS, local GAAP and tax | Statutory requirement |
| [Decision] | [Choice] | [Reason] |
8. Clean core and extensibility
SAP describes clean core as keeping the ERP close to standard, with
extensions built only on stable, released interfaces, so that upgrades
remain predictable. In 2025 SAP evolved its earlier three-tier
extensibility model into a clean core level concept that rates each
extension from A to D (SAP News, August 2025). The summary below is in
our own words; check SAP's current guidance before you apply it.
| Level | Our summary | Policy in this programme |
|---|
| A | Uses only released, stable APIs and extension points (ABAP Cloud on stack, or side by side on SAP BTP) | Default for all new development |
| B | Also uses documented classic APIs that SAP regards as upgrade-stable | Allowed with architect approval and a note in the extension register |
| C | Accesses SAP internal objects that may change between releases | Exception only; design authority approval and an upgrade test per release |
| D | Uses techniques SAP does not recommend, such as modifications, direct table writes or implicit enhancements | Not allowed; waiver from the steering committee only |
8.1 Extension techniques
| Technique | Where it runs | Use for | Edition |
|---|
| Key user extensibility | In the ERP, through Fiori apps for custom fields, logic, business objects and CDS views | Extra fields, simple validations, custom analytics views | All editions |
| Developer extensibility (ABAP Cloud) | In the ERP, on the same stack | Logic close to the data that needs released APIs | All editions |
| Side-by-side extensibility | SAP BTP (for example SAP Build, SAP Cloud Application Programming Model, ABAP environment) | New apps, process automation, decoupled logic | All editions |
| Classic ABAP extensions | In the ERP | Legacy scenarios not yet covered by released APIs | Private Edition and on-premise only, rated against levels B to D |
8.2 Governance
- Run the ABAP test cockpit with clean core checks on every transport;
block level D findings automatically.
- Record every extension in section 9 with its level before build.
- Review level B and C extensions at every release upgrade and replace
them when a released alternative appears.
- For a system conversion, analyse custom code with SAP's custom code
tools and retire unused objects first.
9. Extension register
| Object ID | WRICEF type | Description | Fit-gap ID | Technique | Clean core level | Owner | Status |
|---|
| EXT-BIL-001 (Example) | E | Usage-based billing calculation | FG-007 | Side by side on SAP BTP, billing API | A | [@billing-lead] | In build |
| INT-AP-003 (Example) | I | Scanned invoices to draft supplier invoices | FG-005 | Integration Suite with released API | A | [@ap-lead] | In test |
| WFL-PUR-001 (Example) | W | Contract release approval with budget availability pre-check | FG-024 | Flexible workflow with a released BAdI for the pre-check | A | [@procurement-lead] | Built |
| RPT-FIN-004 (Example) | R | Intercompany open items by partner | FG-031 | Custom CDS view via key user tool | A | [@controller] | Built |
| FRM-SD-002 (Example) | F | Customer invoice form | FG-040 | Adobe form template with output management | A | [@sales-ops-lead] | Built |
| ENH-MM-007 (Example) | E | Batch determination exit for regulated products | FG-052 | Classic BAdI | B | [@quality-lead] | Approved exception |
| [OBJ-ID] | [W/R/I/C/E/F] | [Description] | [FG-NNN] | [Technique] | [A-D] | [@owner] | [Status] |
10. Integration architecture
| Interface ID | Source | Target | Pattern | Technology | Frequency and volume | Owner |
|---|
| INT-OTC-001 (Example) | CRM | S/4HANA | Synchronous request | OData API through Integration Suite | 2,000 orders per day | [@integration-lead] |
| INT-OTC-004 (Example) | S/4HANA | Warehouse | Event | Business event to event broker | 3,500 deliveries per day | [@integration-lead] |
| INT-FIN-002 (Example) | S/4HANA | Banks | File | Payment format through Integration Suite | Daily batches | [@treasury-lead] |
| [INT-NNN] | [Source] | [Target] | [Pattern] | [Technology] | [Volume] | [@owner] |
Rules (Example): use released APIs listed on the SAP Business
Accelerator Hub; in SAP Cloud ERP, connect through communication
scenarios and arrangements; route external traffic through SAP
Integration Suite; publish business events for decoupled consumers.
Detailed specifications follow the Integration Design
(architecture/integration-design) and the Integration Strategy
(architecture/integration-strategy).
11. Data migration
| Item | Design |
|---|
| Tool | Example: SAP S/4HANA Migration Cockpit (Migrate Your Data app), staging tables approach for non-SAP sources, direct transfer for the ECC source (direct transfer is not available in SAP Cloud ERP Public Edition) |
| Objects | Example: 28 migration objects (business partners, products, open items, balances, open orders, fixed assets) |
| History | Example: Open items and balances only; 2 years of history to the archive and reporting store |
| Mock loads | Example: 3 mock loads and 1 dress rehearsal, each reconciled |
| Reconciliation | Data Migration Reconciliation Report (project/data-migration-reconciliation) per load |
| Full design | Data Migration Strategy (architecture/data-migration-strategy) |
| Object | Source | Approach | Volume | Load order | Reconciliation key |
|---|
| Business partner (Example) | ECC, two local packages | Staging tables after cleansing | 48,000 | 1 | Count by role and company |
| Open supplier items (Example) | ECC | Staging tables | 12,500 | 4 | Balance per company code and supplier |
| [Object] | [Source] | [Approach] | [n] | [n] | [Key] |
12. Analytics, output and forms
12.1 Analytics
| Need | Solution | Reason |
|---|
| Operational lists and real-time KPIs | Example: Embedded analytics on released CDS views, Fiori analytical apps | Real time, no extra copy of data |
| Planning and management dashboards | Example: SAP Analytics Cloud | Planning and cross-source dashboards |
| Enterprise data platform | Example: SAP Business Data Cloud or existing lakehouse | Blending with non-SAP data |
| [Need] | [Solution] | [Reason] |
12.2 Output and forms
| Item | Design |
|---|
| Output determination | Example: S/4HANA output management for new documents |
| Form technology | Example: Adobe-based form templates rendered by the SAP forms service |
| Channels | Example: Email, print through cloud print manager, electronic invoicing network |
13. Security, roles and authorisations
| Area | Design |
|---|
| Identity | Example: Corporate identity provider federated with SAP Cloud Identity Services (Identity Authentication, Identity Provisioning) |
| Role model | Example: Business roles built from SAP-delivered templates (Cloud ERP) or task-based single and composite roles (Private Edition) |
| Segregation of duties | Example: Rule set for source to pay and record to report; checks before role assignment |
| Privileged access | Example: Emergency access with time-bound elevation and log review |
| Data protection and audit | Example: Blocking and deletion of personal data per retention policy; security audit log, change documents, read access logging for sensitive fields |
| Role ID | Business role | Main tasks | Conflicting roles | Users |
|---|
| ROL-AP-01 (Example) | Accounts payable clerk | Post supplier invoices, clear items | ROL-MD-02 supplier master maintenance | 25 |
| ROL-MD-02 (Example) | Supplier master specialist | Create and change suppliers | ROL-AP-01 | 4 |
| [ROL-NNN] | [Role] | [Tasks] | [Conflicts] | [n] |
Enterprise identity: IAM Solution Design (security/iam-solution-design).
14. User experience
| Item | Design |
|---|
| Entry point | Example: SAP Fiori launchpad, embedded in the company portal through SAP Build Work Zone |
| App selection | Example: Apps per business role from the SAP Fiori apps reference library |
| Layout | Example: Spaces and pages per role; no personal tile sets at go-live |
| Devices | Example: Desktop for office users; tablets for warehouse picking |
15. Landscape, transport and release management
| Item | Design |
|---|
| Landscape | Example: Three systems (development, quality, production) plus a sandbox; BTP with three subaccounts |
| Change control | Example: SAP Cloud ALM for requirements, test and deployment; transport management system for ABAP; SAP Cloud Transport Management for BTP content |
| Release cadence | Example: Cloud ERP: two SAP releases per year with regression test window; Private Edition: one upgrade every two years, FPS within the year |
| Regression testing | Example: Automated tests for the top 60 process variants run on every SAP release and every major transport bundle |
| Retrofit and freeze | Example: Code freeze two weeks before each SAP upgrade and before go-live |
16. Non-functional design
| Quality | Requirement | Delivered by | Verification |
|---|
| Availability | Example: As per the contracted service level for production | SAP (cloud contract) | Monthly service report |
| Performance | Example: 95% of dialog steps for top 20 apps under 2 seconds at 1,200 users | Project | Performance test |
| Batch window | Example: Nightly MRP and billing complete by 05:00 local time | Project | Volume test |
| Recovery | Example: RPO and RTO per contract and per HA/DR design | SAP and customer | DR test |
| Integration resilience | Example: No message lost; retries and alerting for every interface | Project | Integration test |
| [Quality] | [Requirement] | [Owner] | [Method] |
Surrounding systems follow the Resilience Tiering and HA/DR Design
(architecture/resilience-tiering-ha-dr-design).
17. Cutover, hypercare and run
| Item | Design | Detailed in |
|---|
| Cutover approach | Example: Big bang over a long weekend at month start, legacy read-only for 7 years | Cutover Plan (project/cutover-plan) |
| Go-live criteria | Example: All P1 defects closed, 3rd mock load reconciled, users trained | Go-Live Readiness Review (project/go-live-readiness-review) |
| Hypercare | Example: 6 weeks, daily triage, exit on stable ticket trend | Hypercare Plan (ops/hypercare-plan) |
| Run organisation | Example: Centre of expertise for SAP, partner for application management, SAP for cloud operations | Operations Handover (ops/operations-handover) |
| Continuous improvement | Example: Quarterly review of deferred gaps and new SAP release features | This design, section 6 |
18. Decisions, risks and traceability
18.1 Key decisions
| Decision ID | Decision | Alternatives | Reason | Date |
|---|
| ADR-010 (Example) | Private Edition under RISE with SAP | Public Edition, on-premise | Industry extensions and conversion of history | YYYY-MM-DD |
| ADR-011 (Example) | One controlling area for all companies | One per country | Group-wide margin reporting | YYYY-MM-DD |
| ADR-012 (Example) | Usage billing side by side on BTP | Classic ABAP enhancement | Clean core level A | YYYY-MM-DD |
| [ADR-NNN] | [Decision] | [Alternatives] | [Reason] | YYYY-MM-DD |
18.2 Risks
| Risk ID | Risk | Likelihood | Impact | Mitigation | Owner |
|---|
| RSK-001 (Example) | Business partner data quality delays mock load 1 | High | High | Cleansing sprint started in Explore; data owners named | [@mdm-lead] |
| RSK-002 (Example) | SAP release during Realize changes a standard process | Medium | Medium | Review release notes per release; regression test | [@sap-solution-architect] |
| RSK-003 (Example) | Level B extension breaks at upgrade | Low | Medium | Upgrade test; plan replacement with released API | [@dev-lead] |
| [RSK-NNN] | [Risk] | [L] | [I] | [Mitigation] | [@owner] |
18.3 Traceability
| Outcome | Process | Fit-gap ID | Object ID | Test case | Status |
|---|
| OUT-01 (Example) | E2E-RTR-01 | FG-031 | RPT-FIN-004 | TC-RTR-014 | Passed |
| OUT-03 (Example) | E2E-OTC-02 | FG-007 | EXT-BIL-001 | TC-BIL-005 | In build |
| [OUT-NN] | [E2E-NNN] | [FG-NNN] | [OBJ-ID] | [TC-ID] | [Status] |
19. Glossary and references
19.1 Glossary
| Term | Meaning |
|---|
| SAP Activate | SAP's implementation method with the phases Discover, Prepare, Explore, Realize, Deploy and Run |
| Fit-to-standard | Explore phase workshops that demonstrate the standard and capture delta requirements |
| Clean core | Keeping the ERP close to standard with extensions on stable, released interfaces |
| Clean core level | SAP's A to D rating of how upgrade-safe an extension is |
| RISE with SAP / GROW with SAP | SAP's subscription bundles for cloud ERP: RISE with SAP for the transformation of new or existing customers (any cloud edition), GROW with SAP for net-new customers adopting SAP Cloud ERP (Public Edition) |
| SAP BTP | SAP Business Technology Platform, used for side-by-side extensions and integration |
| Scope item | Preconfigured business process content delivered by SAP |
| WRICEF | Workflows, Reports, Interfaces, Conversions, Enhancements, Forms |
| FPS | Feature package stack delivered between base releases |
19.2 References
| Reference | Version or date checked | Use |
|---|
| SAP Learning, Discovering SAP Activate: Explore phase overview, learning.sap.com | Checked 2026-10-23 | Explore activities and deliverables |
| SAP News, "Extend SAP S/4HANA Cloud the Right Way: Clean and Clear", news.sap.com | 2025-08-12 | Clean core levels A to D |
| SAP News, SAP S/4HANA maintenance to 2040, news.sap.com | 2020-02-04 | Business Suite 7 maintenance dates |
| SAP News, new SAP S/4HANA release and maintenance strategy, news.sap.com | 2022-09 | Two-year release cycle, seven years maintenance |
| SAP News, updates for SAP ERP, private edition, transition option, news.sap.com | 2025-08-04, updated 2026-10-13 | Transition option conditions |
| SAP Help Portal, SAP S/4HANA Migration Cockpit, help.sap.com | Check current release | Migration approaches |
Fit-Gap Analysis (architecture/fit-gap-analysis) | This library | Register behind section 5 |
Standard and licence note
Structure aligned with the deliverables of the Explore phase of SAP
Activate and with SAP's published clean core guidance. Only phase,
product, tool and level names are used; no SAP methodology content,
accelerators, roadmap text or tables are reproduced, and all text,
examples and tables are original and written for this collection.
Dates and conditions are summarised from SAP announcements as checked
on 2026-10-23; check the current official versions before use. SAP,
SAP S/4HANA, SAP Activate, SAP BTP, SAP Fiori, RISE with SAP and GROW
with SAP are trademarks of SAP SE or its affiliates; this template is
not affiliated with or endorsed by them. Template licence: MIT.