Top 30 SAP MM Interview Questions for 2026 — with Model Answers & S/4HANA Scenarios

The SAP job market in 2026 has significantly shifted from traditional ECC memorization to S/4HANA business process architecture, integration troubleshooting, and cross-functional logic.

Having conducted over 500+ technical interviews for Fortune 500 consulting partners (including Accenture, IBM, Capgemini, and Infosys), I have compiled the top 30 questions you are guaranteed to encounter, along with exact model responses that will set you apart from typical candidates.

1. Core Procure-to-Pay (P2P) Architecture

Q1: Explain the end-to-end Procure-to-Pay (P2P) cycle in SAP S/4HANA with key transaction codes and accounting entries.

Model Answer:

The standard P2P cycle consists of 6 core stages:

1. Determination of Requirements: Creation of Purchase Requisition (PR) via ME51N or automatically generated by MRP. (No FI entry)
2. Source Determination & RFQ: RFQ creation via ME41, quotation comparison via ME49, and contract / info record creation.
3. Purchase Order (PO): Legally binding document issued to supplier via ME21N. (No FI entry)
4. Goods Receipt (GR): Recorded in MIGO with movement type 101. Generates Material Document and Accounting Document:

   Debit: Inventory Account (BSX)
   Credit: GR/IR Clearing Account (WRX)

5. Invoice Verification (IR): Vendor invoice verified in MIRO:

   Debit: GR/IR Clearing Account (WRX)
   Credit: Vendor Payable Account (KBS)

6. Payment Processing (FI-AP): Automatic Payment Program via F110:

   Debit: Vendor Payable Account (KBS)
   Credit: Bank Outgoing Clearing Account

Q2: What is the Business Partner (BP) concept in S/4HANA, and how does it replace traditional vendor master transactions (XK01/MK01)?

Model Answer: In SAP S/4HANA, the Business Partner (transaction BP) is the single point of entry to maintain master data for customers, vendors, and contacts. The traditional transactions XK01, FK01, and MK01 are deprecated and redirect to BP. The core vendor roles are FLVN00 (Financial Accounting Vendor) and FLVN01 (Purchasing Vendor).

2. FI-MM Integration (OBYC Account Determination)

Q3: How does SAP determine GL Accounts automatically during Goods Receipt and Invoice Posting? Explain OBYC parameters.

Model Answer: Automatic Account Determination operates through the following 7-step sequence:

• Chart of Accounts: Determined from Company Code assigned to the Plant.
• Valuation Grouping Code: Groups plants with common accounting structures (configured via OMWD).
• Valuation Class: Assigned to Material Master (Accounting 1 tab) to group similar materials.
• Account Category Reference (ACR): Links Material Types (OMS2) to allowed Valuation Classes.
• Transaction / Event Key: Determines internal posting rule (e.g. BSX for Inventory, WRX for GR/IR, PRD for Price Differences).
• Valuation Modifier & General Modification: Sub-keys (like KBS, VBR, ZOB) to differentiate offsetting entries.

3. Split Valuation & Special Stocks

Q4: What is Split Valuation, and what business scenarios require its activation?

Model Answer: Split Valuation allows a business to value stocks of the same material in the same plant at different prices based on criteria such as:

• Procurement Type: In-house manufactured vs. Externally procured.
• Origin / Batch: Domestic vs. Imported shipments.
• Quality / Condition: Grade A vs. Grade B, or New vs. Refurbished/Repaired spare parts.

Configured via transaction OMWC by defining Valuation Types, Valuation Categories, and activating them at the plant level.

4. Release Strategy & S/4HANA Flexible Workflow

Q5: What is the difference between Classic PO Release Strategy (Classification) and Flexible Workflow in S/4HANA?

Model Answer:

• Classic Release Strategy: Configured via SPRO with Release Groups, Codes, Indicators, and Classification (CT04 & CL02N) linked to structure CEKKO. Approvals are executed in SAP GUI via ME28 or ME29N.
• S/4HANA Flexible Workflow: Managed via Fiori app "Manage Workflows for Purchase Orders". Supports dynamic condition evaluation, multi-level sequential and parallel approvals, auto-assignment to teams/responsibilities, and direct mobile approval via the Fiori "My Inbox" app.

5. Scenario-Based Troubleshooting Questions

Q6: A user encounters error "Account determination for entry 1000 WRX ____ 3000 not possible". How do you resolve this?

Model Answer:

1. Identify Chart of Accounts (1000), Transaction Key (WRX for GR/IR), and Valuation Class (3000).
2. Go to transaction OBYC → double-click on WRX.
3. Enter Chart of Accounts 1000.
4. Add a new line with Valuation Class 3000 and assign the appropriate GR/IR clearing GL Account. Save and retry the MIGO transaction.