SAP S/4HANA MM: Procurement Changes You Must Know

What actually changed in SAP MM with S/4HANA — Business Partner for suppliers, the MATDOC inventory model, retired transactions, mandatory Material Ledger, MRP Live, flexible workflow, new output management and Fiori procurement apps — and what stayed the same.

  SAP Training   Oct 22, 2026   123  Add to Reading List
Quick Answer: In S/4HANA MM, suppliers are maintained as Business Partners, material documents live in one table (MATDOC) with stock calculated on the fly, many classic MB and ME transactions are retired in favour of MIGO, ME21N and Fiori apps, Material Ledger is mandatory, MRP runs as MRP Live with MRP areas, and approvals and PO output have new options. The procure-to-pay process itself — requisition, order, goods receipt, invoice — is unchanged.

SAP MM consultants moving to S/4HANA usually find the same thing: the business process is familiar, but the system around it has shifted in dozens of small and a few large ways. Interviewers know this, and "what changed in MM with S/4HANA?" has become one of the most common questions for MM roles in India. Candidates who learned from older ECC material tend to describe transactions that no longer exist.

This guide covers the changes that matter in practice — what they are, why SAP made them, and what they mean for a consultant's daily work — followed by a summary table and the parts that did not change.

1. Suppliers Are Business Partners

The most visible change for anyone touching master data. In ECC, vendors were created through XK01, MK01 or FK01, depending on whether you were maintaining purchasing data, accounting data or both. In S/4HANA, those transactions redirect to the Business Partner transaction BP, and a supplier is a business partner with supplier roles — typically one for financial accounting data and one for purchasing data.

Underneath, the classic vendor tables still exist and are kept in sync through customer–vendor integration, which is why reports and programs reading them continue to work. But maintenance happens through BP. An organisation that both buys from you and sells to you can now be a single business partner with both customer and supplier roles, instead of two unrelated records.

For migrations, this is one of the heaviest workstreams: every vendor must be converted to a business partner before the technical conversion, and duplicate or inconsistent vendor data surfaces quickly. MM consultants are often asked to lead or support the cleanup.

2. One Table for Material Documents: MATDOC

In ECC, a goods movement wrote a header to MKPF and line items to MSEG, and then updated a set of aggregate tables that held current stock — MARD for storage location stock, MCHB for batch stock and several others, plus history tables for previous periods. Every posting had to keep all of these in step.

S/4HANA writes material documents to a single table, MATDOC. Stock quantities are no longer stored as running totals; they are calculated from MATDOC when needed, which HANA can do quickly. MKPF, MSEG and the stock fields of the aggregate tables remain available as compatibility views, so most custom reports keep running.

Two practical consequences follow. Goods movements create fewer database updates and less locking, which improves throughput when many postings hit the same material at once. And custom code that writes directly to the old stock tables — rare but not unknown — must be rewritten, which is why it appears in every custom code check.

3. Retired Transactions

A long list of classic goods movement transactions — MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31 and others — is no longer available. MIGO is the single transaction for goods receipts, goods issues, transfer postings and other movements, alongside Fiori apps for specific tasks such as posting a goods receipt against a purchase order.

In purchasing, the older non-Enjoy transactions such as ME21, ME22, ME23, ME51, ME52 and ME53 were retired in favour of their Enjoy versions: ME21N, ME22N, ME23N, ME51N and so on. Most consultants were already using these, but test scripts, user training and custom transactions that called the old versions all need updating on migration projects.

Reporting transactions such as MMBE, MB52 and ME2N still work, and many now have Fiori equivalents with drill-down and filtering that users tend to prefer once they have tried them.

4. Material Ledger Is Mandatory

In ECC, Material Ledger was optional and many companies never activated it. In S/4HANA it is mandatory for inventory valuation, so every material is valued through it, in up to three currencies or valuations. Actual costing — recalculating actual material prices at period-end and revaluing inventory and consumption — remains optional and is activated separately.

For an MM consultant this matters because price control, valuation and period-end closing now interact with Material Ledger as standard. It is also an integration point with finance, and the conversation is easier if you understand the FICO side; our SAP FICO course covers it from the finance perspective.

5. MRP Live and MRP Areas

Material requirements planning in S/4HANA runs as MRP Live, transaction MD01N, which performs the planning calculation inside the HANA database rather than in the application server. Planning runs that took hours can complete in minutes, which allows companies to run MRP more often and react faster to demand changes.

Storage-location MRP — planning a storage location separately or excluding it from planning — was replaced by MRP areas, which offer the same capability with more flexibility. Projects migrating from ECC need to convert any storage-location MRP settings. For monitoring, Fiori apps such as Monitor Material Coverage and Manage Material Coverage give planners exception-based views instead of long lists.

6. Approvals: Flexible Workflow

The classic release strategy, built on classification characteristics, is still supported for purchase requisitions and purchase orders. Alongside it, S/4HANA offers flexible workflow, configured through Fiori apps, which lets business users define approval conditions and steps — by amount, material group or plant, say — without characteristics and classes. Approvers act from their Fiori inbox, including on mobile.

Interviewers increasingly ask which you would choose. A reasonable answer: release strategy for migrated systems where it already works and the team knows it; flexible workflow for new implementations or where business users need to change approval rules themselves.

7. Output Management for Purchase Orders

In ECC, purchase order printing, email and EDI output were controlled by condition technique, configured through NACE. S/4HANA introduces a new output management framework based on BRF+ rules, with form templates and email handled more simply. For purchase orders, the classic approach can still be used, and many migrated systems keep it initially, but the new framework is the recommended direction for new implementations.

8. Fiori Apps and Embedded Analytics

Daily procurement work increasingly happens in Fiori apps: Manage Purchase Requisitions, Manage Purchase Orders, Create Purchase Order – Advanced, Post Goods Receipt for Purchase Order, Create Supplier Invoice and Manage Supplier Invoices. Analytical apps show overdue purchase orders, spend by supplier and delivery performance directly on live data, without a separate data warehouse.

Finance-facing procurement tasks benefit too. The GR/IR reconciliation app helps clear long-standing open items on the goods receipt / invoice receipt account, a task that used to consume days of manual effort at month-end. The classic SAP GUI transactions remain available on-premise, so most teams run a mix.

Summary: ECC versus S/4HANA in MM

AreaECCS/4HANA
Supplier masterVendor master via XK01 / MK01 / FK01Business Partner (BP) with supplier roles
Material numberUp to 18 charactersUp to 40 characters
Material documentsHeader MKPF and items MSEGSingle table MATDOC; MKPF/MSEG as compatibility views
Stock quantitiesStored in aggregate tables (MARD, MCHB …)Calculated on the fly from MATDOC
Goods movementsMB01, MB1A, MB1B, MB1C, MB31 and MIGOMIGO (plus Fiori apps); old MB transactions retired
Purchasing transactionsME21 / ME51 family alongside ME21NME21N, ME51N and Fiori apps only
Material LedgerOptionalMandatory for valuation; actual costing optional
MRPClassic MRP (MD01), storage-location MRPMRP Live (MD01N) on HANA; MRP areas
ApprovalsRelease strategyRelease strategy or Fiori flexible workflow
PO outputCondition-technique output (NACE)BRF+-based output management (recommended)

What These Changes Mean on a Migration Project

On a brownfield conversion from ECC, an MM consultant's work concentrates in a few predictable places. Supplier conversion comes first: vendors must be mapped to business partner groupings, number ranges aligned, and inconsistent records — missing addresses, duplicate tax numbers, blocked vendors still in use — cleaned before conversion can run. This is usually the longest MM workstream.

Next is the simplification item check, which lists every S/4HANA change relevant to the system. The consultant reviews each MM item, decides what action it needs and works with developers on custom code that uses retired transactions, writes to old stock tables or assumes 18-character material numbers in interfaces and forms.

Then come configuration adjustments — converting storage-location MRP to MRP areas, reviewing valuation settings now that Material Ledger is active, and deciding whether to keep condition-technique output or move to the new framework — followed by regression testing of every procurement scenario and user training on changed transactions and new Fiori apps. Knowing this sequence lets you answer migration questions with confidence even before you have worked on one.

What Did Not Change

The procure-to-pay process is the same: purchase requisition, source determination, purchase order, goods receipt, invoice verification in MIRO and payment. The organisational structure — purchasing organisation, purchasing group, plant, storage location — works as before. Movement types such as 101 for goods receipt, 201 and 261 for goods issue, 311 for transfer posting and 122 for return delivery behave the same way. Automatic account determination through OBYC, with valuation class and transaction keys such as BSX, WRX and GBB, is unchanged. Info records, source lists, quota arrangements, physical inventory, batch and serial number management all work as they did.

This is why experienced ECC MM consultants transition successfully, and why a fresher should still learn the process and configuration thoroughly rather than treating S/4HANA as a new subject. What changed is the data model, master data and user experience around a familiar process.

How to Answer This in an Interview

Avoid reciting a list. Group your answer into four layers — master data (Business Partner, 40-character material number), inventory data model (MATDOC and calculated stock), transactions and user experience (retired MB transactions, Fiori apps), and planning and valuation (MRP Live, mandatory Material Ledger). Give one concrete detail from each, then close with what did not change.

Expect a follow-up. Common ones: "How is stock calculated if MARD no longer stores quantities?", "What happens to XK01 in S/4HANA?", "Would you use release strategy or flexible workflow?" and "What MM work happens on a brownfield migration?" If you have practised in an S/4HANA system, answer from what you saw; if you have not worked on a migration, say so plainly and describe what you studied.

Our SAP MM course is taught on S/4HANA, covering procurement, inventory, valuation and integration as they work today, with interview preparation built around exactly these questions.

People Also Ask / FAQ

Do MKPF and MSEG still exist in S/4HANA?

As compatibility views, yes. Data is stored in MATDOC, but reading MKPF and MSEG still works, so most custom reports continue to run.

Can I still use XK01 to create a vendor?

No. It redirects to transaction BP, where the supplier is created as a business partner with the appropriate roles.

Is MIGO the only goods movement transaction?

In SAP GUI, yes, for most movements. Fiori apps provide alternatives for specific tasks, such as posting goods receipts against purchase orders.

Is release strategy removed in S/4HANA?

No. It is still supported. Flexible workflow is an additional option that is often chosen for new implementations.

Should a fresher learn ECC MM first?

No. Learn MM on S/4HANA and understand the main differences from ECC, since many clients are migrating from it.

Learn SAP MM on S/4HANA

Live classes on S/4HANA systems, online and in select cities across India Explore the SAP MM Course