SAP S/4HANA

SAP S/4HANA is SAP's current-generation ERP suite and the successor to SAP ERP Central Component (ECC), itself the successor to R/3. Its defining architectural decision is that it runs only on SAP HANA, a columnar in-memory database. Because aggregates can be computed on read rather than maintained on write, S/4HANA removed many of the aggregate and index tables that earlier SAP releases carried, which simplifies the data model and allows transactional and analytical queries to run against the same tables instead of requiring a separate reporting warehouse for every question.

The clearest expression of that is the Universal Journal, a single line-item table that merges what were previously separate financial accounting and controlling structures. Financial postings, cost centre and profit centre detail, and margin analysis share one source of truth, which removes the periodic reconciliation between modules that finance teams previously had to perform. The user experience is SAP Fiori, a role-based HTML5 interface that replaced the older SAP GUI transaction screens for most day-to-day work.

Functionally the suite spans finance, sourcing and procurement, manufacturing and production planning, supply chain and inventory, sales and order management, service, asset management, and research and development or project control. Around the core, SAP positions a wider portfolio for specific domains — Ariba for sourcing networks, SuccessFactors for human capital, Concur for travel and expense, and the SAP Business Technology Platform for extension and integration work — so a large deployment is typically S/4HANA plus several connected products rather than one monolith.

It is offered in several deployment forms that differ in more than hosting. The on-premise and private cloud editions retain deep configurability and a broad functional scope; the public cloud edition follows a more standardised, regularly updated model with extension handled through released APIs and side-by-side development rather than core modification. SAP packages private-cloud migration commercially under RISE with SAP.

Moving to S/4HANA from ECC is a programme in its own right, and the industry recognises three broad routes: a greenfield reimplementation on a clean data model, a brownfield technical conversion of an existing system, and selective data transition that carries across chosen entities or company codes. The scale of that decision — alongside the size of the partner and consulting ecosystem around it — is usually the deciding factor for organisations weighing S/4HANA against a lighter mid-market ERP.

It targets large and complex enterprises: multinational groups with multiple legal entities, statutory reporting obligations across jurisdictions, and industry-specific processes. Smaller organisations in the SAP ecosystem are more commonly served by SAP Business One or SAP Business ByDesign.