SAP S/4HANA Simplification Items & Data Model Changes

Key structural changes from ECC to S/4HANA - Universal Journal, Material Number length extension, and business-process-level simplifications.

A simplification item is a specific, catalogued difference between ECC and S/4HANA that a conversion project must deal with. There are hundreds, and SAP's readiness tooling tells you which apply to you.

Treating an S/4HANA conversion as 'just a technical upgrade' without reviewing simplification items is like renovating a house and assuming all your existing furniture will still fit, only to discover several load-bearing walls were actually removed and rebuilt in different places - some old furniture (custom code) simply won't fit anymore without adjustment.

Key Concepts

Three of them account for most of the work.

1. The Universal Journal. FI, CO, asset accounting and the material ledger merged into one line-item table:

    ECC        BKPF/BSEG + COEP + ANEP + ... plus totals tables
    S/4HANA    ACDOCA

Dozens of ECC tables are now compatibility views, so old code still reads. New development reads ACDOCA directly. The reconciliation work between FI and CO largely disappears, because they are the same rows.

ACDOCA

2. Material number length, 18 to 40 characters. This sounds trivial and is consistently the most painful item in practice.

Every custom program with DATA lv_matnr(18), every interface file with a fixed-width layout, every downstream system expecting 18 characters — all of them break, and they break at the edges of the system where nobody is looking.

DATA lv_matnr(18)

It is the clearest argument for referencing data elements instead of hard-coding lengths, which is exactly why the ABAP Dictionary works the way it does.

3. Business Partner is mandatory. Customers and vendors are no longer separate master records. The old transactions are retired:

    ECC        XD01 customer, XK01 vendor -- separate objects
    S/4HANA    BP with customer and vendor roles -- one object

A company that both buys from you and sells to you was two records that nobody linked. Now it is one, which is better and means converting existing data and every program that read the old tables.

Process-level items too. Older goods movement transactions are replaced by MIGO. The material ledger is mandatory rather than optional. Various aggregate tables are gone, since HANA computes totals on the fly.

MIGO

The tool that turns this into a plan. SAP Readiness Check analyses your system and reports which simplification items are relevant — filtered by what you actually use, because an item for a module you never implemented does not matter.

It also counts the affected custom code objects.

Why the question distinguishes people. Treating a conversion as a technical upgrade is the mistake the question is probing for. The database migration is the predictable part. The simplification list is the unpredictable part, and running Readiness Check before committing to a date is what keeps it from becoming a mid-project discovery.

What the interviewer is probing.1. "What is a simplification item?" Probing: the vocabulary. Stalls: "A change." Moves up: a documented difference from ECC — a removed transaction, a merged table, a mandatory conversion — each with an action you must take.

2. "How do you find out what applies to you?" Probing: the method. Stalls: "Read the notes." Moves up: the simplification item check run against your system, plus the readiness check — it lists the relevant ones with blocking issues.

3. "What is the business partner conversion?" Probing: the biggest one. Stalls: "A rename." Moves up: customer and vendor masters become one business partner with roles, which affects interfaces, custom code and master data processes.

4. "What happened to the aggregate tables?" Probing: the model change. Stalls: "Nothing." Moves up: index and aggregate tables were removed and replaced by views over the line items, so custom code reading them must be adjusted.