Lesson 1 of 5
What changed in SAP S/4HANA: simplification items
11 min
Listen to this lesson
SAP S/4HANA is not SAP ERP with a new database. Data models were simplified, some functions were replaced, and some were dropped. SAP documents each such change as a simplification item. An SAP blog on the Simplification Item Check defines it as a description of a major, potentially incompatible change between SAP ERP and SAP S/4HANA, or between SAP S/4HANA releases, that might require preparation or follow-on activities in a conversion or upgrade. SAP Learning adds a useful warning: "simplification" here means "has changed", not "made easier".
Kinds of change
| Kind of change | What it means | Example |
|---|---|---|
| Changed data model | Data stored differently; conversion moves it | Simplified data model in inventory management (MM-IM) |
| Changed functionality | Same business need, different behavior or UI | Business partner as the single entry point for customers and suppliers |
| Functionality unavailable, equivalent exists | Old function gone; a successor covers the need | Storage location MRP replaced by MRP areas |
| Not strategic, no equivalent yet | Function remains but is not the future direction | Some functions placed in the compatibility scope with limited usage rights |
Typical kinds of simplification items. Readiness Check groups custom code findings by similar categories.
The Conversion Guide for SAP S/4HANA 2025 lists important application-specific preparations by area, each pointing to its notes: the business partner approach, finance conversion tasks, SAP Credit Management, foreign trade replaced by SAP Global Trade Services, simplified data models in sales and distribution, SD pricing data model changes, and the simplified data model in inventory management. Each of those is a group of simplification items with work attached.
Who should care? Everyone, at different depths. Solution architects use the items to shape scope and the transition approach. Basis prepares the system and runs the checks. Developers adapt code that reads changed data structures. Process owners decide how the business absorbs changed functions. Test leads turn every item with business impact into tests. A conversion where only Basis reads the items usually goes live technically and then surprises its users.
What a simplification item is not
- Not a list of innovations. New features are in SAP's What's New documentation; simplification items are about what changes for existing users.
- Not a custom code check. The Simplification Item Check does not check custom code; the ABAP test cockpit and the Custom Code Migration app do that, against the simplification database.
- Not only for conversions. Release upgrades within SAP S/4HANA also have simplification items, and the check runs for them too.
- Not all relevant to you. The full set spans every industry and line of business; only some apply to a given system.
Data model changes you will meet first
The data model items are the ones developers and testers meet every day, because they change where data lives. The conversion moves the data for you, but every custom report, interface and test query that reads the old tables is affected. Four examples matter at almost every ECC customer, including Contoso:
| Area | In SAP ERP (ECC) | In SAP S/4HANA | What it means for Contoso |
|---|---|---|---|
| Inventory management | Material document header and items in MKPF and MSEG; stock totals in tables such as MARD | One material document table, MATDOC; stock quantities are calculated from it, and the old tables are still readable through compatibility views | Custom stock reports keep working but must be retested for results and runtime |
| Sales and distribution | Document status in VBUK and VBUP | Status fields moved into the document tables (VBAK, VBAP, LIKP, LIPS, VBRK, VBRP) | Custom fields appended to VBUK or VBUP must be moved before conversion |
| Pricing | Condition records of documents in KONV | PRCD_ELEMENTS | Custom pricing reports must read the new table |
| Finance | Totals and index tables such as GLT0, BSIS, BSAS | Universal Journal, table ACDOCA; old tables replaced by compatibility views | Balances must reconcile before and after; finance reports are retested |
Common data model simplification items. The conversion converts the data; your code and tests must follow.
Contoso's first Readiness Check found 118 relevant items for EP1 (illustrative course data), from the business partner approach to storage location MRP. Most needed reading and a decision; a few, such as business partner synchronization and financial data consistency, needed months of work. That spread is normal and is why items must be triaged rather than counted.
What would you do?
A developer asks why the Simplification Item Check found nothing wrong with Contoso's custom pricing report, which reads old SD tables. What is the correct explanation?
- A simplification item documents a potentially incompatible change between releases.
- "Simplification" means "has changed", not "made easier".
- Items cover data models, functions, processes, UI and the compatibility scope.
- They are not innovations and not custom code checks; only some apply to your system.
- Data model items (MATDOC, SD status fields, PRCD_ELEMENTS, ACDOCA) hit every custom report and test query.
Check your understanding · not graded
Lesson check
1. What does a simplification item describe?
2. Which tool analyzes custom code against SAP S/4HANA simplifications?
3. Do simplification items exist for upgrades within SAP S/4HANA?
4. Which kind of item covers storage location MRP?
5. Which table holds material documents in SAP S/4HANA, replacing MKPF and MSEG?