5 questions to ask before an S/4HANA fit-gap

A fit-gap study often starts with "what does the standard do and how are we different". But a few questions need answers before the workshops begin. If they stay open, the same topics come back in every meeting.

1. Which S/4HANA model?

On-premise, private cloud and public cloud set different limits for customisation and different upgrade rhythms. The answer to "can we do this?" depends on it.

2. Do we start from the standard scope?

Starting from SAP's best-practice scope (scope items) wherever possible keeps the gap list short. For each gap, ask openly: change the process or change the system?

3. How will local requirements be met?

For Turkey-specific needs such as e-Invoice, e-Ledger and e-Waybill, the solution should be chosen early. Adding them later affects both design and test schedules.

4. Chart of accounts and master data strategy

The relation between local and group chart of accounts, master data cleansing and ownership should be discussed before fit-gap. In most projects, data is the slowest part of the migration.

5. Who runs testing and training?

Key users' time is the real constraint of a project. Test scenarios and training responsibilities should be planned during blueprint.

In short: fit-gap is not a system comparison, it is a series of decision meetings. Framing the decisions up front makes the workshops far more productive.