Fit-to-Standard Workshops for SAP S/4HANA Cloud

Written by Scheer IDS Netherlands Specialist. Updated 21 October 2026.

Fit-to-Standard workshops are the working sessions in which Scheer IDS Netherlands and your process owners walk through SAP's predefined best practice processes in SAP S/4HANA Cloud, Public Edition, and decide per process whether it fits as delivered. After reading this you will know what the workshops cover, who should attend, how gaps are handled and how to prepare.

What is a Fit-to-Standard workshop?

A Fit-to-Standard workshop is a structured session in which a best practice process is demonstrated in a prepared SAP S/4HANA Cloud system and compared with how your organization works. SAP delivers hundreds of such processes with preset configuration, sample master data and test scenarios. The workshop establishes where your business fits the standard and where it does not. It does not replace process design for areas outside the delivered scope.

The idea is the reverse of a classic blueprint phase. In a traditional ERP project, requirements are written first and the system is built to match them. With a SaaS ERP such as SAP S/4HANA Cloud, Public Edition, the standard is already there and is updated twice a year. The question therefore changes from "what do we want?" to "what do we really need to do differently, and why?"

The workshops are built on scope items. A scope item activates the functionality for an end-to-end process or a specific scenario, and comes with its own configuration, test scripts and documentation. Several scope items together form an end-to-end process such as Order to Cash, Source to Pay or Record to Report.

Where do the workshops fit in an SAP S/4HANA Cloud implementation?

The workshops take place early in the project, in the Explore phase of SAP Activate, after the Prepare phase has set up the project and before the Realize phase starts. SAP Activate follows the phases Prepare, Explore, Realize, Deploy and Run, and it is an iterative method. That means the outcome of the workshops can still be refined as insight grows, but scope changes later in the project always cost time.

Our implementation approach builds on SAP Activate and starts from the processes you selected during the assessment. If you have not yet done an assessment, the Discovery Assessment comes first. It answers whether the Public Edition is the right choice, which functionality you need now or later, which integrations are required and in which countries you will use the system. The workshops then take that scope and test it in detail.

The requirements that come out of the workshops, after an approval cycle, become project tasks for the sprints of the Realize phase. When the project is managed in SAP Cloud ALM, which is part of the SAP S/4HANA Cloud license, gaps are captured there and flow directly into the sprint backlog. We describe that in our blog on SAP Cloud ALM for implementation.

Who should attend a Fit-to-Standard workshop?

The attendees are the people who own the process in daily operations, plus the consultants who know how SAP delivers it. A workshop with only IT staff produces a technical review; a workshop with only managers misses the exceptions that matter. The balance matters more than the number of people.

• Process owners and key users from finance, sales, procurement, production or services, depending on the process under review. They decide whether the standard behavior is acceptable.
• Functional consultants who run the process in the prepared system, explain the variants and capture each gap.
• An integration or BTP specialist when the process touches other systems, because interfaces are better scoped in the session than discovered during testing.
• A project manager who tracks decisions and keeps the scope consistent between workshops.

Our consultants cover the end-to-end processes Order to Cash, Design to Operate, Source to Pay, Record to Report and Hire to Retire, within the Manufacturing, Consumer Products, Life Sciences and Professional and Technical Services sectors. That sector knowledge shortens the sessions, because the typical variants for your industry are already known.

How does a Fit-to-Standard workshop run, step by step?

A workshop follows a fixed pattern per process: demonstrate the standard, compare it with your practice, classify the differences and record the decision. The pattern is repeated for each end-to-end process in scope, so that the results are comparable and nothing is decided informally.

1. Demonstrate the best practice. The consultant runs the process in the prepared system with sample master data, step by step, so that the participants see the real screens and not a slide.
2. Compare with your practice. The process owners say where their current way of working differs: another approval, another document layout, another report.
3. Select the variant. Many processes have variants. Choosing the right one often removes the apparent gap without any change.
4. Classify each remaining gap. The team decides whether to adopt the standard, adjust the configuration or build an extension.
5. Record and approve. The decision, the reason and the owner are written down, and approved gaps become tasks in the project plan.

Examples of gaps that surface in these sessions include a changed layout of sales invoices, a specific report that is critical for warehouse management, a new workflow for approving purchase invoices and a link between SAP S/4HANA Cloud and another system. None of these is unusual, and each is handled differently, as the next section shows.

How are gaps handled: adopt, configure or extend?

A gap has three possible answers, in a fixed order of preference: adopt the standard process, adjust it within the configuration options, or build an extension. The order protects what we call a Clean Core, an ERP that stays close to the standard so that maintenance remains low and the twice-yearly updates can be taken without rework. The order stops applying when a legal or operational requirement leaves no alternative.

Our experience is that most apparent gaps are habits, not requirements. A team that has used the same invoice layout for ten years will say it is needed, until the workshop shows what the alternative costs in maintenance. We say so openly, because the final decision belongs to you. Where an extension is justified, we record why, so that the next release update does not come as a surprise.

Why do Fit-to-Standard workshops speed up an implementation?

The workshops speed up a project because they decide the scope against a system that already works, so there is less to design, build and test afterwards. Per sprint, a number of process variants are picked up and fully set up, tested and documented, which takes two to three weeks according to our description of the Realize phase. This only holds when the scope is stable at the start of the sprints.

The standard also brings its test scenarios. Best practice processes in SAP S/4HANA Cloud are delivered with manual and automated tests, so every process adopted as delivered arrives with its test material. That shifts effort from writing tests to executing them. The ERP Variants of the Public Edition add to this, because they give a quick foundation for the desired functionality and allow the system to be expanded step by step, instead of in one big-bang project.

There is a second benefit that is easy to overlook. The workshops are where your employees first meet the new system. They see the processes running and can ask questions. That early contact makes adoption easier, which is why we advise starting with the functional scope in phases.

How do you prepare your organization for the workshops?

Preparation means choosing the participants, collecting real examples and agreeing how decisions are made before the first session. A workshop series without a decision rule slows down, because every gap turns into a discussion. The following points help.

• Name a decision owner per process. Someone must be able to accept a standard behavior on behalf of the department.
• Bring real documents and exceptions. Real invoices, orders and reports expose differences faster than a description.
• Know your starting point. A new ERP, a spin-off of a business unit, a migration from SAP ECC and an extension of an existing ERP each lead to different workshops. Our assessment looks at each of these paths.
• List the integrations. Systems that must stay connected are scoped in the session, so BTP integration work is planned from the start.
• Reserve time for follow-up. Plan for the time needed to approve gaps between sessions, because approval cycles take calendar time.

Be realistic about effort. The workshops require more of your key users' time than many teams expect, and they cannot be delegated to the project team alone. In return, the decisions are theirs, and so is the result. If you run SAP S/4HANA Cloud as a Two-Tier ERP next to an existing SAP ECC or SAP S/4HANA system, the workshops also define which processes stay central and which move to the cloud.

What do you have after the workshops?

After the workshops you have a documented fit-gap result, an agreed scope per end-to-end process and a list of approved extensions and integrations, each with an owner. That result feeds the sprint plan and the budget, and it is the reference when someone later asks why a process works the way it does. The result does not replace testing: a fit that looks right in a workshop still has to be proven in the sprint.

If you want to see what this looks like in practice, our customer references for SAP S/4HANA Cloud, Public Edition describe projects delivered on this approach. For the services around the workshops, including managed services after go-live, see our overview of Managed Services.

Frequently asked questions

Fit-to-Standard workshops decide the scope of your implementation against a system that already works. Prepared well, they replace long requirement documents with short, documented decisions that your own process owners have made.