SAP Activate — How a Real Project Runs
🎯 In plain words
🧠 The six Activate phases
Every project moves through these six phases in order. Here's what happens in each — and what you, the MM consultant, actually deliver:
| Phase | What happens | MM consultant delivers |
|---|---|---|
| Discover | Trial system, business case — does SAP fit, and is it worth it? | Learn the value; understand what the business wants to gain. |
| Prepare | Project setup — team, plan, and systems provisioned. | Help set up environments & the project plan for MM. |
| Explore | Fit-to-Standard workshops — show the standard process, identify gaps (the "delta"). | Run the P2P Fit-to-Standard; capture gaps and build the Business Process Master List (BPML). |
| Realize | Configure & build (sandbox → DEV), transport to QAS, test cycles, WRICEF developments. | Do the MM config; run unit & integration testing. |
| Deploy | Cutover, data migration, go-live readiness checks. | Cutover plan + data load for MM (vendors, materials, open POs, stock). |
| Run | Hypercare + ongoing support after go-live. | Stabilize the system; handle the early tickets. |
A handy way to remember the order: Discover, Prepare, Explore, Realize, Deploy, Run.
🧠 Fit-to-Standard & Best Practices
This is the heart of Activate. Instead of asking "how do you work today, and how do we copy that?", you start from SAP's standard Best-Practice process and walk the business through it:
- Show the standard. In a Fit-to-Standard workshop you demonstrate the out-of-the-box P2P (or inventory, or invoice) process. The business confirms what fits.
- Configure only the deltas. Where the standard doesn't fit, you note the difference and configure just that — not the whole process.
- Document the WHY. Every config choice goes into a configuration rationale / config workbook: what you set, and the reason. This is gold during testing, audits, and the next upgrade.
- Real gaps become WRICEF items. If a need can't be met by configuration, it becomes a development: Workflow, Report, Interface, Conversion, Enhancement, Form.
🧠 Where the MM consultant adds value
On a real project, the MM consultant is the bridge between the warehouse/buying team and the system. You:
- Translate business needs into config — turn "we value stock per plant" into the right setting.
- Defend the standard — push back on "we need custom" when the standard already does the job.
- Write functional specs for real gaps — hand the developer a clear spec for each WRICEF item.
- Coordinate across modules — MM touches FI (valuation, invoice posting), SD (stock for sales), and PP (components for production).
- Support cutover & hypercare — load the data, then stand by to fix the first wave of issues.
🛠️ Do it now — a writing exercise
No T-code today — this is the work a consultant really does. Open a blank page and write two short documents for our PakSteel project:
- A one-page Fit-to-Standard agenda for the P2P process. List, in order, what you'd demo in the workshop: who's in the room, the standard steps you'll walk through (PR → PO → goods receipt → invoice), and where you'll stop to ask "does this fit?".
- A configuration rationale for one PakSteel decision. Pick plant-level valuation: write what you chose, and why (e.g. each plant needs its own stock value for costing) — in two or three plain sentences a manager could read.
Tip: pull the actual config from the setup hub and the actual processes from the scenarios hub so your documents describe the real thing, not a guess.
Config to rationalize Processes to demo Curriculum- Fit-to-Standard ≠ fit-gap analysis. The old way mapped the customer's current process and found gaps. Activate flips it: you start from the standard and challenge every "we need custom".
- Over-customizing kills upgrades. Each custom build is something you must re-test and maintain forever — and it can block the next SAP upgrade. Adopt the standard wherever you can.
- Never skip the WHY. A config with no documented reason becomes a mystery in six months. Always write the configuration rationale.
🔗 Connects to
- Phase 14 — Cutover & Migration: this is the Deploy phase in action — loading data and going live.
- Phase 17 — Consulting Skills: running workshops, defending the standard, and writing specs are the soft skills behind Activate.
- Phase 16 — Certification: knowing the methodology and its vocabulary is part of looking like a real consultant.
🎓 Quick recall
Senior-consultant vocabulary — the words you'll hear in your first week on a project.
Name the six Activate phases in order.
Discover, Prepare, Explore, Realize, Deploy, Run.
What happens in a Fit-to-Standard workshop?
You demonstrate SAP's standard Best-Practice process to the business, confirm what fits, and capture the differences (the "delta") that need configuration or development.
What is hypercare?
The intensive support period right after go-live (in the Run phase) where the team stabilizes the system and quickly handles the first wave of issues.
What does WRICEF stand for, roughly?
The six kinds of custom development: Workflow, Report, Interface, Conversion, Enhancement, Form.
✅ You're ready to move on when…
- You can name the six Activate phases in order and say what happens in each.
- You can explain Fit-to-Standard and why it's different from old fit-gap analysis.
- You've written a configuration rationale for one PakSteel decision.