SAP MM interview questions

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

SAP MM interview questions test whether you can design and defend how a company buys: purchasing documents and their flow, what a goods receipt posts, invoice verification and the three-way match, release strategies, stock types, and open purchasing at cutover. They arrive as scenarios, so this guide takes them as scenarios.

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 sets out the question types every area shares; below are the ones a buyer, a warehouse manager and an accountant will each recognise as theirs.

Procurement panels listen for vocabulary rather than ask for it: a candidate who brings up movement types, account determination and the release strategy before being prompted has usually configured them. The table lists what to name for each scenario.

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. Name the master data in the order the system reads it: the quota arrangement (MEQ1), the source list (ME01), then outline agreements and the info record (ME11) that holds the price and planned delivery time for one material from one supplier. 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. Say that you would run the simulation in OMWB before touching OBYC, and that GBB carries modifiers such as VBR for consumption and BSA for initial stock. 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 specifics to have ready: tolerance keys are set in OMR6, PP for price and DQ for quantity among them, an automatic block sets payment block R, MRRL runs evaluated receipt settlement and MRKO settles consignment withdrawals. 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. The classic procedure uses class type 032 and characteristics that point at the communication structure CEKKO, such as GNETW for the total net value and BSART for the document type. 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 (MI01 creates the count document, MI04 enters the count, MI07 posts the difference with movement type 701 or 702). "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. Where the warehouse runs its own application, the question moves to EWM and the delivery seam, and the candidate is expected to know which document each side owns.

Standard price or moving average: what does the interviewer want?

The posting, not the definition. Price control is one field on the material's accounting view: S for standard price, V for moving average. With S, a goods receipt values the stock at the standard price and the gap to the order price goes to a price difference account through transaction key PRD. With V, the receipt is valued at the order price and the average moves. The invoice follows the same split: with V a price variance is added to the stock value as long as the stock is still there, and goes to price differences for the part that has already been issued. The usual design is V for purchased raw materials and S for what the company makes, and the follow-up asks what happens to the margin when a volatile material is left on S.

Which S/4HANA changes do MM interviewers ask about?

The ones that change what you type or where the data sits. A candidate who still says vendor master and MB1A is dating their experience. When a developer or a data person is on the panel, expect tables too: EKKO and EKPO for purchase order headers and items, EBAN for requisitions, EKBE for the order history, RBKP and RSEG for invoices.

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?" Take it in the order the load runs. Materials, business partners in their supplier role, source lists and info records have to be in place before any document can point at them, and only then do the open documents get a decision each: 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 you can recognise a requirement the standard already meets under a name the business does not use, and say so without making the buyer feel corrected. And whether the projects you describe left marks — the supplier who invoiced twice, the plant that counted stock on the wrong day, the release strategy that stopped a shutdown order at midnight — because a story with a mess in it is the kind of evidence the ecosystem reads.

Which procurement stories should you have ready?

• One purchasing structure from memory, 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.
• One blocked invoice and one stock difference, told in the order you diagnosed them.
• A release strategy you designed and the policy gap it exposed.
• The sales mirror: the SD interview guide asks the same chain from the selling side.