Lesson 1 of 5
Activate overview
8 min
Listen to this lesson
Every SAP S/4HANA program you join will talk in the language of SAP Activate: "we are in Explore", "that is a Realize deliverable", "the Q-gate is next Thursday". SAP Activate is SAP's implementation framework for its solutions. It brings together three things: SAP Best Practices (ready-made business process content to start from), a methodology (phases, workstreams, deliverables and tasks), and tools such as SAP Cloud ALM that put the methodology to work.
Activate replaced SAP's older waterfall-style method (ASAP) and leans on two ideas. First, start from the standard: show the business how SAP Best Practices processes work before designing anything new. Second, build iteratively: configure and test in short sprints with business involvement, rather than designing everything up front and testing everything at the end.
The six phases
- DiscoverUnderstand the valueExplore what the solution can do, build the business case and choose the transition path. Happens before the project starts.
- PrepareSet up the projectPlan, staff and govern the project; set up tools and systems; define the high-level approach.
- ExploreValidate the standardFit-to-Standard workshops confirm how standard processes fit; gaps become requirements; test planning starts.
- RealizeBuild and testConfigure and extend in sprints, migrate data, and run integration and user acceptance testing.
- DeployGo liveFinal preparations, cutover and go-live, followed by hypercare support.
- RunOperate and improveOperate the solution, adopt innovations and test each upgrade or release.
Discover is special. It happens before a contract or project exists, so project tools such as Cloud ALM start their plan at Prepare. Run is not the end of the method but its steady state: in the cloud, upgrades and feature packs arrive on a schedule, and each one needs planning and testing.
Transition paths
Activate content differs by how you get to S/4HANA. A new implementation starts fresh. A system conversion converts an existing ECC system in place. A selective data transition builds a new system and moves selected data and configuration. Contoso Motor Co. is moving from SAP ECC 6.0 EHP 8 to SAP S/4HANA Cloud Private Edition under RISE with SAP. The phases are the same whichever path is chosen; the tasks inside them differ.
| Transition path | Starting point | What moves | Testing emphasis |
|---|---|---|---|
| New implementation | A fresh system | Selected master data and open items | Standard processes tested from scratch against Fit-to-Standard decisions |
| System conversion | The existing ECC system, converted in place (Contoso) | Configuration, custom code and full history | Regression of today's processes plus checks on converted data and changed functions |
| Selective data transition | A new system shell | Chosen configuration and selected data | Both: redesigned processes and reconciliation of the data that was moved |
Agile inside a phased frame
Activate is phased at the top and agile inside. Phases and their gates give executives predictable checkpoints. Inside Realize, the team works in sprints: configure a slice of scope, show it to the business, fix what they find, and move on. Testing is part of each sprint, not something saved for the end.
- Plan the sprintPick a slice of scope from the backlog, such as fleet pricing for order to cash
- ConfigureBuild the slice in the development system
- TestUnit and string tests as the configuration is completed
- Show the businessDemonstrate the slice to process owners such as Maria
- Fix and move onFeedback becomes backlog items; the next sprint starts
| Phase | Typical Contoso milestone | Who leads |
|---|---|---|
| Prepare | Project kickoff; Cloud ALM project and teams set up | Grace (PMO lead) |
| Explore | Fit-to-Standard complete for order to cash; requirements approved | Process owners such as Dan and Maria |
| Realize | SIT cycles and UAT complete | Priya (test lead) with the build teams |
| Deploy | Cutover executed; Q3 go-live | Luis (cutover manager) |
| Run | Hypercare closed; first regression for an update | Support organization |
Contoso's program mapped to the Activate phases.
Why the method matters to quality
A methodology can sound like paperwork. For anyone responsible for proving that the system works, Activate is useful for a simple reason: it tells you when each kind of evidence should exist. Requirements should exist at the end of Explore. Test cases should exist before integration testing starts in Realize. Acceptance should be recorded before Deploy. When a program is late, the first sign is usually evidence that should exist and does not, and the phase model lets you spot that early instead of at the go-live meeting.
It also gives everyone a shared calendar. Business users know when they will be needed for workshops, for acceptance testing and for cutover. Partners know which deliverables they owe at each gate. The customer's PMO can compare progress across workstreams using the same phase names, rather than translating between a partner's private method and the customer's own.
What would you do?
Contoso's CFO asks Grace why the program wants business users in workshops during Explore instead of "just collecting requirements in a document". What is the best explanation?
- SAP Activate combines SAP Best Practices, a methodology, and tools such as SAP Cloud ALM.
- The six phases are Discover, Prepare, Explore, Realize, Deploy and Run.
- Discover precedes the project; Run is the steady state of operating and upgrading.
- Activate is phased at the top and agile inside, with testing built into Realize sprints.
Check your understanding · not graded
Lesson check
1. Which list gives the Activate phases in order?
2. Which three elements make up SAP Activate?
3. Which phase happens before the project formally starts?
4. Which phase includes Fit-to-Standard workshops?