SAP Consultant Interview Questions: MM, SD, FICO, S/4HANA, and More

Last updated: March 2026

SAP consulting interviews are among the most technically demanding in enterprise technology. Unlike general software engineering interviews that test algorithmic thinking, or management consulting interviews that test structured problem-solving, SAP interviews test deep module-specific knowledge, implementation experience, and the ability to navigate the complex intersection of business processes and technical configuration. An SAP MM consultant who cannot explain the three-way match in procurement, or an SD consultant who cannot walk through the order-to-cash cycle, will not survive the first technical round.

This guide covers the interview questions and scenarios you will encounter across the most common SAP modules — MM (Materials Management), SD (Sales and Distribution), FICO (Financial Accounting and Controlling), EWM (Extended Warehouse Management), and S/4HANA-specific topics — as well as cross-module questions on implementation methodology, integration, cutover planning, and the day-to-day reality of SAP consulting.

SAP MM (Materials Management) Interview Questions

Materials Management is one of the most widely implemented SAP modules and covers the entire procurement lifecycle. Interviewers expect consultants to demonstrate fluency in both configuration and business process understanding.

Core MM Questions

Q: Explain the procure-to-pay (P2P) cycle in SAP MM.

The procure-to-pay cycle follows this sequence: Purchase Requisition (PR) creation, either manually or via MRP run, followed by conversion to a Purchase Order (PO). The vendor delivers goods, which are recorded through a Goods Receipt (GR) posting (MIGO transaction). The vendor sends an invoice, which is processed through Invoice Verification (MIRO transaction). Finally, payment is executed through FI (Financial Accounting). Each step generates corresponding accounting documents — the GR creates a GR/IR clearing account entry, and invoice verification settles against this clearing account.

Q: What is the three-way match and why does it matter?

The three-way match compares the Purchase Order, Goods Receipt, and Invoice to ensure consistency in quantity, price, and terms before approving payment. SAP performs this automatically during invoice verification (MIRO). Discrepancies beyond configured tolerance levels trigger blocks that require manual intervention. The three-way match is a critical internal control that prevents overpayment, unauthorised purchases, and fraud.

Q: Explain the difference between a stock transfer order and a stock transport order.

A stock transfer order (STO) moves material between two plants within the same company code using a one-step or two-step procedure. A stock transport order generates a purchase order between plants, often across different company codes, and follows the full procurement process including goods receipt. Stock transport orders are used when intercompany pricing, billing, or customs documentation is required.

Q: What are the key organizational levels in MM and how do they relate?

Organizational Level	Purpose	Relationship
Client	Highest level; represents the entire enterprise	Contains all company codes
Company Code	Legal entity for financial reporting	Contains one or more plants
Plant	Manufacturing or logistics facility	Contains storage locations
Storage Location	Physical inventory location within a plant	Assigned to a plant
Purchasing Organization	Entity responsible for procurement	Can be assigned to company code, plant, or cross-company
Purchasing Group	Buyer or group of buyers	Assigned to purchasing organization

Q: How does MRP work in SAP MM?

MRP (Material Requirements Planning) calculates net requirements by comparing demand (sales orders, planned independent requirements, reservations) against supply (current stock, purchase orders, planned orders, production orders). The MRP run (transaction MD01/MD02) generates planned orders for materials whose stock falls below the reorder point or safety stock. Key MRP types include MRP (deterministic planning), reorder point planning, and forecast-based planning. The MRP controller then converts planned orders into purchase requisitions or production orders.

Advanced MM Questions

Q: How would you handle a client who wants to implement consignment inventory in SAP?

Consignment requires specific configuration: a consignment info record (condition type for consignment price), consignment purchase orders (document type), special stock indicator ‘K’ for consignment stock at plant level. The process flow differs from standard procurement — goods receipt creates consignment stock that belongs to the vendor until consumption. Settlement (transaction MRKO) transfers ownership and triggers payment based on actual consumption. Key considerations include valuation (consignment stock is valued separately), physical inventory counting requirements, and integration with the vendor’s billing process.

Q: Explain release strategies for purchase orders.

Release strategies control PO approval workflows based on configurable criteria — purchase order value, material group, plant, account assignment category, or any combination. Configuration involves defining release groups, release codes, release indicators, release strategies, and classification (using characteristics and classes). In S/4HANA, flexible workflow and business rules frameworks provide more dynamic approval routing, but the classic release strategy remains widely used. A common implementation challenge is balancing approval rigour with process efficiency — too many approval steps create bottlenecks that frustrate users and delay procurement.

---

Level up your job search with AI. OphyAI offers interview copilot, resume builder, and job search tools — all in one platform starting at $9/mo.

---

SAP SD (Sales and Distribution) Interview Questions

SD covers the order-to-cash cycle and is deeply integrated with MM, FICO, and warehouse management modules.

Core SD Questions

Q: Walk through the order-to-cash (O2C) cycle in SAP SD.

The cycle begins with a sales inquiry or quotation, followed by sales order creation (VA01). After order confirmation and availability check, the system creates a delivery document (VL01N), which triggers picking and packing in the warehouse. Goods issue (PGI) posts the inventory reduction and creates accounting entries. The billing document (VF01) is generated based on the delivery, and the accounting document posts the revenue and receivable. Finally, payment is received and applied through FI.

Q: Explain the pricing procedure in SD.

The pricing procedure determines which condition types (discounts, surcharges, freight, taxes) apply to a sales transaction and in what sequence. It is determined by a combination of sales organization, distribution channel, division, document pricing procedure (from document type), and customer pricing procedure (from customer master). Condition records store the actual values for each condition type. The access sequence defines the hierarchy in which the system searches for condition records — for example, customer/material-specific pricing before material-level pricing before price list pricing.

Q: What is the difference between a billing plan and a milestone billing plan?

A periodic billing plan generates billing documents at regular intervals (monthly, quarterly) for a fixed amount — common for rental or subscription services. A milestone billing plan generates billing documents based on project milestones or completion percentages, with each milestone representing a defined value or percentage of the total contract. Milestone billing integrates with the Project System (PS) module for complex project billing scenarios.

Advanced SD Questions

Q: How do you handle intercompany sales in SAP?

Intercompany sales involve a selling company code that receives the customer order and a supplying company code that delivers the goods. Configuration requires: intercompany billing document type, intercompany pricing conditions (PI01/PI02 for intercompany price), customer master for the ordering company code in the delivering company code, and vendor master for the delivering company code in the ordering company code. The process generates two billing documents — one to the external customer and one between company codes — ensuring both legal entities record appropriate revenue and cost.

SAP FICO (Financial Accounting and Controlling) Interview Questions

FICO is the backbone of SAP — every transaction in every module ultimately generates financial accounting entries.

Core FICO Questions

Q: What is the difference between a chart of accounts, an operating chart of accounts, and a country-specific chart of accounts?

The chart of accounts is a list of all G/L accounts used by one or more company codes. The operating chart of accounts is assigned to a company code and used for daily postings and management reporting. The country-specific chart of accounts addresses local statutory reporting requirements — for example, a German company might use an international operating chart of accounts for group reporting and the SKR03 or SKR04 as its country chart for German GAAP (HGB) compliance. A group chart of accounts maps to the operating chart for consolidated reporting.

Q: Explain the document principle in SAP FI.

Every financial transaction in SAP creates a document with a unique document number. Each document contains a header (document date, posting date, document type, company code) and at least two line items that must balance to zero (debit = credit). Documents are the audit trail — they cannot be deleted, only reversed. Document types control the number range and the account types (asset, vendor, customer, G/L) that can be posted. This principle ensures complete traceability of every financial event.

Q: What are the different types of special G/L transactions?

Special G/L transactions are postings to customer or vendor accounts that need to be displayed separately from normal receivables and payables. Common types include:

Special G/L Type	Indicator	Example
Down payment request	F	Customer or vendor advance request
Down payment	A	Actual advance payment received/made
Bill of exchange	B	Bills receivable/payable
Guarantee	G	Bank guarantees
Security deposit	S	Rental or performance deposits

Each special G/L transaction posts to a separate reconciliation account rather than the standard AR/AP reconciliation account, enabling accurate balance sheet classification.

Advanced FICO Questions

Q: How does the New General Ledger (New GL) differ from the classic GL, and what changed in S/4HANA?

The New GL (introduced in ECC 6.0) added document splitting (enabling balance sheets by profit centre, segment, or other dimensions), real-time integration with CO, parallel ledgers for multiple accounting principles (IFRS, local GAAP), and segment reporting. In S/4HANA, the New GL is the only option — the classic GL is eliminated. S/4HANA further introduces the Universal Journal (table ACDOCA), which merges previously separate tables (BSEG, COEP, ACDOCA) into a single table of record for all financial and controlling postings. This simplifies reporting, eliminates reconciliation between FI and CO, and enables real-time analytics directly on transactional data.

Q: Explain the asset accounting lifecycle in SAP.

Asset accounting manages the full lifecycle from acquisition (asset creation and capitalisation), through periodic depreciation (calculated based on depreciation keys, useful life, and depreciation methods), maintenance and revaluation, to retirement (scrapping or sale). Key configuration elements include depreciation areas (book depreciation, tax depreciation, group depreciation), asset classes, and depreciation keys. In S/4HANA, asset accounting runs on the Universal Journal with real-time depreciation posting, replacing the periodic depreciation runs (AFAB) of ECC.

SAP EWM (Extended Warehouse Management) Interview Questions

EWM is increasingly important as companies upgrade from basic WM to the full-featured extended warehouse management capabilities available in S/4HANA.

Q: What are the key differences between WM and EWM?

Feature	Classic WM	EWM
Deployment	Embedded in ECC	Embedded in S/4HANA or decentralised
Warehouse structure	Storage type → Storage section → Storage bin	More granular: Activity area, work centre, resource
Wave management	Not available	Full wave management with wave templates
Labour management	Not available	Integrated labour management and resource planning
Task and resource management	Basic transfer orders	Warehouse tasks with execution steps
Slotting	Not available	Product slotting optimisation
Yard management	Not available	Integrated yard management

Q: Explain the warehouse order concept in EWM.

In EWM, warehouse tasks are grouped into warehouse orders for execution. A warehouse task represents a single move (pick, putaway, internal movement), while a warehouse order groups related tasks for a single resource or wave. This grouping optimises travel paths, balances workloads across resources, and enables sequencing based on priority, destination, or physical proximity. Warehouse order creation rules define how tasks are grouped — by activity area, product, destination, or custom logic.

Q: How does EWM handle hazardous materials?

EWM integrates hazardous material management through hazardous substance master data linked to product master records. Configuration includes storage constraints (which bins can hold hazardous materials), quantity limits per storage section, incompatibility rules (which hazardous classes cannot be stored together), and regulatory documentation requirements. The system enforces these rules during putaway and pick operations, preventing dangerous storage configurations.

S/4HANA-Specific Interview Questions

S/4HANA knowledge is now expected for virtually all SAP consultant roles. Interviewers assess whether candidates understand the architectural changes, not just the functional differences.

Q: What are the most significant architectural changes in S/4HANA compared to ECC?

The fundamental change is the move to SAP HANA as the sole database, enabling in-memory computing with dramatic performance improvements. Key architectural changes include:

• Universal Journal (ACDOCA): Single source of truth for financial and controlling data
• Business Partner: Replaces separate customer (KNA1) and vendor (LFA1) master data with a unified Business Partner concept
• Material Ledger mandatory: Always active, enabling actual costing and parallel valuation
• Simplified data model: Elimination of aggregate tables, index tables, and redundant data structures
• Embedded analytics: Real-time reporting without separate BW extraction
• Fiori UX: Launchpad-based user interface replacing SAP GUI for most transactions

Q: Explain the ASAP methodology for SAP implementations.

ASAP (Accelerated SAP) provides a structured implementation framework:

Phase	Activities	Key Deliverables
1. Project Preparation	Team formation, project planning, infrastructure setup	Project charter, team structure, project plan
2. Business Blueprint	Requirements gathering, process documentation, gap analysis	Business Blueprint document, process flows
3. Realisation	Configuration, development, unit testing	Configured system, custom developments, test scripts
4. Final Preparation	Integration testing, user training, cutover planning, data migration	Trained users, cutover plan, migrated data
5. Go-Live & Support	System cutover, hypercare support, issue resolution	Production system, support processes

In modern S/4HANA implementations, SAP Activate has largely replaced ASAP, incorporating agile principles with iterative sprints, fit-to-standard workshops, and pre-configured best practices as a starting point rather than blank configuration.

Q: Describe your approach to cutover planning for an SAP go-live.

Cutover planning is the most critical element of go-live preparation. A comprehensive cutover plan includes:

1. Timeline: Minute-by-minute schedule from legacy system freeze to production go-live
2. Data migration: Final data loads (master data, open items, balances) with validation checkpoints
3. Technical activities: System configuration transport, role assignments, interface activation
4. Business activities: Legacy system closeout, parallel run reconciliation, user communication
5. Validation gates: Go/no-go checkpoints at defined intervals with clear criteria and decision authority
6. Rollback plan: Defined procedures to revert to the legacy system if critical issues are discovered
7. Communication plan: Stakeholder notifications at each phase of the cutover

The cutover should be rehearsed at least twice (mock cutovers) with timing recorded and refined. Common failures include underestimating data migration time, insufficient validation after migration, and poor communication when issues arise.

Cross-Module and Consulting-Specific Questions

These questions assess your broader consulting capabilities beyond module-specific knowledge.

Q: How do you handle a situation where the client’s business process does not fit SAP standard functionality?

This is a fundamental consulting question. The approach should follow a clear decision hierarchy:

1. Understand the business requirement deeply. Often what appears to be a gap is actually a misunderstanding of either the business need or SAP’s capabilities.
2. Explore SAP standard configuration options. SAP is highly configurable, and many apparent gaps can be addressed through configuration, BAdIs, user exits, or enhancement points.
3. Evaluate SAP best practices. Sometimes the client’s existing process is inefficient, and SAP’s standard process is actually better. This requires diplomatic but honest consultation.
4. Custom development as a last resort. If custom development (ABAP, Fiori extensions) is truly necessary, document the business justification, assess the impact on future upgrades, and build with the principle of minimal modification.

Q: Describe a challenging integration scenario you have managed.

Interviewers want to hear about real-world complexity. Strong answers include: integration between SAP and non-SAP systems (middleware platforms like SAP Integration Suite, MuleSoft, or Dell Boomi), cross-module integration challenges (MM-FI reconciliation issues, SD-WM goods issue timing), or multi-system landscapes where master data synchronisation is critical. Focus on the problem identification, the solution design process, stakeholder management, and the outcome — including any lessons learned.

Q: How do you approach integration testing for an SAP implementation?

Integration testing validates end-to-end business processes across modules and systems. The approach includes:

• Test scenario design: Map complete business processes (e.g., procure-to-pay from requisition through payment) across all involved modules
• Test data preparation: Create realistic test data that covers standard scenarios, edge cases, and error conditions
• Interface testing: Validate all inbound and outbound interfaces with external systems
• Authorization testing: Verify that role-based access controls work correctly across processes
• Performance testing: Validate response times for critical transactions under expected user load
• Regression testing: Confirm that new configuration or developments have not broken existing functionality

A Day in the Life of an SAP Consultant

Interviewers at consulting firms often ask what you expect the day-to-day work to look like. Demonstrating realistic expectations shows maturity and readiness.

Implementation projects: Long hours during blueprint workshops and go-live periods. Significant travel (3-4 days on-site per week during active phases). Continuous requirements discussions with business users who may not understand SAP terminology. Configuration work in development systems, testing, documentation, and knowledge transfer to the client’s internal team.

Support/AMS projects: Ticket-based work resolving production issues, processing change requests, and handling periodic activities (month-end close, year-end close). Less travel, more routine, but requires deep system knowledge and the ability to diagnose issues under time pressure.

S/4HANA migration projects: Assessment of current customisations, custom code remediation, data migration planning, fit-to-standard workshops comparing current processes against S/4HANA best practices, and extensive testing. These projects combine the complexity of implementation with the constraint of existing data and processes.

Preparing for Your SAP Consultant Interview

SAP interviews reward depth over breadth. Interviewers can tell within minutes whether a candidate has genuine implementation experience or has only completed training courses. To prepare effectively:

1. Review your project experience in detail. Be ready to discuss specific configuration decisions, challenges you faced, and how you resolved them. Vague answers like “I configured the MM module” are insufficient — you need to explain which specific areas you configured and why.

2. Refresh your transaction code knowledge. Being able to reference specific T-codes (ME21N, MIGO, MIRO, VA01, VL01N, VF01, FB60, F110) demonstrates hands-on experience that book knowledge alone does not provide.

3. Understand the S/4HANA migration path. Even if you are interviewing for an ECC role, knowledge of S/4HANA changes in your module is expected. Every client is either planning or executing their S/4HANA transition.

4. Prepare implementation stories. Have 3-5 detailed stories about challenging situations from your projects — a difficult client requirement, a data migration problem, a go-live issue, an integration challenge. Structure these using the STAR method (Situation, Task, Action, Result).

For comprehensive preparation on interviewing at SAP itself as an employer, see our SAP Interview Guide.

Practice your technical explanations and scenario-based answers using the OphyAI Interview Coach, which provides AI-powered mock interviews tailored to consulting roles. During live interviews, the OphyAI Interview Copilot offers real-time assistance to help you structure your responses to complex technical questions. And to ensure your SAP consulting resume highlights the right modules, certifications, and project experience, use the OphyAI Resume Builder to create an ATS-optimized CV that speaks directly to SAP hiring managers.

OphyAI offers a free tier with 5 credits to get started, with plans starting at $9/month for Basic, $19/month for Pro, and $39/month for Premium — covering unlimited mock interviews and real-time interview support across all SAP modules and consulting scenarios.

---

Take Your Job Search Further

Interview preparation is just one piece of a successful job search. OphyAI helps you manage the full picture:

• Find relevant jobs with AI-powered search that matches your skills and experience
• Auto-generate cover letters and follow-ups tailored to each role — plus thank-you notes, LinkedIn messages, and salary negotiation letters
• Track every application in one place so you never miss a deadline or follow-up

Combined with the Interview Copilot and AI Resume Builder, OphyAI covers your entire job search from first application to first day.