Lesson 1 of 5
Preparing Fit-to-Standard
9 min
Fit-to-Standard is the heart of the SAP Activate Explore phase. Instead of asking the business to describe its processes from scratch, the project shows how SAP's standard processes work and asks one question again and again: does this fit, and if not, why not? Good workshops depend almost entirely on preparation. A team that walks in with the wrong system, the wrong people or no test data spends the workshop apologizing instead of validating.
Fit-to-Standard replaces the classic blueprint of older SAP methods. A blueprint started with the customer's current processes and designed the system to match. Fit-to-Standard starts with SAP Best Practices and records only the deltas that genuinely matter. For a conversion like Contoso's, where ECC configuration is carried over, Fit-to-Standard focuses on processes that change in SAP S/4HANA and on new standard functions the business wants to adopt.
The content you prepare from
Choosing the demo system
SAP's learning content for the private edition describes three options. The SAP S/4HANA Fully-Activated Appliance is a ready system with Best Practices and Fiori apps active, and SAP recommends it for most customers, including conversions. A customer evaluation system built by SAP ECS takes longer and costs more but suits larger customers who want to reuse configuration. A converted sandbox of the customer's own system is realistic but often not ready in time, and Best Practices cannot be activated in it the same way.
| Option | Strength | Watch out for | Contoso's use |
|---|---|---|---|
| Fully-Activated Appliance | Ready quickly with standard processes and apps active | Generic demo data, not Contoso's | Main demo system for new S/4HANA functions |
| Customer evaluation system | Can be shaped and later reused | Lead time and cost | Not used |
| Converted sandbox | Shows Contoso's own data and settings | Often late; limited Best Practices activation | Used to show how converted ECC processes behave |
In the public edition, partner experts typically demonstrate in the starter system, after creating test users for each business role and running every test script once to be sure the system is ready.
Organizing the workshops
- Review the process flows and note which business roles do most of the tasks in each process.
- Group processes that share the same main roles, so the same people stay engaged all day.
- Size each workshop by the length of its test scripts: SAP's guidance suggests roughly one to two processes for a half day and two to three for a full day.
- Run the chart of accounts and organizational structure workshops first; the rest can run in parallel.
- Invite at least two and no more than four representatives per business role.
- Send configuration questionnaires ahead of time and collect values, master data examples and integration needs before the session.
- Four weeks beforeScope confirmedSolution processes in scope agreed and loaded into the Cloud ALM project
- Three weeks beforeWorkshops groupedProcesses grouped by role and sized; calendar sent with named attendees
- Two weeks beforeBusiness enabledKey users get short sessions on SAP terms, master data and the workshop approach
- One week beforeSystem dry runEvery test script run end to end with the test users in the demo system
- Workshop dayShow and tellStandard demonstrated; fit, values and deltas captured in Cloud ALM
What would you do?
Contoso's order-to-cash workshop is in five days. The partner consultant has not yet run the test scripts in the demo system, and two of Maria's key users have not seen any SAP S/4HANA screens. What should Grace prioritize?
- Fit-to-Standard starts from SAP Best Practices and records only the deltas that matter.
- Prepare from scope, Process Navigator content, standard test scripts, configuration questionnaires and a working demo system.
- For the private edition SAP recommends the Fully-Activated Appliance for most demonstrations.
- Group processes by role, size by test script length, start with chart of accounts and org structure, and dry-run every script.
Check your understanding · not graded
Lesson check
1. How does Fit-to-Standard differ from a classic blueprint?
2. Which demo system does SAP Learning recommend for most private edition customers?
3. Which workshops should run first?
4. How many representatives per business role does SAP Learning suggest?