As companies rapidly transition to SAP S/4HANA, the expectations for SAP MM (Materials Management) consultants are shifting. Interviewers in 2026 are not just looking for basic transaction code knowledge; they want to see your understanding of S/4HANA architecture, Business Partner integration, Fiori usability, and real-world problem solving.
This comprehensive guide covers the top SAP MM interview questions for 2026, divided into core concepts, S/4HANA specifics, and real project scenarios.
Part 1: Core SAP MM Concepts (S/4HANA Context)
1. Explain the complete Procure-to-Pay (P2P) cycle in SAP MM.
Answer: The P2P cycle represents the entire procurement process. The standard steps are:
- Determination of Requirements: Creating a Purchase Requisition (PR) manually or via MRP.
- Source Determination: Identifying the best vendor using Source Lists, Info Records, or Quotations.
- Vendor Selection: Sending a Request for Quotation (RFQ) and evaluating responses.
- Purchase Order (PO) Processing: Converting the PR into a formal PO and sending it to the vendor.
- Order Monitoring: Tracking delivery timelines and sending reminders.
- Goods Receipt (GR): Receiving the materials and posting a GR (movement type 101) via
MIGO, which updates inventory and generates an accounting document. - Invoice Verification: Verifying the vendor invoice against the PO and GR (3-way match) using
MIRO. - Payment Processing: The Finance (FI) team processes the payment to the vendor.
2. What is the difference between a Purchase Requisition (PR) and a Purchase Order (PO)?
Answer: A Purchase Requisition is an internal document used to request the purchasing department to procure a specific quantity of a material or service by a certain date. It is not legally binding. A Purchase Order is an external, legally binding document sent to a vendor, confirming the intent to buy materials or services under specified conditions. PRs are created via ME51N and POs via ME21N.
3. What are the common Movement Types in SAP MM?
Answer: Movement types are three-digit keys used to control goods movements.
| Movement Type | Description |
|---|---|
| 101 | Goods receipt against a purchase order |
| 102 | Reversal of goods receipt |
| 122 | Return delivery to the vendor |
| 201 | Goods issue for a cost center |
| 261 | Goods issue for a production order |
| 301 | Plant-to-plant transfer posting in one step |
| 311 | Storage location-to-storage location transfer |
4. Explain the concept of a Purchasing Info Record.
Answer: An Info Record serves as the source of information for procurement, linking a specific material to a specific vendor. It stores data such as current and future vendor pricing, delivery lead times, planned delivery times, and tolerance limits. In S/4HANA, Info Records are critical for automating source determination. They are maintained via ME11 (create) and ME12 (change).
Part 2: S/4HANA Specific Procurement Changes
5. What is the biggest master data change in S/4HANA MM compared to ECC?
Answer: The biggest change is the mandatory adoption of the Business Partner (BP) concept. In ECC, vendors and customers were created separately using different transaction codes (like XK01 for vendors). In S/4HANA, the single point of entry for creating, displaying, and editing master data for business partners, customers, and vendors is transaction BP. The system manages the underlying vendor/customer tables automatically.
6. Explain what happened to the MKPF and MSEG tables in S/4HANA.
Answer: To dramatically improve database performance and reduce data footprint, SAP replaced the traditional document header (MKPF) and document item (MSEG) tables. In S/4HANA, material document data is stored in a single, flat table called MATDOC. The old tables exist only as CDS (Core Data Services) compatibility views for custom code that still references them.
7. What is SAP Fiori, and how does it impact the MM consultant?
Answer: SAP Fiori is the modern user experience for S/4HANA. Instead of heavily relying on SAP GUI with complex T-codes, users access role-based, intuitive apps via a web browser. For an MM consultant, this means understanding Fiori Catalogs, Groups, and the standard apps available for procurement (like "Manage Purchase Orders" or "Post Goods Receipt"). Fiori is also the foundation for Embedded Analytics.
Part 3: Real-World Project Scenarios
8. Scenario: A vendor delivered 100 laptops, but 5 are damaged. How do you handle this systemically?
Answer: I would use Movement Type 122 (Return delivery to vendor) in MIGO. This movement type references the original material document of the goods receipt. It decreases warehouse stock, reverses the accounting entries for the 5 damaged units, and automatically updates the purchase order history so the purchasing department knows a replacement is needed.
9. Scenario: The business wants automatically generated Purchase Orders to require director approval ONLY if the value exceeds $50,000. How do you configure this?
Answer: I would configure a Release Strategy for Purchase Orders. I would define a Release Characteristic based on the PO total value field (CEKKO-GNETW). Then, I would create a Release Class assigning this characteristic. Finally, I would define a Release Strategy with specific Release Codes (representing the buyer and the director) and set the prerequisite that the director's release code is only triggered if the value logic threshold ($50,000) is met. Configuration is done via SPRO under Materials Management - Purchasing - Purchase Order - Release Procedure.
10. Scenario: During Goods Receipt (MIGO), the system throws an error: "Account determination for entry INT GBB VBR 3000 not possible." How do you troubleshoot this?
Answer: This is an OBYC (Automatic Account Determination) configuration error. Here is my troubleshooting path:
- Check the Valuation Class assigned to the Material Master (Accounting 1 view). Let us assume it is 3000.
- Check the Movement Type used in MIGO. If it is 201 (Goods Issue to Cost Center), it points to the Transaction Event Key GBB with Account Modifier VBR.
- Go to Transaction
OBYC. - Select Transaction Key GBB.
- Look for the combination of Chart of Accounts (INT), Account Modifier (VBR), and Valuation Class (3000).
- The error means a GL Account is missing for this exact combination. I would request Finance to provide the correct expense GL account and assign it in OBYC.
11. Scenario: You are moving a business from an old legacy system to S/4HANA. How do you migrate the inventory balances?
Answer: Inventory balances cannot be imported passively; they must be posted into the system to generate financial documents. I would use the SAP S/4HANA Migration Cockpit (transaction LTMC or the newer Fiori app 'Migrate Your Data'). The migration object for Material Inventory uses Movement Type 561 internally. Before loading, we must ensure all material masters are complete, open posting periods are aligned between MM (MMPV) and FI (OB52), and standard prices are loaded.
Key Preparation Tips for 2026
- Know Integration: MM does not operate in a vacuum. Understand how Movement Types trigger Finance (FI) entries and how MRP triggers Production Planning (PP) orders.
- Speak S/4HANA: Ensure you confidently use S/4HANA terminology (MATDOC, Business Partner, Fiori, CDS Views) rather than relying solely on ECC concepts.
- Prepare for Scenarios: Interviewers want to see your logic. When given a problem, walk them through your troubleshooting steps in the SAP configuration menu (
SPRO).
Key Takeaway
SAP MM interviews in 2026 test S/4HANA-specific knowledge (Business Partner, MATDOC, Fiori) alongside traditional process mastery (P2P cycle, movement types, OBYC account determination). Prepare with real troubleshooting scenarios - the ability to walk through a problem step-by-step using the correct T-codes is what separates good candidates from great ones.
