SAP Activate methodology explained

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal, October 2026

The SAP Activate methodology is SAP's framework for implementing its software: six phases — Discover, Prepare, Explore, Realize, Deploy and Run — with fit-to-standard workshops in place of a blueprint, preconfigured best-practice content to start from, and a quality gate at every phase transition. Almost every current SAP project is planned in its vocabulary.

As of October 2026, SAP publishes the methodology as roadmaps in the SAP Activate Roadmap Viewer, with separate roadmaps for RISE with SAP (SAP Cloud ERP Private, the SAP S/4HANA Cloud Private Edition), GROW with SAP (SAP Cloud ERP, the SAP S/4HANA Cloud Public Edition) and on-premise projects — the same six phases in each — and the cloud roadmaps are also delivered as task lists inside SAP Cloud ALM, the implementation and operations tool that took over that job from SAP Solution Manager for cloud projects.

What are the SAP Activate phases?

The SAP Activate phases are Discover, Prepare, Explore, Realize, Deploy and Run, in that order, and each one exists to produce a named set of things that the next phase consumes. The table lists them the way the roadmaps do.

Discover is often done by the customer alone with a partner's help, so a consultant's first project week is usually in Prepare. Run is where AMS work lives, and the end of Deploy is the cutover weekend described in cutover and hypercare.

What is a fit-to-standard workshop?

A fit-to-standard workshop is a session in the Explore phase where a consultant runs a standard process in a live system in front of the process owners and asks, step by step, whether it works for them. A purchase order raised, approved, received and invoiced, say, with the buyer and the accounts-payable lead watching the screen. Where the answer is yes, the standard is adopted and documented as such. Where the answer is no, the consultant records a delta requirement with its business reason, and the team later decides whether the delta becomes configuration, a key-user extension, a side-by-side app on SAP BTP, or a change to the way the company works. Fit-gap is the older name for the same exercise, and job adverts still use it.

The skill is in the conversation: keeping the business looking at what exists rather than describing what they had, and pushing back, politely, on deltas that are habits rather than needs. Delta design — the term for the follow-up sessions where deltas are specified — produces the backlog that Realize works from.

What are scope items and best-practice content?

A scope item is one preconfigured business process delivered by SAP as part of SAP Best Practices, identified by a short code: J59 is Accounts Receivable, BD9 is Sell from Stock. Each scope item ships with a process flow diagram, a configured system behind it and a test script, and a project selects the scope items it needs and activates them in the starter system before the first workshop. The workshops only work because there is something to show.

Since the SAP Best Practices Explorer was retired, the process diagrams and test scripts are published through SAP Signavio Process Navigator. For a consultant the content sets two things: the default, so knowing the standard process in your area cold is the entry ticket; and the test backbone, so much of Realize is adapting delivered test scripts to the deltas rather than writing tests from nothing.

What are the SAP Activate workstreams and quality gates?

The workstreams are the lanes of work that run across all six phases, and the quality gates are the checks at each phase transition. As SAP's Roadmap Viewer lists them, the workstreams are Project Management, Solution Adoption, Customer Team Enablement, Application Design and Configuration, Extensibility, Integration, Testing, Data Management, Technical Architecture and Infrastructure, Operations and Support, and Analytics. Each roadmap task belongs to one workstream and one phase, so a project plan built from the roadmap is a grid: phases across, streams down.

There is one quality gate per phase transition. Each gate lists the deliverables that must exist and the sign-offs that must be given before the next phase spends money: the Prepare gate wants the charter and the plan, the Explore gate wants the backlog and confirmed scope, the Realize gate wants passed test cycles and a rehearsed cutover, the Deploy gate is the go or no-go decision itself. Project managers run their calendars on the gates, and the test manager owns most of the evidence the Realize gate asks for.

What is the SAP Activate Roadmap Viewer, and what are accelerators?

The Roadmap Viewer is where SAP publishes the methodology: one implementation roadmap per product and deployment, each of which can be filtered by phase and by workstream. A roadmap has three levels. Deliverables say what must exist by the end of a phase, tasks say how each deliverable is produced, and accelerators hang off the tasks. SAP defines an accelerator as a document, template or web link that helps a consultant, a customer or the project manager complete a task with less effort: a project plan, a guide to running fit-to-standard workshops, a configuration questionnaire, a quality gate checklist.

In practice nobody writes an Activate plan from an empty page. The team takes the roadmap's deliverables and tasks, removes what does not apply, and adds owners and dates. As of October 2026 the viewer sits inside SAP for Me and asks for an S-user to sign in, and the same content comes preloaded in SAP Cloud ALM. SAP's free course on the implementation tools and methodology explains the structure without a login.

Is SAP Activate agile or waterfall?

It is both, in different places. The six phases run in sequence and each one ends at a quality gate, which is the waterfall part. Inside Realize the build is agile: the deltas found in Explore sit in a product backlog, a product owner from the business sets the order, and the team configures and develops in sprints, with unit tests and some string tests inside each sprint. A full integration test and a user acceptance test still close the phase before Deploy can start. SAP's course material describes Realize as iterative and incremental and aligns the Project Management workstream with the PMBOK standard, so fixed gates with sprint-sized builds between them is the method as designed. How strictly the sprints are run varies from one programme to the next; the gates rarely move.

How does SAP Activate differ in the public cloud and the private cloud?

The phases, workstreams and gates are the same; what differs is where a project may start from, which system the workshops run in, how a gap may be closed and who sets the upgrade dates. The table compares the public cloud roadmap with the one used for private cloud, which an on-premise project follows closely.

The practical effect is on Explore. In the public cloud a delta that configuration cannot meet becomes an extension or a change to the process, so the workshop has to settle it on the day. In a conversion much of Explore is spent deciding which existing custom code and which old process variants are carried across at all.

How does SAP Activate differ from ASAP?

ASAP began with a blueprint and SAP Activate begins with a working system. The older methodology's five phases — Project Preparation, Business Blueprint, Realization, Final Preparation, Go Live and Support — spent months in requirement workshops producing documents that described the future system, followed by a realization phase that built what the documents said. The risk was structural: the business specified from memory of the old system, the documents drifted from what was possible, and the first time anyone saw working software was late. SAP Activate inverts the order. The preconfigured system comes first, requirements are captured as deltas from it, often by the business analyst on an SAP project, and build happens in iterations the business sees. SAP presents Activate as the successor of both ASAP and SAP Launch, the methodology it used for its cloud products.

Blueprint thinking still shows up in candidates and in some project shapes — large brownfield conversions and template rollouts keep more of the documentary style — but the cloud editions sold under RISE and GROW more or less require the fit-to-standard style, and Public Edition requires it outright.

What does each phase mean for your week?

Each phase has its own rhythm, and the phase — not the role — decides what a given week looks like.

• Prepare — reading the scope, learning the client's organisation, preparing demo data for your area, checking the starter system works. Quiet, and the last quiet you will get.
• Explore — workshop days, usually on site, with evenings spent writing up deltas and preparing tomorrow's demo. The most sociable phase and the one where a functional consultant's reputation is made.
• Realize — configuration in the morning, a developer conversation about an extension at noon, test scripts in the afternoon, a stand-up somewhere in between. Increasingly remote as the phase goes on.
• Deploy — cutover checklists, rehearsals at odd hours, the go-live weekend, then a hypercare desk with the key users. The phase that produces the stories interviews ask for.
• Run — tickets, small changes, release reviews, and the beginning of the next project's Discover.

A fuller picture of those days is in a day in the life.

Which certification covers SAP Activate?

SAP Certified - Project Manager - SAP Activate (exam code C_ACT, now a scenario-based assessment) covers the methodology: the phases, the workstreams, the quality gates and the agile delivery practices inside Realize. It is listed on SAP Learning and is the one project managers and delivery leads are asked for; a functional consultant is judged on the area certification instead, and on how many Explore phases they have run.