SAP S/4HANA Key Simplifications Reference
S/4HANA is not a version upgrade, it is a data model and functional change. This reference lists the simplifications that most often drive effort in an ECC conversion, with the action each one usually forces.
| Area | In ECC | In S/4HANA | Typical project action |
|---|---|---|---|
Master data | Separate customer (KNA1) and vendor (LFA1) masters | Business Partner (BP) is the leading object; CVI keeps customer and vendor records in sync | Run CVI synchronization and clean duplicates before conversion |
Master data | Material number 18 characters (MATNR) | Material number field length extended to 40 characters | Check interfaces, IDocs, custom fields and files that assume 18 characters |
Inventory | Material documents in MKPF and MSEG | MATDOC is the single material document table; MKPF and MSEG remain as compatibility views | Review custom code that writes to or joins the old tables |
Finance | Line items split across BSEG, COEP, FAGLFLEXA, ANEP and others | Universal Journal (ACDOCA) holds one set of line items for FI, CO, asset and Material Ledger | Plan reconciliation and report redesign; aggregates become views |
Finance | Classic General Ledger or New G/L | New G/L logic is embedded in the Universal Journal; classic G/L is not supported | Migrate to New G/L first if you are still on classic |
Finance | Classic Asset Accounting | New Asset Accounting is mandatory | Convert asset accounting and review depreciation areas |
Finance | Cost elements as separate CO master data | Cost elements are G/L accounts with an account type | Align chart of accounts and cost element settings |
Finance | Material Ledger optional | Material Ledger is always active; actual costing remains optional | Activate and convert Material Ledger during the project |
Finance | Classic credit management (FD32) | SAP Credit Management (FSCM) with UKM_BP | Migrate credit segments and scores |
Finance | Classic cash management | SAP Cash Management based on bank accounts and the Universal Journal | Redesign cash position reporting and liquidity forecast |
Sales | Pricing conditions in KONV | Pricing conditions in PRCD_ELEMENTS | Fix custom code selecting from KONV |
Sales | Classic rebate processing (VBO1) | Settlement Management with condition contracts | Migrate open rebate agreements |
Sales | Output control with NAST | Output management based on BRFplus is the strategic approach; NAST still works for compatibility | Plan form and output migration, test print and email |
Production | Classic MRP (MD01) | MRP Live (MD01N) runs in the database | Test planning results and custom MRP user exits |
Warehouse | Classic Warehouse Management (WM) | Classic WM remains usable; embedded EWM is the strategic option | Decide whether to keep WM or move to embedded EWM |
Procurement | SAP SRM | SRM is not part of S/4HANA; functions move to S/4HANA procurement or SAP Ariba | Map SRM scenarios to a target solution |
Planning | SAP APO | APO is replaced by embedded PP/DS or SAP Integrated Business Planning | Decide planning landscape before the conversion plan |
Foreign trade | SD Foreign Trade | Replaced by SAP Global Trade Services | Scope GTS if you export or import under licenses |
Real estate | Classic Real Estate (RE) | Flexible Real Estate Management (RE-FX) | Migrate classic RE contracts to RE-FX before conversion |
Technology | Any supported database, non-Unicode possible | SAP HANA database and Unicode only | Complete Unicode conversion first if needed |
Technology | SAP GUI dynpro as main UI | SAP Fiori launchpad is the default user experience; SAP GUI still works | Define roles and Fiori app scope |
General guidance only. The authoritative list is the Simplification Item Catalog and the SAP Readiness Check for your own source release and target release.
Get a second opinion on your simplification scope
Send your Readiness Check output and we will give you a short written review of what looks under or over scoped.
Optional. The tool and every export work without this. No spam.
How to use this list
Search by area or object name and read across the row: what you have in ECC, what exists in S/4HANA, and what the project normally has to do. Use it in workshops to decide which items are in scope before you run the SAP Readiness Check, then confirm each item against your own system results. Export to Excel and add columns for owner, status and effort so it becomes the working register for the program.
- Filter by area to assign each row to a functional lead
- Mark rows that your landscape does not use and record why
- Add the matching Simplification Item number from the catalog
Where the real effort sits
Most conversions are dominated by three themes: Business Partner and CVI for master data, the Universal Journal for finance, and custom code that reads or writes tables whose structure changed, such as MKPF, MSEG, KONV and the finance line item tables. Functional replacements such as credit management, rebates and SRM add scope when you actually use them. A site that does not use rebates has no rebate migration, so usage data matters more than the headline list.
What this list does not replace
The official Simplification Item Catalog contains hundreds of items and changes with each release. This page is a summary for planning conversations. Always run the Simplification Item Check and the Readiness Check against the exact source and target releases, and record the check results as evidence. Items also differ between system conversion, selective data transition and new implementation approaches.
Frequently Asked Questions
Is this the official SAP simplification list?
No. It is a planning summary of well-known changes. The official source is the Simplification Item Catalog and the check reports run against your own system, which are release specific and far more detailed.
Do all of these items apply to every conversion?
No. Applicability depends on the modules you use. If you never used SRM, APO or classic rebates, those rows do not create work. Always confirm with usage data and the SAP check reports.
Which item usually causes the most delay?
Business Partner and CVI data quality, and custom code touching changed tables, tend to cause the longest delays because they require data cleansing and developer time before technical conversion can start.
Does the list differ for greenfield projects?
In a new implementation you do not convert old structures, but you still must migrate master and open item data into the new model, so Business Partner, Universal Journal and Material Ledger decisions still apply.
If you want help turning the check results and custom code findings into a prioritized remediation backlog, Netray can review the output with you.
Related Tools
SAP ECC Obsolete Transactions and S/4HANA Replacements
A lookup table of common ECC transaction codes and the transaction or app that replaces them in S/4HANA, for training and role design.
SAPSAP S/4HANA Conversion and Migration Tools Reference
A lookup of the SAP tools used at each phase of an S/4HANA conversion or migration, what each does and when to use it.
SAPSAP CVI Business Partner Gap Report ABAP Generator
Generates an ABAP report that finds customers and vendors without a Business Partner link, the first check before a CVI conversion.
SAPSAP S/4HANA Pre-Conversion Technical Checklist
A checklist of the technical preparation items to close before running SUM on a system conversion from ECC to S/4HANA.