SAP S/4HANA: Key Features, Architecture, and What Makes It Different

S/4HANA is not ECC on a faster database. That is the misconception we meet most often, so it goes first. The name is simple enough: “S” for Suite, “4” for fourth generation, “HANA” for the in-memory database underneath. The change behind it is bigger: SAP rebuilt how the ERP stores data, presents it and gets extended. Dates, options and a path finder for your own system are collected in our hub on SAP ECC end of maintenance 2027.

TL;DR: S/4HANA differs from ECC in five ways that matter in practice: an in-memory, column-based database without aggregate tables, a simplified data model with one universal journal for finance, Fiori instead of SAP GUI, analytics embedded in the transactional system, and a clean core model where extensions live outside the standard. In S/4HANA Public Cloud these principles are not optional, which is exactly what keeps upgrades painless.

What makes the in-memory architecture different?

Classic ERP systems, ECC included, kept data on disk and read it into memory when needed. Complex queries therefore relied on pre-calculated aggregate tables, index tables and materialised totals to stay fast. It worked, but it was always a workaround.

S/4HANA runs only on SAP HANA, an in-memory, column-based database. Three consequences:

No more aggregate tables. ECC maintained hundreds of totals and index tables to avoid slow reads. HANA calculates them on the fly from the line items. Less redundancy, and every report shows the current state rather than last night’s batch.

Column-store compression. Values in a column resemble each other, so they compress well. The database footprint shrinks and queries get faster.

Analytics on live transaction data. In ECC, heavy reporting ran in separate systems (SAP BW, BusinessObjects) because it would have slowed down operations. HANA handles transactions and analytics on the same data.

How is the data model simplified?

The most visible simplification is in finance. In ECC, financial data was spread over BSEG, BKPF and separate tables for open items, cleared items and totals (BSID, BSIK, BSAD, BSAK and more). S/4HANA brings them together in ACDOCA, the universal journal: one table for all financial and controlling postings. Anyone who has traced a financial report across seven ECC tables knows why this matters.

Similar consolidations run through the other areas:

• Materials management: stock and valuation data condensed into fewer tables with aggregation at runtime
• Sales and distribution: a leaner document flow with fewer intermediate tables
• Controlling: no separate CO posting tables; everything flows through the universal journal

The practical consequence: custom reports and interfaces that read ECC tables directly need to be checked and often adapted during a conversion. It is work, and it is also the moment to clear out years of technical debt. In a new implementation on S/4HANA Public Cloud, this question disappears, because old custom code does not come along.

What does SAP Fiori change for users?

Fiori replaces SAP GUI as the user interface, and it is more than a new look.

Role-based apps. Instead of long menu trees and transaction codes, users get the apps for their role on a Launchpad. A sales manager sees pipeline, forecast and activities, not the full SAP menu.

Runs on any device. Fiori apps work on desktop, tablet and phone. Warehouse staff post goods receipts on a tablet without a separate mobile app.

Analytics in the app. Overview pages show KPIs, charts and drill-downs directly. A finance manager sees open payables, cash trends and overdue invoices on one screen.

One design language. All apps follow the same guidelines. Whoever knows one app finds their way around the next, which shortens training.

Why does the clean core matter so much?

In ECC, companies modified the standard directly. That made every upgrade a project. S/4HANA separates the two: the standard stays untouched, and extensions use released interfaces, either inside the system with ABAP Cloud or side by side on SAP BTP. SAP describes this as a clean core, with a level model that rates extensions by how upgrade-safe they are (SAP News).

In S/4HANA Public Cloud the clean core is the only way to extend, which is why SAP can upgrade all customers on its schedule without breaking their systems. In the private edition it is a discipline you have to enforce yourself. We explain both routes in detail: extensions inside the system with ABAP Cloud and side-by-side apps on BTP.

What analytics and AI come built in?

Embedded analytics means every area of S/4HANA brings its own reports and dashboards. Finance sees cash positions, procurement sees spend by supplier, sales sees open orders and margins, without leaving the system or waiting for a data warehouse load.

On top of that, SAP builds AI into the application. Joule, SAP’s AI assistant, answers questions in natural language, summarises documents and guides users through tasks. Predictive functions sit in specific processes, such as payment behaviour in finance or demand in supply chain, and learn from your own data. SAP says Business AI was included in two thirds of its cloud order entry in the fourth quarter of 2025 (SAP News). Whether a given AI function pays off depends on your data quality, so treat it as part of the process design, not as an add-on.

How does S/4HANA connect to the customer side?

The value of S/4HANA grows when the ERP and the customer processes share one data foundation:

Prices and availability. Sales Cloud V2 can pull customer-specific prices and availability from S/4HANA while the quote is being built, so the sales rep quotes the right figure in the meeting.

Order to cash. Orders from Sales Cloud V2 or Commerce Cloud flow to S/4HANA for delivery, invoicing and revenue recognition. We show the full flow in quote to cash with Sales Cloud V2 and S/4HANA Public Cloud.

Service with context. Service Cloud V2 agents see order history, delivery status and invoices from S/4HANA next to the case. When a customer calls about a late delivery, the agent already knows.

This is where our work sits. Spadoom implements S/4HANA Public Cloud and the CX stack around it with one team, so the seam between ERP and CRM belongs to one project instead of two. This overview of partners for cloud ERP and CRM explains why that matters. If you run ECC today, remember the calendar: mainstream maintenance for SAP Business Suite 7 ends in 2027, optional extended maintenance in 2030 (SAP News). The S/4HANA readiness assessment shows in five days which route fits, and the transformation guide shows the target architecture.

FAQ

How long does an S/4HANA migration take?

It depends mostly on the route and on your custom code. A new implementation of S/4HANA Public Cloud for a mid-sized company with clear processes is typically a matter of months, not years. A system conversion of a heavily modified ECC takes longer, because every custom object has to be analysed and adapted. A readiness assessment gives you a realistic figure for your own landscape.

Is SAP GUI still available in S/4HANA?

In the private edition and on-premise, yes, for compatibility, and many companies run it alongside Fiori during the transition. S/4HANA Public Cloud is used through Fiori. SAP’s development goes into Fiori, and new functions often appear only there, so plan the move of your users rather than treating GUI as the long-term interface.

What happens to SAP BW when I move to S/4HANA?

S/4HANA’s embedded analytics cover much of the operational reporting that used to need BW. Cross-system and historical analytics still need a data platform. SAP now positions SAP Business Data Cloud for that role, and many companies reduce their BW footprint step by step rather than switching it off at go-live.

Do users need retraining?

Yes, but less than for a completely new system, because Fiori apps follow one design and are organised by role. Most users need a short introduction to the Launchpad and their own apps. Key users and administrators need more, covering configuration, extensibility and analytics.

Which database does S/4HANA need?

SAP HANA, without alternatives. In S/4HANA Public Cloud and in RISE with SAP this is part of the service and you do not size or operate hardware yourself. Only on-premise installations need certified HANA hardware or a hosting provider.