S/4HANA Fundamentals Explained: What Really Changes vs. Classic SAP

From SAP ERP to S/4HANA: why a new system at all?

Classic SAP ERP (ECC) dates back to the 1990s and was extended over decades. The result: a grown system with thousands of tables, aggregates and indexes, where the same information is often stored multiple times. Reporting there frequently means: extract data, aggregate overnight, analyze the next day.

S/4HANA, by contrast, was built from scratch for the in-memory database SAP HANA. Instead of reading data from disks, the system computes directly in memory — fast enough to calculate totals and reports in real time from the documents. Aggregate tables become obsolete and the data model gets leaner.

For companies, the switch is no longer a voluntary modernization: SAP is ending maintenance for classic ECC. That's why job postings today almost exclusively ask for S/4HANA skills — and universities are adapting their courses accordingly.

The core: a leaner data model

The most important technical consequence of in-memory: aggregates and indexes disappear. Where ECC maintained separate tables for totals in financial accounting, S/4HANA calculates amounts live from the line items when needed.

The best-known example is the Universal Journal (table ACDOCA): FI, CO, Material Ledger and asset accounting all write into a single line item. The old separation between financial accounting and controlling — a constant topic in ECC — largely disappears. Cost elements are now G/L accounts, and every document carries FI and CO information at the same time.

Understand that, and you understand half of S/4HANA's logic: fewer tables, no redundancy, real-time reporting directly on the document. Exam questions like “Where is the CO assignment stored in S/4HANA?” are answered confidently with ACDOCA.

Business Partner instead of customer and vendor

One of the most visible changes in master data: customer and vendor master records are now maintained via the central Business Partner (transaction BP). The Business Partner bundles all roles — customer, vendor, contact person — in one object.

The classic transactions XD01 or XK01 now only redirect. In exams this is often asked as a comprehension question: why does the Business Partner exist? The answer: redundancy-free master data and a unified view of business partners across all modules.

Fiori instead of SAP GUI

The classic SAP GUI with its transaction codes is complemented by the Fiori Launchpad: tiles instead of menu trees, roles instead of transaction lists, end-to-end search — much closer to modern web apps. Many standard processes now run as Fiori apps, such as “Create Purchase Order” or “Display Supplier Invoices”.

For exams and practice this means: you need both. The process logic stays the same, but the path through the system looks different — and many universities now work exclusively with Fiori.

Practical tip: if you know the GUI transactions, you'll find the matching Fiori apps quickly via search. Conversely, it helps to note which document sits behind each app — that connects the interface with process understanding.

What changes in everyday work

For daily work, S/4HANA mainly means three things: faster processes (no waiting for background jobs), better reporting directly in the system (embedded analytics instead of Excel exports) and new process variants like automatic document recognition or predictive features.

At the same time, much stays familiar: document flows, organizational structures and the basic logic of order-to-cash and procure-to-pay are the same as in ECC. If you understood the processes in the old system, you'll find your way quickly — but you need to learn the new interfaces and data models.

What you should actually learn

A sensible order: first navigation and organizational structures (client, company code, plant, sales organization), then the Business Partner, then the Universal Journal and finally one complete process such as order-to-cash or procure-to-pay in the live system.

In the amigoSAP module “S/4HANA Fundamentals” we go through exactly these points live in the system — including the differences to ECC that come up in exams again and again. That way you learn not just where to click, but why the system works the way it does.