What changed between ECC and S/4HANA, why the data model matters more than the interface, and what the deadlines mean for planning.
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.
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.
HANA is columnar and in-memory. Reporting that relied on pre-aggregated totals is rebuilt to read line items directly.
Financial accounting and controlling share one line-item table, which removes a whole category of reconciliation between them.
Code that read removed tables will not run. A custom code analysis is the first real deliverable of any migration.
Role-based apps rather than transaction codes. Adoption is a change-management exercise, not a technical one.
Customer and vendor masters are unified into Business Partner, which is mandatory and often the largest data workstream.
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.
| 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. |
The data model change means custom code and reporting both need real work. Scoping it as a database migration understates it substantially.
A migration is the cheapest moment to retire code nobody can justify. Most estates can drop a meaningful proportion.
It is mandatory, it touches master data everywhere, and it is consistently underestimated.
Maintenance dates have shifted before and are conditional. Plan on business value, with the deadline as a constraint rather than the reason.
| 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. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.