Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP S/4HANA?

What changed between ECC and S/4HANA, why the data model matters more than the interface, and what the deadlines mean for planning.

In short

SAP S/4HANA is SAP's current ERP suite, built to run on the HANA in-memory database. The visible change is Fiori, the web interface. The structural change is the data model: aggregate and index tables were removed in favour of calculating from the line items, which is why reporting behaves differently and why migration is more than a technical upgrade.

Why It Matters

Why this matters in practice

Most businesses encounter S/4HANA as a deadline rather than a choice, which is the wrong way round. The migration is an opportunity to retire customisations that have accumulated for a decade, and a risk of carrying them forward untouched. The decision that matters is not when to move but what to take with you.

Simplified data model — aggregates calculated rather than stored
Fiori replaces SAP GUI as the primary interface
Universal Journal brings FI and CO into a single table
Several ECC modules are replaced rather than upgraded
How It Works

How it works in practice

1

The database changes

HANA is columnar and in-memory. Reporting that relied on pre-aggregated totals is rebuilt to read line items directly.

2

The Universal Journal

Financial accounting and controlling share one line-item table, which removes a whole category of reconciliation between them.

3

Custom code is assessed

Code that read removed tables will not run. A custom code analysis is the first real deliverable of any migration.

4

Fiori becomes the front end

Role-based apps rather than transaction codes. Adoption is a change-management exercise, not a technical one.

5

Master data is simplified

Customer and vendor masters are unified into Business Partner, which is mandatory and often the largest data workstream.

Worked example

A worked example: what the data model change actually does

In ECC, a finance posting touched several tables — the document header and lines, separate controlling tables, separate asset and material ledger structures — plus pre-built aggregate and index tables maintained so that reports could run at acceptable speed.

In S/4HANA those postings land in one line-item table and the aggregates are computed on read, because the column store is fast enough to do it live. Two consequences follow. Reconciliation between finance and controlling largely disappears, because they are no longer separate records that could diverge — they are the same record. And a whole class of month-end jobs whose purpose was rebuilding aggregate tables stops existing.

The migration consequence is the one that catches people. Custom ABAP that reads the old aggregate or index tables directly has to be remediated, because those tables may be replaced by compatibility views or not exist at all. This is why the custom code inventory is the first real task of any ECC-to-S/4HANA assessment: the size of that inventory, more than any other single factor, determines whether a brownfield conversion is a few months of work or a year of it.

Key terms

The vocabulary, briefly

Term What it means
Universal Journal The single table (ACDOCA) holding finance and controlling postings together, removing the old reconciliation between them.
HANA The in-memory column-store database S/4HANA runs on, which is what allows aggregates to be calculated on read.
Fiori The current user experience layer, role-based and browser-delivered, replacing much of the classic SAP GUI.
RISE with SAP SAP's bundled subscription offering covering software, infrastructure and services under one contract.
Compatibility scope Older functionality usable for a transitional period. Time-limited, which matters when planning around it.
What Goes Wrong

Common mistakes worth avoiding

Treating it as a technical upgrade

The data model change means custom code and reporting both need real work. Scoping it as a database migration understates it substantially.

Carrying every customisation forward

A migration is the cheapest moment to retire code nobody can justify. Most estates can drop a meaningful proportion.

Leaving Business Partner conversion late

It is mandatory, it touches master data everywhere, and it is consistently underestimated.

Planning around the deadline alone

Maintenance dates have shifted before and are conditional. Plan on business value, with the deadline as a constraint rather than the reason.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Custom objects in scope The single biggest driver of conversion effort. Inventory it before estimating anything. Counting objects rather than usage; much custom code is dead and can simply be retired.
Data volume by module Drives both downtime and licence sizing. Measuring current volume without archiving first, which inflates the project.
Simplification item impact How many SAP-flagged changes affect your configuration. Reviewing the list without testing, since impact depends on your actual usage.
Readiness check findings The structured output SAP's own tooling produces. The cheapest first evidence available. Treating the output as a plan; it is an input to one.
FAQ

Questions we are asked about this

ECC runs on any supported database and stores aggregates; S/4HANA runs only on HANA and calculates them. That difference drives the interface, the reporting model and the custom code impact.
No. It is offered on-premise, in private cloud and as a public cloud edition. The editions differ in how much configuration you control and how updates are applied.
Mainstream maintenance for Business Suite 7 has a published end date, with extended maintenance available beyond it at additional cost. So the real question is not whether but when, and on what basis. The deadline is also the most-used closing lever in SAP sales, which is why the sound sequence is assessment first — custom code, data volumes, process fit — and a date chosen from that evidence rather than from the calendar.
Brownfield converts your existing system in place, keeping configuration, history and custom code, and remediating what the new data model breaks. Greenfield builds a new system on standard processes and migrates selected data into it. Brownfield is usually faster and cheaper but carries your accumulated complexity forward; greenfield is the opportunity to leave it behind and the cost of rebuilding what works. Hybrid approaches exist and are common in practice.
No. It runs on-premise, in a private cloud, and in a public cloud edition, and the editions differ materially in how much you can configure and extend. Public cloud trades flexibility for a standardised upgrade path; on-premise and private cloud keep more control and more responsibility. This choice shapes your extension strategy more than almost any other, so it belongs early in the assessment rather than late.
It gets inventoried, classified and triaged. A surprising share is typically dead code that can be retired outright. Some needs remediation where it reads tables the new data model changed. Some should move out of the core to side-by-side extensions on BTP, which is the pattern that keeps future upgrades cheap. Treating the whole inventory as something to be carried across unchanged is the expensive default.
Related

Where to read next

SAP ECC to S/4HANA migration guide

Read more

Brownfield vs greenfield migration

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.