SAP MM Interview Questions and Answers 2026-27

1) Master Data Management: Master data is the foundation of SAP MM. Without accurate data, procurement and inventory processes can fail. The key master data includes: Material Master (MM01) – Stores all material-related information; Vendor Master (XK01) – Maintains supplier details; Purchase Info Record (ME11) – Links vendors to materials with pricing; Source List (ME01) – Defines approved vendors for materials.

2) Procurement Process: Purchase Requisition (PR) (ME51N) – Internal request for materials; Purchase Order (PO) (ME21N) – Formal order sent to vendors; Request for Quotation (RFQ) (ME41) – Collects price quotes from suppliers; Contracts & Scheduling Agreements – Long-term procurement planning.

3) Inventory Management: Goods Receipt (GR) (MIGO, MB1C) – Records incoming stock; Goods Issue (GI) (MB1A, MB1B) – Tracks stock consumption; Stock Transfer (MB1B, MIGO) – Moves stock between locations; Physical Inventory (MI01, MI07) – Verifies actual stock vs. system stock.

4) Invoice Verification: Invoice Posting (MIRO) – Matches invoices with purchase orders; Invoice Blocking & Release – Prevents incorrect payments; Automatic Payment Processing (F110) – Streamlines payments.

5) Material Requirement Planning (MRP): MRP Run (MD01, MD02, MD04) – Calculates material demand; Reorder Point Planning – Ensures stock availability; Consumption-Based Planning – Avoids excess inventory.

Consignment Stock (K) – Stock owned by the vendor but stored at the company's location. Payment is made when used (Example: Raw materials supplied by a vendor and stored in your warehouse).

Subcontracting Stock (O) – Stock sent to a subcontractor for processing but still owned by the company (Example: Sending metal parts to a vendor for coating).

Customer Stock (W) – Stock that is owned by the company but is located at the customer's site (Example: Spare parts stored at a customer's factory for quick service).

Project Stock (Q) – Stock assigned to a specific project and can't be used for general purposes (Example: Raw materials reserved for a construction project).

Sales Order Stock (E) – Stock assigned to a specific sales order and not available for general use (Example: Custom-made products for a specific customer order).

Returnable Transport Packaging (M) – Packaging materials that are sent to the customer but expected to be returned (Example: Reusable containers used for shipping parts).

ROH (Raw Material) – Basic materials used for production (Example: Steel, Chemicals). HALB (Semi-Finished Product) – Partially processed materials used in production (Example: Car Engine, Processed Wood). FERT (Finished Product) – Final product ready for sale (Example: Laptop, Car). HIBE (Operating Supplies) – Consumables used for operations (Example: Office Supplies, Lubricants). VERP (Packaging Material) – Materials used for packaging finished goods (Example: Boxes, Bottles). SERV (Services) – Non-material items like consulting or maintenance (Example: Software Installation, Repairs). ERSA (Spare Parts) – Replacement parts used in maintenance (Example: Machine Components).

SAP MM handles materials that require batch tracking through Batch Management, which enables the system to manage and track materials at the batch level. This is crucial for industries such as pharmaceuticals, chemicals, food, and manufacturing, where materials need to be monitored based on characteristics like expiry date, production date, and quality specifications.

MRP Type in SAP MM (Material Management) defines the planning method used for a material. It controls how the system calculates procurement proposals, such as purchase requisitions or planned orders. Common MRP Types include PD (Material Requirements Planning), VB (Manual Reorder Point Planning), ND (No Planning), and VV (Forecast-Based Planning). MRP Type is maintained in the Material Master (MM02) under the MRP1 tab. It determines if and how a material is planned, whether based on demand, consumption, or manual reorder points.

Shelf life refers to the duration a product remains usable, safe, or effective. There are different types of shelf life based on industry and usage:

Two types of shelf life: 1) Total shelf life, 2) Minimum remaining shelf life.

1) Manufacturing Shelf Life – Time from production until the product is no longer usable. 2) Storage Shelf Life – How long a product remains stable under specified storage conditions. 3) Expiration Date – The final date after which the product should not be used. 4) Best Before Date – Recommended date for optimal quality, not safety. 5) Retest Shelf Life – Time after which a product needs to be tested before further use, common in pharmaceuticals.

Split Valuation in SAP MM allows a single material to have multiple valuation types, enabling different prices for variations like origin, quality, or batch. It is used when the same material has different costs due to factors such as procurement source (in-house vs. external), quality grades, or different batch characteristics. Split Valuation helps in accurate inventory valuation, cost control, and better procurement decisions. It is configured in SAP by defining valuation categories (e.g., batch, procurement type) and valuation types (e.g., domestic, import).

1) Requirement identification (Purchase Requisition - PR). 2) Vendor selection and Purchase Order (PO) creation. 3) Vendor delivers the goods. 4) Goods Receipt (MIGO). 5) Invoice Verification (MIRO) process ensures the invoice matches the PO and goods receipt. 6) Payment processing is completed through the finance module (FICO).

In SAP, Valuation Class determines the GL account for material postings in inventory and accounting transactions. It is assigned in the Material Master (Accounting 1 View) and links materials to the correct General Ledger (GL) accounts based on material type and movement type. This helps in automatic account determination during goods receipt, invoice posting, and stock valuation. Different materials (e.g., raw materials, finished goods) can be linked to different GL accounts through their valuation class.

In SAP ERP HANA and ECC 6.0, in MRP (Material Requirements Planning), the forecast helps predict future material demand based on past consumption patterns. It ensures accurate procurement and production planning by estimating required quantities in advance. Forecasting is primarily used in Forecast-Based Planning (MRP Type VV), where SAP generates procurement proposals based on historical data trends. This prevents stockouts and overstocking, optimizing inventory levels. Forecasts can be adjusted manually or system-driven using statistical models. During an MRP run, forecast values are considered along with current stock, open orders, and demand requirements, ensuring smooth material availability for production and sales while reducing excess inventory costs.

In SAP HANA and ECC 6.0 MM, blocked stock refers to materials that are unusable for consumption or sales due to quality issues, inspection, or other reasons. It is managed using movement type 103 (Goods Receipt Blocked Stock) during GR for Purchase Orders and movement type 105 to release it. For direct blocking, movement type 101 with blocked stock is used. Blocked stock is not included in MRP calculations or available stock. It can be transferred to unrestricted stock through movement type 343 after approval.

In SAP HANA and ECC 6.0 MM, Automatic Account Assignment links material movements to the correct General Ledger (G/L) accounts without manual intervention. It is configured in OBYC (Automatic Account Determination), where SAP maps valuation classes, transaction keys, and account modifiers to G/L accounts. When a material movement (e.g., goods receipt, invoice posting, stock transfer) occurs, SAP automatically determines the relevant account based on the valuation class in the Material Master and movement type.

SAP MM integration with SD (Sales & Distribution) and PP (Production Planning) ensures a seamless flow of materials and data across supply chain processes. Integration with SD enables automatic stock updates during sales, triggering procurement or production if stock is low. It ensures smooth order fulfillment by linking sales orders with material availability. Integration with PP helps in efficient material planning for production, ensuring raw materials are available when needed. This reduces production delays and optimizes inventory. Additionally, MM integration with SD and PP enhances real-time data sharing, cost control, and accurate financial postings, improving overall business efficiency.

Pricing conditions in SAP MM are essential for determining the cost of materials and services in procurement. They define price components such as base price, discounts, surcharges, freight, and taxes, ensuring accurate cost calculation in purchase orders and invoices. SAP uses condition types (Example: PB00 for gross price, RA01 for discount) to structure pricing systematically. Pricing conditions help in vendor negotiations, cost control, and financial transparency by automating price determination. They also integrate with SAP FI for correct accounting postings. Properly maintained pricing conditions ensure consistent procurement pricing, compliance with contracts, and accurate financial reporting in the supply chain.

Stock Transport Orders (STO) play a main role in intercompany stock transfers by facilitating the controlled movement of materials between two company codes within the same organization. Unlike simple stock transfers, STO involves a purchase order (PO) process, ensuring proper documentation, valuation, and financial tracking. STO enables automatic goods receipt, invoice verification, and integration with FI and SD for correct pricing and taxation. It helps maintain accurate inventory levels, transparency, and compliance with intercompany pricing regulations. STOs can be created using ME21N and processed using outbound and inbound deliveries.

1) Intra-Company STO – Transfers stock between plants within the same company code. It involves a stock transport purchase order (PO) but does not create an invoice. 2) Inter-Company STO – Moves stock between plants in different company codes. It includes billing, pricing, and financial postings, integrating with SAP SD and FI. 3) Stock Transfer with Delivery – Uses outbound and inbound deliveries for logistics control, commonly integrating with shipping and transportation modules.

1) OMS9 – Define Field Selection for Material Master (control mandatory, optional, or hidden fields). 2) OMSR – Maintain Field Selection Groups (group related fields for control). 3) OMT3 – Configure Material Master Views (define which views appear based on material type). 4) SE11 – Create or modify custom fields in the material master using Data Dictionary.

In SAP HANA and ECC 6.0, long-term agreements with suppliers are managed using outline agreements, which include contracts and scheduling agreements. A contract (ME31K) defines agreed terms and prices for a specific period but requires release orders (POs) for procurement. A scheduling agreement (ME31L) allows automatic delivery schedules without needing separate POs. These agreements ensure stable pricing, better supplier relationships, and streamlined procurement. SAP enables tracking through release documentation, validity periods, and quantity limits. Integration with MRP ensures timely order creation. Managing long-term agreements improves cost control, procurement efficiency, and supplier collaboration, reducing manual efforts and ensuring supply chain stability.

In SAP MM, Returnable Transport Packaging (RTP) is linked to the Vendor Master and Purchase Orders (POs) to track and manage reusable packaging materials. In the Vendor Master (XK01 / MK01), RTP materials are assigned under procurement settings. When creating a PO (ME21N), RTP materials (e.g., pallets, containers) are included as non-valuated items (Material Type: LEIH - Loan Material). These materials are received using movement type 501M (without PO) or 101 (with PO) and tracked separately. RTP is later returned to the vendor using movement type 161.

SAP MM (Materials Management) is a core module of SAP ERP that manages procurement, inventory, and material valuation processes. It covers the full cycle from raising a purchase requisition, creating a purchase order, receiving goods, verifying invoices, and maintaining accurate stock levels. SAP MM integrates closely with SD (Sales), PP (Production), and FI/CO (Finance and Controlling) so that material movements automatically update inventory value and accounting entries across the organization.

The Material Master is the central data record for every material a company purchases, produces, stores, or sells in SAP. It is organized into views — Basic Data, Purchasing, MRP, Accounting, Storage, and others — each maintained at a different organizational level (client, plant, storage location). Because nearly every MM transaction reads from the Material Master, incomplete or inaccurate master data is one of the most common root causes of downstream errors in procurement and inventory processes.

A Purchase Order (created via ME21N) is a formal, legally binding document sent to a vendor requesting the delivery of specific materials or services at agreed prices, quantities, and delivery dates. Once created, it drives downstream processes including goods receipt (MIGO) and invoice verification (MIRO), and it can be created directly, converted from a Purchase Requisition, or released against a Contract or Scheduling Agreement.

A Purchase Requisition (PR, created via ME51N) is an internal document requesting that a material or service be procured — it never goes to a vendor and has no legal standing outside the company. A Purchase Order (PO, created via ME21N) is the external, vendor-facing document that actually commits the company to buy at agreed terms. In practice, a PR is typically converted into a PO after vendor selection, often via ME59N for automatic conversion or ME21N for manual conversion.

The Procurement Cycle covers the full sequence: requirement determination (Purchase Requisition), vendor selection and RFQ processing where relevant, Purchase Order creation, goods receipt against the PO (MIGO), invoice verification matching the PO and GR (MIRO), and payment processing through FI. Each step updates connected master data and accounting entries automatically, which is what makes SAP MM's procurement cycle end-to-end rather than a series of disconnected manual steps.

A Movement Type is a three-digit key that classifies the nature of a stock movement in SAP MM, controlling which fields are required, which GL accounts are updated, and which stock category is affected. Common examples include 101 (goods receipt for a purchase order), 201 (goods issue to a cost center), 301 (transfer posting between plants), and 561 (initial stock entry). Movement types are central to almost every inventory transaction, since they determine the accounting and stock impact of every posting.

The Vendor Master (created via XK01) is the central record of supplier data used across MM, FI, and SD. It stores general data (name, address, communication details), company-code-specific data (reconciliation account, payment terms, bank details), and purchasing-organization data (order currency, incoterms, purchasing group). Every purchase order and invoice verification transaction pulls directly from the Vendor Master, so incomplete records here commonly block procurement transactions until corrected.

The Vendor Master has three main data segments: General Data (name, address, and control data, shared across all company codes), Company Code Data (reconciliation account, payment terms, and dunning data specific to one company code), and Purchasing Organization Data (order currency, terms of delivery, purchasing group, and partner functions specific to one purchasing organization). Together these segments determine how a vendor is treated financially and procedurally in every transaction.

A Quota Arrangement (maintained in MEQ1) automatically splits procurement of a material across multiple approved vendors according to defined percentage quotas, rather than a single source. It is commonly used to maintain supplier diversification, manage risk, or fulfill contractual minimum-purchase commitments with more than one vendor. During an MRP run, the system uses the quota arrangement to decide which vendor should receive each new procurement proposal.

Material Type is a classification in the Material Master (such as ROH for raw materials, FERT for finished goods, or HALB for semi-finished products) that controls which views are relevant, the number range used, whether the material is quantity or value updated, and which GL accounts apply through account determination. Choosing the correct material type at creation is important because changing it later is restricted and can require significant reconfiguration.

Valuation Class, maintained on the Accounting 1 view of the Material Master, links a material to a specific set of GL accounts through automatic account determination (OBYC). It allows different categories of materials — such as raw materials, trading goods, and finished products — to post to different balance sheet and P&L accounts automatically during goods receipt, invoice verification, and consumption postings, without requiring manual account entry on every transaction.

A Material Group is a higher-level classification used to group similar materials together for reporting, analysis, and purchasing organization purposes, independent of material type. It is commonly used to run spend analysis by category, restrict certain purchasing activities to specific material groups, and simplify vendor evaluation by comparing pricing and performance within the same material category rather than across the entire material master.

A Contract (created via ME31K) is a long-term outline agreement with a vendor covering agreed prices and terms for a material or material group over a defined validity period, without specifying delivery dates or quantities upfront. Actual procurement happens through release orders (POs) created against the contract, which is why contracts are valuable for negotiating better pricing on materials purchased repeatedly over time without committing to fixed delivery schedules.

A Scheduling Agreement (created via ME31L) is an outline agreement that includes specific delivery schedules and quantities agreed with a vendor over time, allowing automatic, recurring deliveries without creating a separate PO for each one. It is typically used for materials with predictable, ongoing consumption, such as components feeding a production line, where delivery reliability and reduced administrative overhead matter more than one-off pricing negotiation.

Returnable Transport Packaging (RTP) refers to reusable packaging materials, such as pallets, crates, or containers, that are sent to a customer or received from a vendor with the expectation that they will be returned rather than consumed. In SAP, RTP materials are typically set up as a special material type (LEIH - Loan Material) and tracked using dedicated movement types, since they represent company assets moving in and out of the business without being sold or consumed.

This repeats Question 2 above — a Scheduling Agreement (ME31L) is an outline agreement with predefined delivery schedules and quantities, enabling automatic recurring deliveries from a vendor without a separate purchase order for each shipment, commonly used for high-frequency production components.

Stock Transport Orders (STO) enable controlled stock movement between two plants, either within the same company code or across different company codes, using a purchase order process rather than a simple stock transfer. This ensures proper documentation, valuation, and — for inter-company transfers — correct billing and financial postings between the two company codes involved. STOs are created using ME21N and processed through outbound and inbound deliveries.

Goods Receipt records the physical arrival of materials into a plant or storage location, most commonly posted against a Purchase Order using transaction MIGO. Posting a GR increases stock quantity, updates the material's moving average or standard price depending on the valuation method, and creates a material document along with an accounting document that posts the corresponding GL entries automatically through account determination.

Goods Issue records the outward movement of stock from a plant or storage location, typically for consumption (to a cost center or production order), delivery to a customer, or scrapping. It is posted using MB1A or MIGO with the appropriate movement type (such as 201 for cost center consumption or 261 for production order consumption), reducing stock quantity and posting the corresponding accounting entry automatically.

Transfer Posting moves stock between plants, storage locations, or stock categories (for example, from quality inspection to unrestricted-use) without a sale or consumption taking place. It is posted using MB1B or MIGO with movement types such as 301 (plant-to-plant transfer) or 321 (quality-to-unrestricted transfer), and depending on the movement type, may or may not trigger a change in stock valuation.

A Reservation is a request to set aside a specific quantity of material for a planned future use, such as a production order or cost center consumption, ensuring that stock is not consumed by other demands before it is needed. Reservations can be created manually (MB21) or generated automatically by production orders and MRP, and they are visible in stock overview reports as committed, rather than freely available, quantity.

A Batch is a specific, traceable quantity of a material produced or received together, sharing common characteristics such as manufacturing date, quality grade, or expiry date. Batches are created using MSC1N and are essential for industries requiring traceability and shelf-life control, allowing a company to isolate and manage a single production lot separately from other stock of the same material number.

Invoice Verification, performed using MIRO, is the process of matching a vendor's invoice against the corresponding Purchase Order and Goods Receipt to confirm quantities and prices align before payment is released. If the invoice, PO, and GR match within configured tolerance limits, the invoice posts automatically; if not, it is blocked for review, which is the standard three-way match control most SAP MM implementations rely on.

Tax Codes determine how tax (such as GST, VAT, or sales tax) is calculated and posted on procurement transactions, linking a specific tax rate and GL account combination to purchase orders and invoices. They are configured in FI (transaction FTXP) but are used throughout MM documents, ensuring the correct tax amount is automatically calculated and posted without manual tax entry on every purchase order or invoice.

GR-Based Invoice Verification requires a Goods Receipt to exist before the corresponding invoice can be posted, and allows invoicing per individual GR document, which is useful when multiple partial deliveries occur against one PO line. Invoice-Based (or PO-based) Verification allows the invoice to be posted directly against the PO quantity without requiring a matching GR reference, which is common for services or materials where GR is not tracked at the same granularity.

Freight costs are typically handled as a delivery cost condition type (such as FRA1 or FRB1) on the Purchase Order's Conditions tab, either as a planned delivery cost (known at PO creation, capitalized into material cost at goods receipt) or an unplanned delivery cost (added later during invoice verification). Planned freight is distributed proportionally across the GR quantity and affects moving average price, while unplanned freight is typically posted to a separate expense account depending on configuration.

Pricing Conditions define the individual components that make up the final price on a purchase order or invoice, such as gross price (PB00), discounts, surcharges, freight, and tax. Each condition type is configured with its own calculation rule and can be automatically proposed from an Info Record or Contract, or entered manually, giving procurement teams a structured, auditable way to build up total cost rather than entering a single lump-sum price.

Subcontracting is a procurement process where a company sends raw materials or components to an external vendor, who processes them into a finished or semi-finished product and returns it. It is configured using a subcontracting Purchase Order (item category L), with the components provided tracked as subcontracting stock (special stock category O) at the vendor's location until the finished product is received back via goods receipt.

A Planned Goods Issue is triggered by a known, scheduled demand such as a production order component reservation or a delivery against a sales order, and typically references that originating document during posting. An Unplanned Goods Issue is a direct, ad-hoc consumption posting — for example, issuing material to a cost center for an unplanned repair — made without reference to a pre-existing reservation or order.

Account Assignment Category, entered on a Purchase Requisition or Purchase Order line item, determines which account (cost center, project, asset, or sales order) a non-stock or direct-consumption material is charged to, along with which fields are required for that assignment. Common categories include K (Cost Center), F (Order), A (Asset), and P (Project), and choosing the correct category ensures the procurement cost lands on the right internal or external cost object.

Contracts are created using ME31K, specifying the vendor, validity period, target value or quantity, and pricing conditions for a material or material group. Once active, purchase orders are released against the contract using ME21N with reference to the contract number, which automatically consumes the contract's target value or quantity. Ongoing management includes monitoring consumption against target value, extending validity periods, and renegotiating pricing conditions as the agreement approaches expiry or its committed value.

Implementing Fiori apps for MM typically involves activating the relevant OData services and Fiori tiles for MM processes (such as Manage Purchase Orders, Manage Purchase Requisitions, or Monitor Material Coverage) in the Fiori Launchpad, assigning the correct PFCG roles and catalogs to users, and confirming the backend S/4HANA or embedded Fiori front-end server is properly configured to expose the relevant business objects. Adoption also depends on training end users to transition from familiar SAP GUI transactions to the equivalent Fiori app workflows.

Staying current with SAP MM typically involves monitoring SAP's official release notes and SAP Notes for the module, following SAP Community forums and blog posts for practical implementation experiences, tracking simplification lists and functional changes when a system moves to S/4HANA, and periodically reviewing SAP's roadmap explorer for planned innovations. Hands-on practice in a sandbox system with each new release is the most reliable way to understand how a change actually behaves before it reaches production.

User roles and authorizations, managed through PFCG roles and authorization objects (such as M_BEST_BSA for purchase order document type authorization), control which MM transactions a user can execute and which data they can view or change — for example, restricting purchase order creation to a specific purchasing organization or limiting invoice release authority based on a value threshold. A well-designed authorization concept enforces segregation of duties, such as preventing the same user from both creating a purchase order and approving its invoice, which is a standard internal control requirement in procurement.

This guide covers 19 detailed, real-time scenario questions plus 34 additional questions across Basic Concepts, Master Data, Procurement Process, Inventory Management, and Invoice Verification — 53 questions in total, all fully answered.

Yes. The Basic Concepts and Master Data sections are well suited for freshers building foundational knowledge, while the 19 detailed scenario questions and the Invoice Verification and Extra section cover configuration and real-world judgment calls more relevant to experienced candidates and current SAP MM consultants.

Prioritize understanding of the core procurement cycle, master data structure, movement types, account determination (OBYC), and batch management, since these are asked in almost every SAP MM interview regardless of ECC or S/4HANA. For S/4HANA-specific preparation, also review Fiori app usage for MM processes and any simplification changes affecting classic MM transactions.

Practice explaining not just what a transaction does, but why a business would need it and what happens if it is configured incorrectly — interviewers frequently probe for this reasoning. Working through the 19 detailed scenario questions in this guide, which explain the "why" behind each answer rather than just listing steps, is a good way to build that habit.