Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 36 ยท S/4HANA and Careers

S/4HANA: What Changed and Why

Understand SAP S/4HANA: what it is, the Universal Journal, Business Partner, MATDOC and other simplifications, deployment options and migration paths.

SAP S/4HANA is SAP's current ERP suite. The "S" stands for Suite and the "4" for the fourth generation (after R/1, R/2 and R/3), while HANA is the in-memory database it is built on. Launched in 2015, it replaces SAP ECC (ERP Central Component, the R/3 successor). Understanding what changed is valuable because most SAP jobs today involve a migration to S/4HANA or work on a system already running it.

SAP cannot run here, so this lesson describes the product, and the runnable code is a labelled stand-in. Dates and product details change, so check SAP's current roadmap for decisions in a real project.

Why a new ERP?

Classic ERP stored aggregated data, because disk databases were slow: totals were pre-calculated and duplicated into many tables. With an in-memory column-store database (HANA) such aggregates can be computed on demand. S/4HANA used that freedom to simplify the data model and move logic into the database. The result: fewer tables, real-time reporting and a redesigned user interface (Fiori).

SAP has announced that mainstream maintenance for ECC ends in 2027, with an optional extended maintenance to 2030, which is the main reason companies are migrating. Always confirm the current dates with SAP.

Key simplifications

Area In ECC In S/4HANA
Finance Separate tables for G/L (BSEG, FAGLFLEXA), CO (COEP), assets and others One source of truth: the Universal Journal table ACDOCA
Customers/vendors Separate master records (KNA1, LFA1) Business Partner (BP) is the leading object; customers and vendors are roles
Materials Material document in MKPF+MSEG; aggregate tables MATDOC table; aggregates calculated on the fly
Material number 18 characters Up to 40 characters
MRP Batch runs MRP Live runs in HANA, much faster
Credit management FI-AR credit SAP Credit Management in FSCM
Database Any supported DB SAP HANA only
UI SAP GUI SAP Fiori (SAP GUI remains available)

The Universal Journal deserves a slide of its own. Instead of posting to many ledgers separately (financial accounting, controlling, asset accounting, material ledger), one line item in ACDOCA carries both financial and management-accounting dimensions, so FI and CO always reconcile.

flowchart LR
  subgraph ECC
    A1["FI: BSEG"] --- A2["CO: COEP"]
    A2 --- A3["Assets: ANEP"]
    A3 --- A4["Totals: GLT0"]
  end
  subgraph S4["S/4HANA"]
    B["ACDOCA<br/>Universal Journal"]
  end
  ECC -->|simplification| S4

Many tables and reconciliation jobs become one table with all dimensions on each line.

JS Stand-in: one journal, many views

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Business Partner

In ECC a company that is both customer and supplier needs two master records. In S/4HANA a single business partner has several roles (for example FLCU00 for FI customer and FLVN00 for FI vendor). The tcodes XD01 and XK01 redirect to BP. Customer/vendor integration (CVI) keeps the old tables in sync, and during migration existing masters are converted to partners.

JS Stand-in: one partner, several roles

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Deployment options

  • On premise: you run it in your data center or on a hyperscaler (AWS, Azure, Google Cloud) and control upgrades.
  • Private cloud edition (RISE with SAP): SAP-managed hosting with a customer-specific system.
  • Public cloud edition: multi-tenant software as a service with standardized processes and mandatory upgrades.

Migration paths

flowchart TD
  M["Migration choice"] --> G["Greenfield<br/>new install, redesign"]
  M --> B["Brownfield<br/>system conversion"]
  M --> L["Selective / bluefield<br/>transfer by scope"]

Choose by how much of the old system you want to keep.

  • Greenfield: install a clean S/4HANA and migrate selected data. Best when the old system is heavily customized and you want a fresh start.
  • Brownfield (system conversion): convert the existing ECC system in place with the Software Update Manager (SUM) and the Database Migration Option. It keeps history and custom code but needs thorough preparation.
  • Selective data transition (bluefield): copy only chosen company codes or scope to a new system.

Tools: the SAP Readiness Check and Simplification Item Catalog show what will change, ATC (ABAP Test Cockpit) with S/4HANA checks finds custom code that must be adapted, and the Migration Cockpit loads data.

Clean core

SAP now recommends a clean core: keep the ERP standard, move custom developments to extensions that use released APIs, ideally side-by-side on SAP BTP (Business Technology Platform) or as in-app extensions through the ABAP RESTful Application Programming Model (RAP). This keeps upgrades cheap. The ABAP side of this is part of Modularization and Classes in ABAP, and user interfaces and data models continue in S/4HANA Data Models: CDS, Fiori and HANA.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which table is the Universal Journal in S/4HANA?

    ACDOCA holds the line items for both financial and management accounting.
  2. 2. What replaces separate customer and vendor masters in S/4HANA?

    The business partner is the central object, with roles for customer and vendor.
  3. 3. Which migration path keeps the existing system and converts it?

    Brownfield is a system conversion of the existing ECC installation.
  4. 4. What does 'clean core' mean?

    Extensions use released APIs so upgrades remain easy.

Summary

  • S/4HANA is built on the HANA in-memory database and a simplified data model.
  • The Universal Journal (ACDOCA), Business Partner and MATDOC replace many tables.
  • Options: on premise, private cloud, public cloud.
  • Migration: greenfield, brownfield or selective, supported by readiness checks and ATC.
  • Clean core keeps customizations outside the standard.

Next: S/4HANA Data Models: CDS, Fiori and HANA