SAP MM interview questions
An SAP MM interview tests whether you can design and defend how a company buys. The scenarios run along procure-to-pay: the purchasing documents and their flow, what a goods receipt posts and why, invoice verification and the three-way match, release strategies, stock and its types, and what happens to open purchasing at cutover. This guide takes them as scenarios, because that is how the interviews worth passing are run.
How is an MM interview different from a procurement quiz?
The circulating question lists ask what a movement type is. A real interview gives you a company — a manufacturer with two plants and a central purchasing department, say — and asks how you would set up its buying, then changes one fact and asks what you would change. The procurement area suits this because every decision in it has a downstream owner: a setting in purchasing lands as a posting in finance, a stock type decides what the warehouse may pick, a release strategy decides who is woken at night. The functional interview guide describes the general structure; what follows is the procurement content that fills it.
Which purchasing-document scenarios get tested?
"A requisition is raised in a plant, sourced centrally and delivered to a different plant. Walk me through the documents and the organisational objects they touch." This is the opening scenario because it exposes whether you know what the purchasing organisation, the purchasing group and the plant are each for, and how the requisition, the purchase order, the contract and the scheduling agreement relate. Follow-ups test the edges: when an item category changes what the document may contain, what an account assignment category does to the posting and to the goods receipt, why a company might buy through a central purchasing organisation for some materials and a local one for others, and what source determination should decide automatically. A good answer keeps the objects and the documents apart and explains which is expensive to change after go-live — the organisational structure, always.
How does account determination come up?
As a defect to diagnose. "A goods receipt for a stock material has posted to the wrong account. Where do you look, in what order?" The interviewer wants the chain: the material's valuation class, the movement type and the transaction key it drives, the account grouping that modifies it, the valuation grouping code above them all — and the goods-receipt/invoice-receipt clearing account that sits between receipt and invoice. Then the harder question: "The finance team wants the setting changed. What do you ask before you agree?" The answer that shows experience is the one that names who reads the account afterwards, because the finance interviewer down the corridor is asking the same scenario from the other side. An MM consultant who can say where a posting lands is trusted; one who says "that is finance" is not.
What do invoice verification and the three-way match look for?
"A supplier invoice is blocked. Why might it be, and who should release it?" The mechanism is the three-way match — order, receipt, invoice — with tolerances that decide how much price or quantity variance passes unblocked; the judgment is in where the tolerances sit and who owns a block. Good answers distinguish a price variance from a quantity variance from a missing receipt, know that a blocked invoice is still posted, and can say what changes when a company uses evaluated receipt settlement or consignment stock instead of invoices at all. The follow-up is nearly always about month-end: what happens to the clearing account when receipts and invoices never quite meet, and whose job it is to clear it.
How are release strategies and stock probed?
Release strategies test whether you can turn a policy into classification. "Purchase orders above a threshold need a second signature, and anything for capital equipment needs the plant manager's. Design it." The interviewer is listening for the characteristics you would choose, why a strategy must be unambiguous across all of them, and what you tell the business when their policy has a gap the system will not tolerate. Stock questions test the types and the movements behind them: unrestricted, quality inspection, blocked, and the transfers between them; what a stock transfer between plants does that a transfer within one does not; how a physical inventory count is posted and what a difference does to the books. "The warehouse says the system stock is wrong" is a favourite, because the honest answer starts with the movement history rather than with a correction.
What does the cutover scenario ask about open purchasing?
"We go live on a Monday. What happens to the purchase orders that are open on the Friday?" The answer has a structure: master data first — materials, business partners in their supplier role, source lists and info records — then the open documents, with a decision for each kind: recreate open orders in the new system, receive them there, and carry the received-not-invoiced quantities so that invoices arriving after go-live can be matched. Stock balances are loaded as goods movements against a migration account that must net to zero. Proof is reconciliation, stock by plant and value, open orders by count and value, signed by the purchasing lead; the migration stream loads it, but the MM consultant owns the answer to whether it is right.
What is an MM interviewer really testing?
Whether you see procurement as a chain with finance at the end and the warehouse in the middle, rather than as a set of screens. Whether you can talk to a buyer about approval and to an accountant about clearing in the same afternoon. Whether your knowledge of the standard is deep enough that you can tell a real gap from a habit when the business asks for a field the standard already has under another name. And whether your stories have the texture of real projects — the supplier who invoiced twice, the plant that counted stock on the wrong day — which is how experience is read everywhere in the ecosystem.
Which MM scenarios should you rebuild before the interview?
- One purchasing structure from memory — plants, purchasing organisations, groups — with the reason each object exists and what you would change now.
- The account-determination chain for a stock receipt, a consumable and a service, traced to the accounts, and the setting that controls each step.
- One blocked invoice and one stock difference, told as the diagnosis you actually did, in the order you did it.
- A release strategy you designed, with the gap in the policy you found while designing it.
- The sales side of the same flow, since order-to-cash and procure-to-pay meet in stock and in finance; the SD interview guide shows what the neighbour is asked, and the umbrella guide the pattern they share.
Related reading
- SAP MM and Procurement explained
Purchasing, inventory and invoice verification — how a company buys.
- SAP SD interview questions
Order types, the condition technique, document flow, blocks, billing and revenue — as scenarios.
- SAP FI interview questions
Organisational structure, ledgers, MM and SD integration, period-end and migration — as scenarios.
- SAP functional consultant interview questions
How functional interviews are structured, the question types with example phrasings, what is really being tested, preparation and red flags.
Work with SAP?
Join to get your public SAP profile. Your city appears on the map once 5 professionals are mapped there.