SAP MM and Procurement explained

SAP Procurement — classically the MM module (Materials Management), called Sourcing and Procurement in S/4HANA — is the part of SAP that runs how a company buys: requisitions, purchase orders, goods receipts and supplier invoices. Working in it means configuring that procure-to-pay chain and the material and supplier master data underneath it, so a purchase lands correctly in stock and in the books.

What the area covers

• Purchasing (MM-PUR) — requisitions, RFQs, purchase orders, outline agreements, sources of supply and the release strategies that approve them.
• Inventory management (MM-IM) — goods receipts, goods issues, transfer postings and physical inventory, spoken in movement types.
• Logistics invoice verification (MM-IV) — the three-way match of order, receipt and invoice, with tolerances, blocked invoices and GR/IR clearing.
• Valuation and account determination — valuation classes, price control, and which G/L account a goods movement hits.
• Special procurement — subcontracting, consignment, stock transport orders, third-party orders and external services.
• Sourcing and supplier collaboration — sourcing events, supplier onboarding and catalogue buying, often in SAP Ariba and integrated back to the core.

What does an SAP Procurement consultant actually do?

The artefacts are concrete: a process design out of fit-to-standard workshops, configuration in the IMG (purchasing organisations, document types, release strategies, account determination), functional specs for what standard cannot do — an order form, an approval workflow, a supplier interface — test scripts, and cutover instructions for open orders and opening stock.

Most meetings are border meetings. Buyers describe how they actually order; finance argues about which account a goods receipt posts to; the warehouse wants that receipt to continue into putaway.

A week changes shape by phase: workshops and sandbox demos in explore; configuration, unit tests and specs in realise; defect triage in test, usually a document that will not post; then cutover, with open orders migrated and stock loaded. In hypercare and AMS the same questions recur — a blocked invoice, a price difference, a missing goods receipt — and answering them fast is what earns trust.

How do people get into SAP Procurement?

The common route is domain: buyers, category managers and supply-chain staff who know why a contract exists, now configuring the system they used. Next is the key-user route — owning the purchasing process during a project, then staying with it. Adjacent areas convert: logistics people arrive via the goods receipt, finance people via the invoice. Developers who wrote MM enhancements and integration specialists who handle ORDERS and INVOIC IDocs become strong techno-functional profiles here.

What gets someone hired is evidence rather than vocabulary: explaining account determination and the three-way match in your own words, naming movement types you have used, describing a release strategy you designed, saying what you did at a cutover. Interviews probe exactly there.

What it pairs with

Finance (FI)

Every goods movement and invoice posts into FI; account determination and GR/IR clearing are shared territory, so MM+FI is a well-worn combination.

Supply Chain & Logistics

The goods receipt is where putaway begins; MM and warehousing describe one physical flow from two sides.

Manufacturing (PP)

The planning run turns demand into requisitions, and subcontracting is a joint process with production.

Master data (MDG)

A duplicated vendor is a procurement problem before it is a governance one.

Quality Management (QM)

Inspection at goods receipt and blocked stock hang off the purchasing process (QM explained).

Security and GRC

Who may create a supplier and who may approve its invoice is a segregation-of-duties question.

Where it is going

The process is splitting across layers: operational buying stays in the ERP core while sourcing, supplier onboarding and catalogue buying run in Ariba and hand results back, and central procurement puts one purchasing layer over several back ends. Clean-core discipline moves custom approval logic beside the core on BTP. So "what runs where" is now part of the design work, and the chain you are asked to explain crosses more than one system.