SAP Activate Demo — end-to-end tutorial

Goal

By the end of this tutorial you will have imported the SAP Activate (Demo) Scrydon Pack into your tenant, created a fresh instance for the fictional Northwind Retail Group ECC 6.0 → S/4HANA Cloud Public migration project, walked the project through all six SAP Activate stages (Discover → Prepare → Explore → Realize → Deploy → Run), and produced a signed hypercare exit report.

Anika Schroeder, Program Director at Northwind Retail Group, and Dr. Stefano Bassi (DXC Solution Architect) are the fictional principals. The 12-country migration, the €16.9 m budget, the BeNeLux Wave 1 cutover — all fictional — exist solely to give the SAP Activate flow a concrete narrative to walk through.

Prerequisites

You have a Scrydon deployment with the agentic and ontology surfaces enabled. Set the following env vars in your shell for the import step:

export SCRYDON_URL="https://<your-scrydon-url>"
export ORG_ID="<your-org-id>"
export SESSION_COOKIE="$(cat ~/.scrydon/session-cookie)"

Step 1 — Download the pack

Download sap-activate-demo-3.0.0.scrydon-pack.tar.gz

mkdir -p sap-activate-tutorial && cd sap-activate-tutorial
curl -O https://docs.scrydon.com/static/process-pack-examples/sap-activate-demo-3.0.0.scrydon-pack.tar.gz

The pack is ≈ 4 KiB.

Step 2 — Inspect the pack

bunx @scrydon/sdk-authoring pack inspect sap-activate-demo-3.0.0.scrydon-pack.tar.gz

Pack:
  Package:  sap-activate-demo@3.0.0
  Contents: ontology@3.0.0, process-flow@3.0.0
  Install order: ontology → process-flow
  ontology: sap-activate-demo@3.0.0
  process-flow: sap-activate-demo (6 stages)

Step 3 — Upload the pack

curl -X POST "$SCRYDON_URL/api/packs/import?organizationId=$ORG_ID" \
  -H "Cookie: $SESSION_COOKIE" \
  -F "file=@sap-activate-demo-3.0.0.scrydon-pack.tar.gz"

200 response carries the new processTemplateId and a stub ontology branch.

Step 4 — Create a new project instance

Browse to $SCRYDON_URL/process-flows. The SAP Activate (Demo) card appears under the Enterprise Implementation tag. Click New from template, name the instance Northwind Retail S/4HANA Cloud Migration.

The instance opens on the wizard view by default. The left rail lists the six stages and their tasks; the right panel walks through each task as a scene:

• Discover — 10 tasks (strategic assessment).
• Prepare — 10 tasks (project setup, governance, sandbox).
• Explore — 12 tasks (fit-to-standard workshops, backlog).
• Realize — 12 tasks (sprint execution, WRICEF, testing).
• Deploy — 7 tasks (cutover, go-live).
• Run — 6 tasks (hypercare, optimisation).

Stages are sequential (stageFlow: "sequential"), tasks within a stage run in parallel where the DAG allows. Each stage ends in a Q-Gate sign-off task — the formal SAP Activate gate.

Step 5 — Discover: scope the strategy

The Discover stage is the strategic-assessment phase. Anika and the steering committee walk through 10 tasks:

Anika then opens Steering committee sign-off on strategy — the approval action gating the Q-Gate. The CFO Pieter Vandermeer signs as sponsoring executive.

Step 6 — Prepare: set up project governance

The Prepare stage is when the project moves from strategy to execution. Anika drives 10 setup tasks:

Download 01-project-charter.md — Northwind Retail Group's project charter: scope, governance, 18-month timeline split into 3 waves, €16.9 m budget, top-5 risks.

The 10 tasks include creating the WBS, defining RACI for the 47-person project team, provisioning the SAP Best Practice sandbox tenant (used for fit-to-standard workshops in the next stage), establishing the Solution Manager + Signavio + LeanIX tooling, and onboarding all 47 team members. The stage ends with the Prepare Q-Gate sign-off.

Step 7 — Explore: Fit-to-Standard workshops

The Explore stage is where the meat of the project happens — Fit-to-Standard (F2S) workshops map as-is processes to SAP Best Practice scope items, gap analysis identifies WRICEF objects, and the backlog gets signed by stakeholders.

Download 02-fit-to-standard-outcomes.md — F2S Cycle 1 outcomes for MM + SD + FI (5-day workshop, 12–16 May 2026). 84 % of as-is fits 1:1 to Best Practices; 7 RICEFW objects identified; 31 custom Z-tables consolidated into a single condition technique.

The 12 Explore tasks walk the team through every aspect: workshop facilitation, gap documentation, target architecture, interface maps, testing strategy, learning needs analysis, change impact analysis, and the data load plan. The stage ends with the Explore Q-Gate sign-off — Anika, Cindy (FI), Sofie (SD), Marek (MM), Dr. Bassi (DXC), and audit observer Jürgen.

Step 8 — Realize: build, test, prepare cutover

The Realize stage is the longest (37 weeks in the project plan). 12 tasks cover:

• Configure SAP system per backlog — sprint-by-sprint configuration of MM, SD, FI, CO, EWM, AA, PP.
• Develop WRICEF objects — the 7 backlog objects from Explore.
• Load customer master & transactional data — into the QA tenant.
• Execute unit testing, integration testing, UAT — three testing layers.
• Execute data migration testing / dry-run — full 60-hour cutover dress rehearsal in QA.
• Prepare cutover plan — see Step 9.
• Develop adoption & training materials — 87-store change network for Wave 1.

The stage ends with the Realize Q-Gate sign-off, which is the formal go/no-go for cutover. This gate runs a human-in-the-loop workflow ("Approve transition to Deploy?"): while it waits, the workflow action and the instance header show "Awaiting Human-in-the-loop acceptance" (not a generic "In Progress") and name the reviewer, so it's clear the run is paused on a person rather than stuck. Whoever you mapped to the gate's reviewer persona on this instance is notified (and may approve); if no one holds that persona, it falls back to the org role of the same name. The reviewer approves or rejects inline from the notification (Notifications → click the review → Approve/Reject), and the instance advances to Deploy. Tip: if you expect a notification but don't get one, check that your user is mapped to the reviewer persona — being the org owner is not the same as holding the "admin" persona/role.

Step 9 — Deploy: cutover & go-live

The Deploy stage executes the cutover plan. For Wave 1 (BeNeLux, 87 stores):

Download 03-cutover-plan.md — the 60-hour cutover plan: freeze ECC NL/BE/LU at Sat 18:00 CEST, migrate master and transactional data through Sunday, activate S/4 production tenant Sunday 12:00, validate, and open to stores at Mon 06:00 CEST.

The 7 Deploy tasks walk the cutover phase by phase. The approval action on Final Go/No-Go at T-12 hours is the last reversibility point. The wave finishes when stores transact successfully on S/4HANA Cloud Public.

Step 10 — Run: hypercare and BAU transition

The Run stage covers the 14-day hypercare period for each wave + the transition to business as usual. 6 tasks:

• Monitor KPI gate — close cycle time, order-to-cash error rate, predictive replenishment auto-approval rate, GL reconciliation variance.
• Triage hypercare incidents — P0 < 15 min, P1 < 1 h, P2 < 4 h.
• Daily war-room sync — full project team for first 7 days, then alternate-day.
• Country sign-off — per-country process owners formally accept S/4.
• Issue hypercare exit report — see below.
• Transition to BAU backlog — deferred enhancements move to the Run-stage standing backlog.

Download 04-hypercare-exit-report.md — Wave 1 (BeNeLux) hypercare exit report: 14 days, 47 tickets (0 P0, 3 P1, 11 P2, 33 P3+), all four exit-gate KPIs green by day 5.

Run is a recurring stage — once Wave 1 exits hypercare, the project loops back into Deploy for Wave 2 (DACH), then again for Wave 3. The same instance carries each wave through Deploy → Run as separate sub-task threads.

Three error variants worth seeing

Customising the pack

Northwind Retail's project plan diverges from the shipped pack in three places: the WBS structure, the country wave grouping, and the hypercare KPI definitions. Three customisation paths:

1. Fork the pack in TypeScript. Copy packages/sdk-authoring/src/process-flows/examples/sap-activate-demo/index.ts into your own SDK project, edit, change package.id and template.slug to a custom value (e.g. northwind-s4-migration), and rebuild with bunx @scrydon/sdk-authoring pack build src/pack.ts --outDir dist.
2. Add typed ontology contributions. A future release could add Sprint, Backlog, RicefwObject, QGate, KPI Object Types under the pack's ontology/manifest.json so tasks emit typed instances — making "show me all RICEFW objects across all waves" or "what hypercare incidents trace back to a specific Q-Gate" queryable.
3. Assign personas at instance time. The pack ships with no personas; each instance can wire its own org-specific personas in the agentic UI when the template instance is created.

If you fork, change the slug and package.id away from sap-activate-demo to avoid colliding with the example pack if it is ever imported into the same workspace.

Where to go next