Free live session with Noel D’Costa: Saturday 24 October, 1:00 PM Eastern / 10:00 AM Pacific. Reserve your place
All interview questions
SAP MM · 18 QUESTIONS · THREE LEVELS

SAP MM interview questions and answers

The questions SAP MM interviewers ask at three levels, what each question is really testing, and how to answer from your own procurement and inventory projects. Covers ECC and S/4HANA.

Freshers and first roles

Expect questions on the procure-to-pay cycle and the organisational structure. Explain each step in business terms.

1. Explain the procure-to-pay cycle in SAP.

What it tests: Whether you can connect the steps and the documents.

Purchase requisition, source determination, request for quotation and quotation where used, purchase order, goods receipt in MIGO, invoice verification in MIRO, and payment in finance. Mention which document each step creates and that goods receipt and invoice receipt both post to the GR/IR account.

A strong answer adds who does each step in a real organisation and where approvals sit.

2. What is the organisational structure in MM?

What it tests: Basics that every configuration depends on.

Client, company code, plant, storage location, purchasing organisation and purchasing group. Explain how a purchasing organisation can be plant-specific, company-specific or cross-company, and why a business might choose central purchasing.

Then describe the structure on a project you know: how many plants and storage locations, how purchasing was organised, and one decision about the structure that the business had to make early.

3. What is the difference between a purchasing info record and a source list?

What it tests: Understanding of master data used in source determination.

An info record stores the relationship between a supplier and a material, such as price, conditions and planned delivery time. A source list defines which sources are allowed or fixed for a material in a plant over a period, and can be made mandatory.

Explain how they work together in source determination when a requisition is converted, and how a quota arrangement splits demand between several suppliers.

4. Name common movement types and what they do.

What it tests: Practical inventory knowledge from real goods movements.

101 goods receipt for a purchase order, 102 its reversal, 122 return delivery to the supplier, 201 goods issue to a cost centre, 261 goods issue to a production order, 311 transfer between storage locations, 301 transfer between plants in one step, 551 scrapping and 561 initial stock entry.

Say which ones you used and in what situation, rather than reciting the list.

5. What is the difference between a purchase requisition and a purchase order?

What it tests: Whether you understand internal requests versus external commitments.

A purchase requisition is an internal request for a material or service. It can be created manually or by MRP and has no legal effect outside the company. A purchase order is the formal commitment to a supplier, with price, quantity, delivery date and terms.

Explain how requisitions are converted to orders in your project, for example through assignment of a source and conversion in ME57 or a Fiori app, and where the approval sat.

6. What are the types of outline agreements?

What it tests: Knowledge of purchasing documents and when a business uses each one.

Contracts, either quantity or value contracts, against which release orders are raised, and scheduling agreements, which carry delivery schedule lines. Explain when a business uses each: a value contract for services or spend limits, a scheduling agreement for regular deliveries of direct materials.

Three to five years

Here the interviewer wants to hear about configuration you did, issues you resolved and integration with finance.

1. How does automatic account determination work in MM?

What it tests: The integration point with finance, which experienced candidates must know.

Postings are determined by the valuation grouping code, the general modification, the valuation class from the material master and the transaction key. Configuration is in OBYC. Common keys are BSX for inventory, WRX for GR/IR clearing, GBB for offsetting entries such as consumption and scrapping, and PRD for price differences.

Describe an account determination error you traced, such as a missing valuation class assignment, and how you fixed it.

2. How did you configure a release strategy for purchase orders?

What it tests: Hands-on configuration of approvals.

Explain characteristics and class (for example net value, purchasing group and document type), release groups, release codes, release indicators, release strategies and the conditions that trigger them. Mention how changes after release can reset the strategy.

If your project used flexible workflow in S/4HANA instead, say so and explain the difference.

3. Explain split valuation and when you would use it.

What it tests: Valuation depth, and whether you can weigh the business benefit against the effort.

Split valuation lets one material carry different valuations by valuation type, for example by origin, quality or in-house versus external procurement. It is activated globally, with valuation categories and types assigned in the material master.

Give the business reason you met, and the extra effort it adds to goods movements.

4. How do subcontracting and consignment work?

What it tests: Special procurement processes.

In subcontracting, components are provided to the supplier with movement type 541, the finished item is received against the subcontracting purchase order, and component consumption is posted with 543. In supplier consignment, stock is held in your warehouse but owned by the supplier until you withdraw it, and the liability is settled through MRKO.

Describe one of these processes from a project, including any issue at go-live.

5. How does invoice verification handle price and quantity differences?

What it tests: Whether you can explain blocked invoices and how they are released.

When the invoice price or quantity differs from the purchase order or goods receipt beyond the tolerances, the invoice is posted but blocked for payment. Tolerance keys such as PP for price variance and DQ for quantity variance are configured per company code. Blocked invoices are released in MRBR once the difference is resolved.

Describe how your project set tolerances with finance and how blocked invoices were monitored, and one recurring cause you helped remove.

6. How does MRP decide what to order?

What it tests: Planning knowledge that links purchasing to demand.

MRP compares requirements, such as sales orders, forecasts and dependent demand, with available stock and incoming receipts, and creates planned orders or purchase requisitions for the shortfall. The MRP type, lot size, safety stock, planned delivery time and goods receipt processing time in the material master drive the result.

Say which MRP types you set up, how you checked the results in the stock/requirements list (MD04), and a planning issue you resolved, such as wrong lead times causing late orders.

7. How does a stock transport order work between plants?

What it tests: Cross-plant and cross-company flows.

Explain the one-step and two-step options, the supplying and receiving plant settings, whether a delivery is created, and the difference between intra-company and inter-company transfers, where billing and invoice verification are involved.

Senior and lead consultants

Senior interviews focus on design, data, integration and leading delivery.

1. What changes for procurement in S/4HANA?

What it tests: Current release knowledge and migration awareness.

Suppliers are maintained as business partners. The material ledger is active for valuation. MRP Live is available for planning. The inventory data model is simplified, with material documents stored in table MATDOC. Fiori apps and flexible workflow change how users approve and monitor purchasing.

Say which of these you have delivered and what the migration impact was.

2. How would you approach material master data quality before a migration?

What it tests: Ownership of the most common cause of go-live problems.

Cover profiling the current data, agreeing data owners and standards, cleansing duplicates and obsolete materials, mapping old values to new ones, and running mock loads with business sign-off. Mention governance after go-live so the quality does not slip again.

3. How do you design a procurement process for a group with central and local purchasing?

What it tests: Design judgement, and whether you start from the business rather than the system.

Explain how you would choose between a central purchasing organisation, plant-specific purchasing organisations or reference purchasing organisations, and how contracts and conditions are shared. Tie the choice to the business: spend visibility, negotiating power and local autonomy.

4. How do you work with finance on inventory valuation and month-end?

What it tests: Integration leadership between logistics and finance.

Cover the agreements you need with finance: the valuation approach (standard or moving average price), how price differences are handled, the material ledger and actual costing where used, GR/IR analysis at month end, and who owns each reconciliation.

A strong answer shows that you take responsibility for the numbers that logistics produces in the ledger, not only for the documents.

5. Tell me about a difficult cutover you were part of.

What it tests: Delivery maturity under pressure, and what you learned from it.

Describe the objects you migrated, such as open purchase orders, stock and info records, the timing constraints, what went wrong and how the team recovered. Interviewers want to hear what you would do differently.

How to prepare

Before the interview

  • Choose two projects and prepare the full story: scope, your role, configuration you did and what changed after go-live.
  • Know your account determination: be ready to trace a posting from a goods movement to the GL accounts.
  • Prepare one production issue you resolved, step by step.
  • Be clear about whether your experience is ECC, S/4HANA or both.

Going deeper: how the SAP Readiness Check assesses a migration, by Noel D’Costa on noeldcosta.com.

Transaction codes, tables and options vary by release and by how a system has been configured. Answer from the system you actually worked on, and say which release it was.

Make yourself comfortable

Optional campaign attribution

Remember the campaign that brought you here. Rejecting does not affect assessments, orders or sign-in. Withdrawing clears saved attribution.

Current choice: Not yet chosen