Explainer

SAP Activate: SAP’s own method for S/4HANA and RISE, in diagrams

The method SAP recommends for every SAP S/4HANA move, packaged for RISE with SAP as the RISE with SAP Methodology. What happens in each phase, where the quality gates sit, and where testing and sign-off belong.

What it is

SAP Activate is SAP’s implementation framework. It combines SAP Best Practices (ready-made process content), guided configuration, and a method with six phases. For RISE with SAP, SAP publishes it as the RISE with SAP Methodology: the same six steps, with a success plan, clean core principles and quality gates built in. It leans on two ideas: start from the standard, and build iteratively with the business in the room.

1. Six phases, from Discover to Run

Discover happens before the project, Run is the steady state after go-live, and the four phases in between (Prepare, Explore, Realize, Deploy) are the delivery project. Explore is where Fit-to-Standard happens: the business sees SAP’s standard processes first and only asks for changes where the standard truly doesn’t fit. Realize is agile: configuration and testing happen in short sprints.

Phase 1
Discover
Why move, and to what?
- · Value and business case
- · Transition path
- · Scope and approval
Quality
Agree what "ready to go live" will mean before the contract is signed.
Phase 2
Prepare
Are we set up to deliver?
- · Team, governance, roadmap
- · Systems and tools (SAP Cloud ALM)
- · Success plan
Quality
Testing approach agreed, test management set up, test roles named.
Quality gate
Phase 3
Explore
How well does the standard fit?
- · Fit-to-Standard workshops
- · Delta requirements and extensions
- · Clean core decisions
Quality
Test strategy written; every in-scope process has acceptance criteria.
Quality gate
Phase 4
Realize
Build it, sprint by sprint
- · Configure in agile sprints
- · Extensions and integrations
- · Data migration loads
Quality
Unit and string tests in each sprint, then integration testing and UAT by the business.
Quality gate
Phase 5
Deploy
Ready for production?
- · Final testing
- · Cutover rehearsals
- · Go-live and hypercare
Quality
Dress rehearsals, data reconciliation and the go/no-go evidence pack.
Quality gate
Phase 6
Run
Keep it running, keep it current
- · Operations
- · Upgrades and feature packs
- · Continuous improvement
Quality
Regression testing for every upgrade, using the test cases built in Realize.

Phased at the top, agile inside Realize. A quality gate closes each delivery phase: the program moves on only on evidence.

SAP Activate’s six phases. Phase names and activities follow SAP’s RISE with SAP Methodology; the quality notes are The Sign-Off Table’s testing lens.

2. Quality gates: moving on only on evidence

A quality gate closes each delivery phase. Under RISE with SAP, you complete a questionnaire at the end of each phase and SAP experts come back with feedback and recommended next steps. In SAP Cloud ALM, the gates live in the project with their checklists. A gate ends in one of three ways: pass, pass with conditions (named actions, owners and dates), or fail.

For anyone who signs, the useful part is timing. Activate tells you when each kind of evidence should exist: requirements and acceptance criteria at the end of Explore, test cases before integration testing starts, accepted UAT results before Deploy, and reconciled rehearsal results before go-live.

3. Where each test level belongs

Testing in Activate isn’t a phase. It’s a workstream that runs through every phase, with the test strategy written in Explore and the test levels run in Realize and Deploy. SAP’s guidance for Private Edition is that UAT is run by the business experts who attended Fit-to-Standard, with issues resolved before moving to Deploy.

Test level	When	Who runs it	What it proves
Unit and string tests	Realize, in each sprint	Functional consultants	Each configured step works on its own and in short chains
Integration testing	Realize, after the build	Test team with the business	End-to-end processes work across modules and interfaces
User acceptance testing	Realize, before Deploy	Business experts from Fit-to-Standard	The business accepts the processes it will run
Final testing and dress rehearsal	Deploy	Cutover team, test team, business	The move to production works, with reconciled data
Regression testing	Run, every upgrade	Customer (not SAP) under RISE	What worked yesterday still works after the change

Test levels across SAP Activate. Based on SAP Learning’s test strategy content.

4. Who owns testing under RISE with SAP

RISE with SAP moves infrastructure, technical operations and the technical execution of upgrades to SAP. It does not move the job of proving that your business processes work. SAP’s roles and responsibilities document for Private Edition treats functional and regression testing as the customer’s, unless you buy it as a separate service.

Area	SAP under RISE	You, the customer
Infrastructure and technical operations	Provides and runs them	Consumes the service
Technical execution of upgrades	Performs the upgrade	Schedules and approves the dates
Functional and regression testing	Only as separately purchased services	Owns it: plans, runs, signs off
Business process sign-off	No	Process owners sign, on evidence

Responsibilities under RISE with SAP, Private Edition. Source: SAP roles and responsibilities document.

Learn it properly, free

SAP Activate Methodology Essentials

A free Academy course on the phases, workstreams, quality gates, roadmaps and testing in Activate, with a quiz and a certificate path.

Start the course

Sources

SAP, SAP S/4HANA, SAP Activate and RISE with SAP are trademarks or registered trademarks of SAP SE. The Sign-Off Table is not affiliated with or endorsed by SAP SE.