SAP MM and Procurement explained

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal, SAP Learning and sap.com, October 2026

SAP procurement is the part of SAP software a company uses to buy goods and services: a purchase requisition states the need, a purchase order goes to the supplier, the goods are received and the supplier's invoice is checked against both. The procurement module in SAP ERP is SAP MM, which stands for Materials Management, and in S/4HANA the same functions are named Sourcing and Procurement. Under either name the area runs procure to pay, together with the stock and valuation those movements create. The work is configuring that chain so that one purchase lands in the warehouse and the ledger at once.

In a current S/4HANA system the menu says Sourcing and Procurement, and on premise or in private cloud a buyer can still type ME51N and ME21N or open the Fiori apps that replace them. Cloud sourcing and supplier collaboration sit outside the ERP in the SAP Ariba applications, and the old Ariba Network became one part of SAP Business Network when SAP merged its separate business networks under that name in 2021. For the ERP side, start from the S/4HANA product page of SAP's Help Portal.

What is SAP MM (Sourcing and Procurement)?

SAP MM is Materials Management, the module that runs purchasing, inventory management and invoice verification, and Sourcing and Procurement is its name in S/4HANA. Its chain is short to describe and long to configure: a requisition states a need, a source of supply is found, a purchase order goes to the supplier, goods arrive against it, an invoice arrives against both, and the payment is somebody else's problem. Sources come from an info record carrying the last price and its conditions, from a contract or scheduling agreement, or from a source list with a quota arrangement splitting volume between suppliers.

Two fields on the order line do most of the work. The item category says what kind of procurement this is — standard, consignment, subcontracting, third party, stock transfer, a limit item with no quantity, a service item with an entry sheet — and by doing so decides whether a goods receipt is valuated, whether stock exists at all, and which follow-on documents are possible. The account assignment category says who pays: stock, cost centres and internal orders in CO, a project, an asset. Get those two right and the rest of the line usually behaves.

What is the difference between procurement, purchasing and sourcing?

Procurement is the whole process, purchasing is its transactional part and sourcing is its early stage. SAP's own definition of procurement is sourcing, purchasing, receiving and inspecting all the goods and services a business needs. Sourcing covers identifying the need, finding and evaluating suppliers and negotiating price and terms. Purchasing covers ordering, receiving and paying. In an SAP system the split is visible in the documents: requests for quotation, contracts and source lists belong to sourcing, while the purchase order, the goods receipt and the invoice belong to purchasing. SAP also separates direct procurement, which buys what goes into the product a company sells, from indirect procurement, which buys what the company uses itself, such as office supplies and services. In an SAP system that second split usually shows as the difference between a purchase planned as stock and one charged straight to a cost centre.

Which organisational units does SAP procurement use?

Six, and every purchasing document carries most of them. They are set up once in the enterprise structure, and the assignments between them decide who is allowed to buy for whom.

Who owns which view of the material master?

Different departments own different views, because the material master looks like one record and is really a stack of them: basic data and units of measure, purchasing, planning, accounting and costing, warehouse and storage, quality. A procurement consultant owns purchasing and shares accounting, but the planning views belong to manufacturing and the warehouse views to SAP supply chain and logistics.

That is why material creation is a governance problem before it is a configuration one: the record cannot be finished by any single team, and a view extended to the wrong plant is invisible until somebody tries to order. On the supplier side, S/4HANA made the business partner the single object behind what used to be separate vendor and customer masters, so a supplier who is also a customer is now one record with two roles — a migration topic on every conversion, and a master data governance topic ever after.

What do movement types and the GR/IR account do?

Movement types carry the posting logic of every stock movement, and the GR/IR account holds the value of a goods receipt until its invoice arrives. Inventory management speaks in movement types, and consultants really do talk in the numbers: 101 for the receipt against a purchase order and 102 for its reversal, 261 for the issue to a production order, 201 for the issue to a cost centre, 311 for a transfer between storage locations, 541 for the provision of components to a subcontractor. Each one carries the posting logic, the screen fields and the stock type it lands in — unrestricted, quality inspection or blocked.

Valuation is the other half. The material's price control decides whether a difference between order price and stock value lands on the stock account or on a price difference account: a standard price absorbs nothing, a moving average absorbs everything. The valuation class links the material to the accounts, and the receipt itself posts stock on one side and the goods receipt and invoice receipt clearing account on the other, where it sits until the invoice arrives. That account is the permanent shared border with Finance, and its ageing report is read at every close.

Why does the three-way match break so often?

Because it is comparing three documents written by three different people at three different times, and only one of them is inside your system. The order says what was agreed, the receipt says what turned up, the invoice says what the supplier thinks was owed, and invoice verification blocks whenever those disagree by more than a tolerance.

The tolerances are configured per company code and per key — price variance, quantity variance, an order price quantity difference — and each one has a lower and an upper limit that somebody has to defend to both the buyers and the auditors. Set them tight and the payables team spends its week releasing blocks; set them loose and the price variance nobody noticed becomes a year-end conversation. Add the recurring causes — a receipt posted late, delivery costs the supplier itemised differently, an invoice for an order flagged for goods receipt based invoice verification that has no receipt yet — and you have most of the ticket volume of an AMS procurement queue.

How do purchase order release strategies work?

Through classification rather than workflow: a class holds characteristics read from the document — value, purchasing group, plant, material group, document type — and a release strategy fires when a document's values match. Release codes are the individual approvers, and the release indicator at each step decides whether the document may already be printed or sent.

The failure mode is famous and worth naming in an interview: change a characteristic value after approval, most commonly by increasing the value, and the strategy is re-determined and the approvals are lost. Every project meets it, usually a week after go-live, usually reported as "the system deleted my approval". Designing the characteristics so that ordinary edits do not reset the chain is the real skill.

How are subcontracting, consignment and stock transfers handled?

Each is a special procurement type with its own item category and its own stock logic, and services follow a fourth pattern of their own.

Subcontracting

Components are transferred to stock provided to the supplier, and the receipt of the finished part consumes them in the same posting, so the stock report has a column most people forget exists.

Consignment

Stock stands in your warehouse and belongs to the supplier until withdrawal; settlement, not an invoice, creates the liability, and the price comes from a consignment info record.

Stock transport orders

Moving stock between plants is a purchase order in one plant and a delivery in the other; between company codes it also becomes an intercompany invoice, which is where Sales joins the design.

External services

A service line has no quantity in stock terms; the service entry sheet records what was delivered and its acceptance is the event the invoice matches against.

Which SAP products make up the procurement system?

SAP procurement is a set of products, not one system. Operational procurement, the day-to-day purchasing described above, runs inside the ERP. Around it sit cloud products that SAP's procurement training presents as the other solutions for the same process. The names below are the ones in use as of October 2026.

What is central procurement, and what runs where?

Central procurement, sold as SAP Ariba Central Procurement, puts one purchasing layer over several back-end systems, so a requisition raised once can be sourced centrally and executed locally. More broadly, the process has split across systems. Operational buying stays in the ERP, while sourcing events, supplier onboarding and catalogue buying run in Ariba and hand results back as contracts and orders. Clean-core discipline pushes custom approval logic and supplier portals beside the core on SAP BTP, the platform for extensions beside the core, rather than into it.

The practical effect on the job is that "where does this document live" is now a design question in its own right, and a procurement consultant is expected to draw the whole chain across systems, including the interfaces carrying orders and invoices, before configuring any part of it.

What about Ariba, Fieldglass and Concur?

They are SAP's separate cloud products around the ERP rather than parts of MM. SAP Ariba covers sourcing, contracts and the supplier network; SAP Fieldglass covers the external workforce — contractors and services bought under statements of work; SAP Concur covers travel and expense. Each hands orders, invoices or cost postings back to the ERP, so an MM consultant meets them mostly at the interface.

Ariba is also a career of its own. Ariba consultants are hired by SAP partners and by large buying organisations running sourcing events, contract management, guided buying and supplier onboarding, and the network side adds a separate specialism: enabling suppliers on SAP Business Network so purchase orders, confirmations and invoices travel electronically instead of by email. The work is configuration in a cloud tenant rather than in IMG, plus a great deal of supplier communication, and the projects that pay best are the integrated ones, where the consultant can explain which document originates in Ariba, which in the ERP, and how a change on one side reaches the other. An MM background is the usual entry, because every Ariba order still has to land as a purchase order, a goods receipt and an invoice in the ERP.

Who moves into procurement, and what gets checked?

Buyers and category managers convert most often, then purchasing key users (the key-user route), warehouse and finance consultants crossing over, and integration specialists who have handled supplier order and invoice messages. The checks are narrow: the movement types you used and what they post, a release strategy you kept from resetting, which account a goods receipt hits, and what you did with open purchase orders at cutover. The SAP MM interview questions guide runs those as scenarios.