guide · migration
SAP ECC vs S/4HANA: what actually changes
A practitioner's comparison of the two systems — the architectural shift, where the performance really comes from, and how the clean core philosophy decides whether your conversion stays affordable five years from now.
Side-by-side comparison
| Area | SAP ECC | SAP S/4HANA |
|---|---|---|
| Database | Any RDBMS (Oracle, DB2, MS SQL, MaxDB) — row store, disk-optimised. | SAP HANA only — in-memory column store with compression and parallel scans. |
| Data model | Aggregate and index tables (BSEG/BSIS/BSAS, MSEG + MARD/MARC totals) kept in sync by updates. | Simplified model — ACDOCA universal journal, MATDOC for materials; aggregates become CDS views. |
| Field lengths | Material number 18 characters, classic customer/vendor masters. | Material number 40 characters, Business Partner as the single master for customer & vendor. |
| User experience | SAP GUI transactions, limited Web Dynpro / Portal. | SAP Fiori launchpad, role-based apps, responsive UI5, GUI only as fallback. |
| Programming model | Classic ABAP, SELECT loops, application-server-side aggregation. | Code-to-data — CDS views, AMDP, RAP for OData services, ABAP Cloud restrictions. |
| Extensibility | Core modifications, user exits, BADIs, appends — upgrades get expensive. | Key user in-app extensions, released APIs and side-by-side extensions on SAP BTP. |
| Analytics | Batch reporting, separate BW extraction for most insight. | Embedded analytics on live transactional data via CDS and Analytical Fiori apps. |
| Integration | IDoc, RFC, PI/PO middleware. | Same plus OData/REST APIs, Event Mesh and SAP Integration Suite (CPI). |
| Maintenance | Mainstream maintenance ends 2027 (extended 2030). | Maintenance committed to 2040 for SAP S/4HANA. |
Where the HANA performance comes from
No aggregates to maintain
Totals tables disappear, so posting programs write fewer rows and lock less. Period-end and high-volume postings run measurably faster because the update contention is gone.
Code pushdown
CDS views and AMDP move joins, aggregation and filtering into HANA. A nested-loop report that pulled millions of rows to the application server becomes a single set-based statement.
Smaller footprint
Columnar compression plus the removal of index and totals tables typically shrinks the database considerably, which shortens copies, backups and refresh cycles.
Real-time insight
Because analytics run on the transactional tables, operational reporting no longer waits for a nightly extract into BW.
The clean core philosophy
Most of the cost of an SAP landscape is not the conversion — it is every upgrade after it. Clean core is the discipline that keeps those upgrades boring.
- Keep the standard core unmodified — no changes to SAP objects, no clones of SAP programs.
- Consume only released public APIs and extension points so upgrades stay non-breaking.
- Use key-user extensibility for fields and logic that business users own.
- Move heavy custom logic side-by-side to SAP BTP where it scales and releases independently.
- Adopt ABAP Cloud for on-stack development so the compiler enforces the boundaries for you.
- Retire dead custom code before conversion — usage analytics usually removes a large share of the backlog.
Choosing a migration path
System conversion (brownfield)
Convert the existing ECC system in place. Keeps history and configuration; the effort sits in custom code remediation, Business Partner and Finance data migration and simplification-item resolution.
New implementation (greenfield)
Build a fresh S/4HANA system on standard processes and migrate master and open items. Cleanest core, highest change-management effort.
Selective data transition
A hybrid — new system, but selected company codes, history or configuration are carried across. Common for large landscapes consolidating multiple ECC instances.
Frequently asked questions
What is the main difference between ECC and S/4HANA?
ECC runs on any traditional database and relies on aggregate and index tables, while S/4HANA runs only on SAP HANA with a simplified in-memory data model (ACDOCA, MATDOC, Business Partner), a Fiori user experience and a code-to-data programming model based on CDS, AMDP and RAP.
Does custom ABAP code still work after conversion to S/4HANA?
Most syntax still compiles, but code that reads removed tables such as BSIS or MARD totals, assumes an 18-character material number, or uses obsolete customer and vendor master logic must be remediated. SAP's ATC simplification-item checks and custom-code analytics identify the affected objects before conversion.
What does clean core mean in S/4HANA?
Clean core means keeping the standard SAP core unmodified: no core modifications, only released public APIs and extension points, key-user extensibility for business-owned logic, and side-by-side extensions on SAP BTP for heavy custom functionality. It keeps upgrades predictable and low cost.
When does support for SAP ECC end?
Mainstream maintenance for SAP ERP 6.0 (ECC) runs to the end of 2027, with optional extended maintenance to 2030. SAP S/4HANA has committed maintenance through 2040.
Planning an ECC to S/4HANA move?
I have spent 13+ years on ABAP, ABAP on HANA and S/4HANA delivery for global enterprises — custom code remediation, CDS and RAP redesign, and clean core extension strategy.
Get in touch