Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 5

A simpler data model

9 min

Because SAP HANA can total line items quickly, SAP rebuilt large parts of the ERP data model for S/4HANA. The aim was to store each business fact once. This lesson looks at the two simplifications you will meet most often, in finance and in inventory, and explains why they matter to people who test and sign off.

The old problem: the same fact in many places

In SAP ECC, a single supplier invoice could write to the accounting document tables, several index tables used to find open items quickly, totals tables for the general ledger, totals for the supplier account, and separate controlling tables for cost centers. Each table had a reason to exist. Together they meant one posting created many records, and reconciliation reports existed to prove they still agreed.

Finance: the Universal Journal

In S/4HANA, financial postings land in one line-item table known as the Universal Journal (technically, table ACDOCA). General ledger, controlling, asset accounting and material ledger information is recorded on the same line. A single journal entry line can carry the G/L account, the amount in several currencies, the cost center or profit center, the segment, the material and the customer.

Before (ECC)Accounting document, G/L totals (for example GLT0 or FAGLFLEXT), customer and vendor totals (KNC1, LFC1), open-item index tables, and separate controlling line items and totals.
After (S/4HANA)One Universal Journal line per posting line, carrying finance and controlling attributes together. The old totals and index tables are replaced by views calculated from the line items, so older reports still work.
Finance in S/4HANA: one line-item store instead of many copies and totals.

Two examples of removed aggregates are worth remembering: the general ledger totals tables and the customer and supplier totals tables. In S/4HANA those totals are no longer stored; they are calculated from line items when needed. SAP calls the replacements compatibility views, which let older programs and reports keep reading data in the old shape.

For business users, the effect is that finance and controlling agree by design. In ECC, the general ledger and cost center accounting were reconciled at month-end. In S/4HANA they are the same records seen from two angles, so that reconciliation step largely disappears.

Inventory: one material document table

Inventory went through the same change. Every goods movement creates a material document. In ECC, material documents were split into header and item tables, and stock quantities were kept in several aggregate tables updated with each movement. In S/4HANA, material documents are stored in a single table (MATDOC) and stock quantities are calculated from it rather than kept as separate running totals.

AreaWhat was removed or mergedWhat a user notices
General ledgerSeparate totals tables per ledgerBalances are always derived from the journal entries, so drill-down always reaches the source
Customers and suppliersTotals and open-item index tablesOpen items and balances come straight from the journal entries
ControllingSeparate controlling line items for primary costsCost center reports and the G/L show the same postings
InventoryMaterial document header/item split and stock aggregatesStock reports reflect each movement immediately

Where the S/4HANA data model was simplified

Other simplifications you will meet

The data model changes are not limited to tables. Some are business objects you work with directly. The business partner is the single entry point for customers and suppliers. Credit management, the material ledger for inventory valuation, and asset accounting were also reworked. Each one appears on SAP’s simplification list, the document that tells migration projects what changed between ECC and each S/4HANA release.

Why this matters for sign-off

Fewer copies of the same fact means fewer places for numbers to disagree, and fewer reconciliation reports to check. It also means a mistake on a posting line is visible in every report that reads that line. If a goods receipt at Contoso’s Chicago plant posts without a profit center, the gap appears at once in profit center reports, segment reports and margin analysis. That is easier to detect, but only if a tester looks at those attributes.

What would you do?

Contoso has just moved from ECC to S/4HANA. A finance key user wants to run the same monthly reconciliation between the general ledger and the controlling totals that she ran for years. What should she do?

Key points
  • S/4HANA stores each business fact once and calculates totals from line items.
  • Finance and controlling postings share the Universal Journal (ACDOCA).
  • Removed aggregates include G/L totals and customer/supplier totals; compatibility views replace them.
  • Material documents live in one table (MATDOC); stock is derived from movements.
  • Testing shifts from reconciling copies to checking the attributes on each posting line.

Check your understanding · not graded

Lesson check

  1. 1. What is the Universal Journal?

  2. 2. What replaced the old totals tables in S/4HANA so older reports still work?

  3. 3. Where are material documents stored in S/4HANA?

  4. 4. Which document tells migration projects what changed between ECC and an S/4HANA release?