SAP MM

Interview Preparation Guide

4–5 Years Experience Level
200 Questions. 100 SAP MM. 50 Scenarios Based. 50 Behaviour Based.
Also covered Cross-Interview Questions & Answers

💡 This guide is written for real interviews — not textbook recitation. Use these answers as a base, then
make them YOUR story by adding your actual project experiences, company names (where appropriate),
and your own voice.
How to Use This Guide
This document has three sections: 100 Subject/Technical questions, 50 Scenario-based questions, and 50
Behavioural questions — each with a human-toned answer and cross-questions the interviewer is likely to
follow up with.
For the cross-questions: these are marked with ⚡ and listed right below the parent question. When you
answer the main question, expect the conversation to go in the direction of those cross-questions. Be ready.
Don't memorize these answers verbatim. Read them, understand the logic, then practice saying them in
your own words. Interviewers at the 4-5 year experience level will ask you to get specific — so have 2-3 real
project examples ready to drop into any answer.
 SECTION 1: SUBJECT & TECHNICAL QUESTIONS (100
Q&A)

These questions test your core SAP MM knowledge — procurement processes, configuration, master data,
integration, and day-to-day functional understanding.

Q1. Can you walk me through the end-to-end procurement process in SAP MM?
Answer:
Sure. It starts with a Purchase Requisition — either manual or automatic through MRP. That gets converted
into a Purchase Order. Once the vendor delivers, we do a Goods Receipt using MIGO, which hits the
inventory and triggers a material document and an accounting document. Then the vendor invoice comes in
— we process that through MIRO, which does the three-way match: PO, GR, and invoice. If everything
checks out, payment happens through FI. That's the basic P2P flow.
⚡ Cross-Questions They Might Ask:
What happens if the three-way match fails in MIRO?
→ → You'll get a variance. If it's within tolerance, the system can auto-post. Beyond tolerance, the invoice
gets blocked — either price block or quantity block — and a workflow kicks off for approval or you clear it
manually.
Can a PO be created without a PR?
→ → Yes, absolutely. PR is not mandatory. But in most organizations, they enforce it through authorization
roles so there's a proper approval trail.

Q2. What are the different document types in SAP Purchase Orders and why do they matter?
Answer:
Document types like NB (standard PO), UB (stock transfer order), FO (framework order) control number
ranges, item categories allowed, and account assignment categories. They also determine which fields are
mandatory or optional. Choosing the wrong document type can mess up the whole downstream process —
like using NB for an STO would create issues at goods movement.
⚡ Cross-Questions They Might Ask:
What's the difference between a standard PO and a framework order?
→ → A framework order (FO) is basically a blanket PO — you set a validity period and a target value or
quantity, and releases happen against it without creating a new PO each time. Very common for recurring
services.

Q3. Explain the significance of the plant and storage location in SAP MM.
Answer:
Plant is the key organizational unit in MM — almost every MM transaction revolves around it. It's where
materials are produced or stored, MRP runs at the plant level, and valuation area is typically set at plant
level in most implementations. Storage location is within the plant — it's where physical stock sits. You can
have multiple storage locations under one plant and move stock between them using transfer orders or
transfer postings.
⚡ Cross-Questions They Might Ask:
Can stock exist at the plant level without a storage location?
→ → Yes, in some movement types the storage location isn't mandatory — but for most practical scenarios,
especially with WM integration, SLoc is required.
Q4. What is a Material Master and what are the key views you work with in MM?
Answer:
Material Master is the central data repository for any material. The views I most frequently work with are:
Basic Data 1 & 2 (description, base unit, material group), Purchasing (purchasing group, GR processing
time, order unit), MRP views 1-4 (planning parameters, lot sizing, safety stock), Accounting 1 (valuation
class, price control — S or V, standard or moving average), and Warehouse views if WM is active. Each
view is maintained by a different team — MM guys do purchasing views, production does MRP, finance
does accounting.
⚡ Cross-Questions They Might Ask:
What's the difference between price control S and V?
→ → S is Standard Price — fixed, variances go to a price difference account. V is Moving Average Price —
recalculates with every goods movement. Standard price is preferred for finished goods, moving average
for raw materials.
What happens if a material master doesn't have an MRP view?
→ → MRP won't plan for that material. It'll just sit there and nothing gets triggered automatically.

Q5. How does the Vendor Master work and what's the difference between general data,
company code data, and purchasing org data?
Answer:
General data is client-level — name, address, bank details, tax info. This is shared across all company
codes. Company code data is FI-specific — payment terms, reconciliation account, dunning. Purchasing org
data is what MM cares about most — currency, incoterms, order confirmation requirements, GR-based
invoice verification setting. You need all three created properly before you can raise a PO for that vendor.
⚡ Cross-Questions They Might Ask:
Can the same vendor have different payment terms for different company codes?
→ → Yes — payment terms sit at company code level, so absolutely.
What is a one-time vendor and when do you use it?
→ → It's a generic vendor master (CPD account) used for vendors you deal with rarely. Details are entered
per transaction rather than stored centrally.

Q6. What is GR/IR account and why is it important?

Answer:
GR/IR — Goods Receipt / Invoice Receipt — is a clearing account that sits between the goods receipt and
invoice posting. When you do a GR, the system debits the inventory account and credits GR/IR. When the
invoice comes in, it debits GR/IR and credits the vendor account. Ideally they net to zero. But if there's a
timing difference — GR done, invoice not yet received or vice versa — the GR/IR shows an open balance.
Month-end GR/IR reconciliation is a key task to ensure nothing is hanging.
⚡ Cross-Questions They Might Ask:
What transaction do you use to analyze GR/IR accounts?
→ → MB5S gives you the GR/IR analysis. Also F.19 for balance adjustments at period end.

Q7. Explain account determination in SAP MM — how does the system know which GL account
to hit?
Answer:
It goes through a chain: Transaction key (like BSX for inventory posting, WRX for GR/IR) → Valuation class
from the material master → Valuation grouping code (from plant) → Account modifier if applicable. All this is
configured in OBYC — the automatic account determination table. It's one of those areas where MM and FI
have to work very closely during implementation.
⚡ Cross-Questions They Might Ask:
What transaction is used to configure automatic account determination?
→ → OBYC in customizing.
What's BSX used for?
→ → BSX is the transaction key for inventory postings — stock account.

Q8. What is special stock and what types have you worked with?
Answer:
Special stock is stock that doesn't belong to your company or isn't stored in your normal inventory. Types
I've worked with: consignment stock (belongs to vendor until used — tracked under K), subcontracting stock
(material sent to vendor for processing — tracked under O), project stock (WBS-assigned, under Q), sales
order stock (under E), and customer returnable packaging. Each has its own movement types and valuation
treatment.
⚡ Cross-Questions They Might Ask:
How is consignment stock handled at month-end?
→ → Consignment liabilities report (MB54) shows outstanding consignment stock. Settlement happens via
MRKO — consignment and pipeline settlement.

Q9. What are the key movement types you've used and what do they do?
Answer:
101 — GR against PO. 102 — reversal of GR against PO. 201 — goods issue to cost center. 261 — goods
issue to production order. 301 — plant-to-plant transfer one-step. 311/312 — storage location to storage
location. 501 — GR without PO (receipt without reference). 551 — scrapping. 601 — goods issue for
delivery (SD). 701 — GI for returnable packaging. These are the ones you deal with daily. Knowing the
reversal movement type for each is equally important.
⚡ Cross-Questions They Might Ask:
What's the difference between 301 and 303/305 for plant transfers?
→ → 301 is a one-step transfer — immediate. 303 removes from sending plant, 305 places in receiving
plant — it's a two-step process with a stock in transit period.

Q10. How does subcontracting work in SAP MM?

Answer:
You create a subcontracting PO with item category L. The BOM for the finished product is maintained in the
material master or directly on the PO. You issue the components to the vendor using movement type 541 —
this creates subcontracting stock at vendor. When the vendor delivers the finished goods, you do a GR
against the subcontracting PO — movement 101 for the final product and 543 for the consumption of
components. The system calculates the value as: components issued + subcontracting charges.
⚡ Cross-Questions They Might Ask:
What happens if the vendor returns the components?
→ → You use movement type 542 to reverse the 541 — brings components back into your own stock.
How do you track components at the vendor's end?
→ → MB54 or ME2O gives you the subcontracting stock overview per vendor.
Q11. What is a Source List and why would you use it?
Answer:
Source list defines which vendors are valid sources for a material in a specific plant. It's used to restrict or
prioritize procurement sources. You can mark a source as fixed (MRP will always use that vendor) or as a
blocked source. It plays into MRP source determination — if source list is enforced in the MRP parameters,
MRP only creates PRs for valid sources. Helps in scenarios where you have preferred vendors or long-term
agreements.
⚡ Cross-Questions They Might Ask:
What transaction maintains the source list?
→ → ME01 to create, ME03 to display, ME05 for automatic generation from contracts.

Q12. Explain Purchasing Info Records — what data lives there and how does it get used?
Answer:
Info records store vendor-material combination data: vendor's price, conditions, planned delivery time,
tolerance limits, last PO price. There are four categories: standard, subcontracting, pipeline, and
consignment. When you create a PO, the system pulls data from the info record automatically — so price
and delivery time come in without manual entry. Keeping info records current is important because stale
data causes pricing issues in POs.
⚡ Cross-Questions They Might Ask:
Can an info record override a contract price?
→ → By default, contracts take priority over info records. The priority is: contract → scheduling agreement
→ info record.

Q13. What are Outline Agreements in SAP? What's the difference between a contract and a
scheduling agreement?
Answer:
Both are long-term purchase agreements. A contract (blanket or value contract) has a target quantity or
value — releases happen via release orders (POs referencing the contract). A scheduling agreement is
more tight — it's used for just-in-time deliveries with specific delivery dates and quantities in schedule lines.
MRP can directly create schedule lines against a scheduling agreement. Scheduling agreements are
common in automotive or high-volume manufacturing.
⚡ Cross-Questions They Might Ask:
What happens when a contract target quantity is exceeded?
→ → By default, the system gives a warning. You can configure it to give an error if you want hard
enforcement.
Can you convert a PR directly to a scheduling agreement delivery line?
→ → Yes, through source determination and ME59N.

Q14. What is Evaluated Receipt Settlement (ERS) and when is it useful?

Answer:
ERS is automatic invoice processing — instead of the vendor sending an invoice, the system auto-
generates the invoice based on the GR. So you just receive goods, and MRRL runs to create the invoice
document automatically using PO price and GR quantity. It reduces invoice processing work significantly
and eliminates invoice discrepancies. Works well with trusted, long-term vendors where pricing is stable and
agreed upfront.
⚡ Cross-Questions They Might Ask:
What configuration is needed to enable ERS?
→ → The vendor master must have the ERS indicator set, and the info record or contract should also have
it. The movement type and GR must also support it.

Q15. How does the release strategy work for Purchase Requisitions and Purchase Orders?
Answer:
Release strategy is basically the approval workflow. It's configured based on characteristics — like PR
value, material group, plant, purchasing group. You define release groups, classes, and strategies. A PR/PO
gets a release code assigned based on its characteristics, and approvers release it using ME54N or ME28.
Without release, the PR can't be converted to a PO. It's a key control point. I've worked on setting up multi-
level release strategies where different value bands go to different management levels.
⚡ Cross-Questions They Might Ask:
Can a PO be changed after it's been released?
→ → Yes, but if the change is significant (like value increase), the system can reset the release status and
require re-approval — this depends on change-relevant indicators in the release strategy config.

Q16. What is the difference between Goods Receipt (101) and Invoice Receipt in terms of
accounting entries?
Answer:
At Goods Receipt (101): Inventory account is debited, GR/IR account is credited. The value comes from the
PO. At Invoice Receipt (MIRO): GR/IR account is debited, Vendor account is credited. If there's a price
difference between PO and invoice, it goes to a price difference account. So the GR/IR acts as the
balancing clearing account between the two events.
⚡ Cross-Questions They Might Ask:
What if the PO is at a different price than the invoice?
→ → The delta goes to a price difference account. If the material is on standard price, it always goes to price
diff. If it's MAP, it adjusts the moving average first — price diff only if stock is insufficient.

Q17. Explain Inventory Management in SAP — what are the main types of stock you can see in
MB52 or MMBE?
Answer:
MMBE shows the full stock overview. Main types: Unrestricted use — available for normal use. Quality
inspection — goods received but under QM hold. Restricted-use. Blocked stock — usually returned or
damaged goods pending decision. GR blocked stock — provisional GR done before formal acceptance.
Consignment stock. Subcontracting stock at vendor. Transit stock for plant-to-plant transfers. Each type has
its own accounting and availability treatment.
⚡ Cross-Questions They Might Ask:
Can you sell goods that are in quality inspection stock?
→ → By default, ATP check in SD doesn't include QI stock. But there are configurations to include it in
availability checks.

Q18. What is the significance of the Valuation Class in SAP MM?

Answer:
Valuation class links the material to the GL account via automatic account determination. Different valuation
classes route postings to different GL accounts — raw materials go to one account, finished goods to
another, trading goods to another. The valuation class sits in the Accounting 1 view of the material master. If
you change the valuation class after the material has stock, it can create accounting issues — so it's
something you avoid in production.
⚡ Cross-Questions They Might Ask:
Can you change the valuation class of a material?
→ → Technically yes — using CKMVFM (material ledger) or with stock zeroed out. But it's a controlled
activity because it impacts account determination going forward.

Q19. What is split valuation in SAP MM and when would you use it?
Answer:
Split valuation allows the same material to have different valuations based on certain criteria — like origin,
grade, or batch. You define valuation types and each gets its own price. For example, imported steel vs.
domestic steel — same material number but different costs. The valuation category (like 'H' for origin) is set
in the material master. It's powerful but adds complexity, so it should only be used when genuinely needed.
⚡ Cross-Questions They Might Ask:
What's the difference between valuation category and valuation type?
→ → Valuation category is the grouping criterion (like 'H' for country of origin). Valuation type is the actual
value within that category (like 'IN' for India, 'US' for USA).

Q20. How does Physical Inventory work in SAP MM?

Answer:
Physical inventory is the process of counting actual stock and reconciling with system stock. Steps: Create
PI document (MI01 or MI31 for batch), enter count results (MI04), then post differences (MI07). The system
calculates the difference and posts a goods receipt or goods issue accordingly. You can also do cycle
counting — where materials are counted at different frequencies based on ABC classification. The PI
document blocks the material from other movements until it's posted.
⚡ Cross-Questions They Might Ask:
What is cycle counting and how is it different from annual inventory?
→ → Cycle counting assigns different count frequencies to materials based on their ABC indicator — A
materials counted monthly, B quarterly, C annually. It's a rolling approach vs. a one-time annual count.

Q21. Explain how MRP works in SAP MM — what triggers it and what does it produce?
Answer:
MRP runs at the plant level for a specific material or for all materials. Triggers can be online (MD01/MD02)
or via batch job. It reads: the net requirement (demand minus stock minus open orders), the lot sizing
procedure, lead times, and safety stock. It generates Planned Orders for in-house production and Purchase
Requisitions for external procurement. It also reschedules existing orders if needed. The MRP controller is
responsible for reviewing the results in MD06 or MD07 and converting PRs or planned orders.
⚡ Cross-Questions They Might Ask:
What's the difference between MRP type PD and VB?
→ → PD is standard MRP — based on requirements. VB is reorder point planning — doesn't look at future
demand, just monitors stock against a reorder point.
What is a planning time fence?
→ → It's a period within which MRP won't automatically reschedule or delete orders — protects the firm plan
from automatic changes.
Q22. What is Batch Management in SAP MM and what kind of projects have you used it in?
Answer:
Batch management allows tracking materials at the batch level — each batch has its own stock, status, and
characteristics. It's commonly used in pharma, chemicals, food — anywhere traceability is critical. Each
batch has a batch number, and you can define shelf life, expiry dates, classification data. GR creates a new
batch or references an existing one. Goods issues then pick from specific batches — either manually or via
batch determination using FIFO, FEFO, or custom sort criteria.
⚡ Cross-Questions They Might Ask:
What is FEFO and where is it configured?
→ → First Expired First Out — the system picks batches with the earliest expiry date first. Configured via
batch search strategy in MBC1 with shelf life sort.

Q23. What is the role of the Purchasing Group in SAP?

Answer:
Purchasing group is basically the buyer or buying team responsible for a material or category. It's a key
organizational element in purchasing documents and drives reporting — you can pull all POs by purchasing
group. It also feeds into release strategies and authorization checks. Each buyer or buyer team is assigned
a purchasing group code, and that links them to their materials and vendors.
⚡ Cross-Questions They Might Ask:
Can you change the purchasing group on a PO after approval?
→ → It's a change-relevant field — changing it might reset the release status depending on config.

Q24. What is the difference between a standard purchase order item and a blanket PO item?
Answer:
A standard PO item has a specific material, quantity, and unit price. A blanket PO item (item category B) is
for items not managed in material master — things like office supplies or maintenance items. There's no
material number, just a short text, and you set a value limit and validity period. Purchases draw against the
value limit. No GR required — invoice directly references the PO. It's simpler and good for low-value, high-
frequency purchases.
⚡ Cross-Questions They Might Ask:
What account assignment category is typically used with item category B?
→ → Usually U (unknown) at PO creation, with the actual account assignment determined at invoice time.

Q25. Explain the GR-based invoice verification setting — what does it do?
Answer:
When GR-based IV is set in the vendor master (or PO), the MIRO matching works at the GR document level
rather than the PO level. This means you can only invoice what has been received, and each GR line is
matched separately. It prevents invoicing for goods not yet received, which is a key internal control. Most
organizations activate this for regular material POs.
⚡ Cross-Questions They Might Ask:
What happens when GR-based IV is NOT set?
→ → You can invoice against the full PO quantity even before receiving goods. This creates risk of paying
before receiving.

Q26. What are tolerance limits in invoice verification?

Answer:
Tolerance limits define the acceptable difference between the PO price/quantity and the invoice. You
configure upper and lower limits — both percentage and absolute value. If the variance is within tolerance,
the invoice posts cleanly. If it's beyond tolerance, the invoice gets blocked. There are different tolerance
keys for different types of variances — BD for form small difference, AP for quantity variance, etc. These are
configured in OMR6.
⚡ Cross-Questions They Might Ask:
What's the difference between a price block and a quantity block on an invoice?
→ → Price block is when the price per unit differs beyond tolerance. Quantity block is when the invoiced
quantity exceeds GR quantity. Both block payment until cleared.

Q27. What is the account assignment category and how does it affect MM transactions?
Answer:
Account assignment category determines where the cost goes — which cost center, WBS, asset, sales
order etc. Common ones: K for cost center, P for project (WBS), A for asset, F for production order. It also
affects whether a GR is required and whether stock is managed or not — cost center purchases (non-stock
items) usually go directly to expense without creating stock. It's configured in the item category and account
assignment category combination.
⚡ Cross-Questions They Might Ask:
For a PO with cost center assignment, does a GR create stock?
→ → No — it's a direct consumption posting. Stock is not created; the expense goes directly to the cost
center.

Q28. How do you handle return to vendor in SAP MM?

Answer:
For returns, you have a couple of options. If the material hasn't been consumed, you can do a return delivery
in MIGO using movement type 122 (reversal of GR) or use the return indicator in MIRO. If it's a complete
return, you can create a return PO (with the return indicator on the PO item) — movement type 161 is used,
which is a goods issue to vendor. The system reverses the accounting from the original GR.
⚡ Cross-Questions They Might Ask:
How does a credit memo differ from a return delivery?
→ → Return delivery is a physical return of goods — inventory goes back to vendor. Credit memo is a
financial correction — no physical movement, just adjusts the invoice value.

Q29. What is a Delivery Schedule in a Scheduling Agreement?

Answer:
Delivery schedule lines are the specific dates and quantities communicated to the vendor under a
scheduling agreement. They can be firm (JIT) lines or forecast lines. Forecast lines are farther out and less
binding — the vendor plans based on these. Firm lines are commitments. MRP can automatically generate
schedule lines, or planners create them manually. The vendor receives these as delivery instructions.
⚡ Cross-Questions They Might Ask:
What's the difference between a scheduling agreement release and a delivery schedule?
→ → The delivery schedule IS the release in most cases. Some scheduling agreements use separate
release documents — SA release types.

Q30. What is the significance of the MPN (Manufacturer Part Number) in SAP MM?
Answer:
MPN allows you to cross-reference the internal material number with the manufacturer's own part number.
This is useful when the same physical item is supplied by multiple vendors with different part numbers, but
you have one internal material number. It helps in procurement — POs can print the manufacturer's part
number — and in quality management. The MPN profile is set up in the material master.
⚡ Cross-Questions They Might Ask:
How does the system link an internal material number to multiple MPNs?
→ → Through the MPN material master and the MPN profile — the system links the internal material to
multiple manufacturer materials.

Q31. What key transactions do you use for day-to-day MM work?

Answer:
ME21N/ME22N/ME23N — create, change, display PO. MIGO — goods movements. MIRO — invoice
verification. ME51N/ME52N — PR create/change. MB52 — warehouse stocks. MMBE — stock overview.
MB51 — material document list. ME2M/ME2N — PO lists. MD04 — stock requirements list. MK01/XK01 —
vendor creation. MM01 — material creation. MB5B — stock on posting date. These are the daily
workhorses.
⚡ Cross-Questions They Might Ask:
How do you find all goods receipts for a specific PO?
→ → In MIGO display mode, you can see all GR documents. Or use MB51 with movement type 101 and the
PO number as a filter.

Q32. How does the Goods Issue process work in SAP MM?
Answer:
Goods issue reduces stock from inventory and creates an accounting document. Common GI scenarios:
goods issue to cost center (201), to production order (261), for a sales order delivery (601 via SD). In MIGO,
you select goods issue as the transaction type, choose the reference (cost center, order, etc.), enter the
material, quantity, and storage location, then post. The system debits the consumption account and credits
inventory.
⚡ Cross-Questions They Might Ask:
What happens to MAP (moving average price) when you do a goods issue?
→ → MAP doesn't change with goods issues — only goods receipts and invoice postings affect the moving
average.

Q33. Explain the concept of Inventory Valuation — Standard Price vs Moving Average Price.
Answer:
Standard price (S) is fixed — set by finance, usually through a standard cost estimate. Any GR or transfer
happens at this fixed price; differences go to a price difference account. Moving average price (V) changes
with every goods receipt — the system recalculates the average based on the new receipt value. Standard
price is better for manufactured goods where cost variance analysis matters. MAP is better for purchased
materials where market prices fluctuate.
⚡ Cross-Questions They Might Ask:
Can you switch from MAP to Standard price for a material that has stock?
→ → Yes, through the material price change (MR21) transaction. But you need to carefully handle the
revaluation impact.
Q34. What is the difference between MIGO and MB1A/MB1B/MB1C?
Answer:
MIGO is the modern, unified goods movement transaction — handles GR, GI, transfers, reversals, all in one
place. It's the standard in current SAP versions. MB1A is goods issue, MB1B is transfer posting, MB1C is
other goods receipts — these are the older individual transactions. In most modern implementations, MIGO
covers everything. But you still see MB1A/MB1B in older systems or in automation scripts.
⚡ Cross-Questions They Might Ask:
Is MIGO there any functional difference between and the older MB transactions?
→ → Functionally they produce the same result. MIGO has a better UI and more flexibility. Some interfaces
and BAPIs still use the older function modules underneath.

Q35. What are the key MM configurations you've been involved in during implementation?
Answer:
I've worked on defining plant structures, storage locations, purchasing organizations. Setting up number
ranges for POs, PRs, material documents. Configuring movement types (though standard ones are mostly
used, sometimes you copy and modify). Setting up tolerance limits for invoice verification. Release strategy
for POs and PRs. Account determination in OBYC. Info record and contract setup. Batch management
configuration — including batch status management and shelf life. Message output for POs.
⚡ Cross-Questions They Might Ask:
How do you configure output (message) for Purchase Orders?
→ → Through message determination — condition technique. Define output types (NEU for PO), access
sequences, and condition records. PO printout or email is triggered based on these conditions.

Q36. What is the invoice blocking reason and how are blocked invoices managed?
Answer:
When an invoice fails tolerance checks, it gets blocked with a blocking reason — R for manual, B for amount
difference, D for date variance, etc. Blocked invoices sit in MRBR (Release Blocked Invoices) for review.
The accounts payable team investigates — either contacts the vendor, adjusts the GR, or manually
overrides if justified. Clearing the block releases the invoice for payment. It's a key control process.
⚡ Cross-Questions They Might Ask:
Can you do a partial payment on a blocked invoice?
→ → Not from the MM side directly — the block in MIRO prevents payment. But in some cases, FI can do a
manual payment with special handling.

Q37. How does the batch search strategy work in SAP?

Answer:
Batch search strategy determines which batch gets selected when you do a goods issue. You define a
strategy type, sort criteria (like FEFO, FIFO), and access sequence. The strategy is assigned to the
plant/material or movement type level. When you post a goods issue, if auto batch selection is active, the
system runs through the strategy, evaluates available batches based on the sort criteria, and selects the
appropriate one. You can also use batch where-used list for traceability.
⚡ Cross-Questions They Might Ask:
What's the transaction to configure batch determination?
→ → MBC1 for creating batch search strategies. Also need to check the plant settings for batch
management.
Q38. What is a Service PO in SAP MM and how does it differ from a material PO?
Answer:
Service POs use item category D. Instead of a material, you have service lines with service numbers or free
text. There's no material master involved — just service master records or short descriptions with unit price
and quantity. Instead of a GR, you post a Service Entry Sheet (ML81N) — this is the equivalent of accepting
the service. The entry sheet is approved, and then MIRO references it for payment. No stock is created.
⚡ Cross-Questions They Might Ask:
Is a GR created for a service PO?
→ → No — instead, a Service Entry Sheet is created and accepted. This is the equivalent of confirming
services received.

Q39. What is the role of the MRP controller in SAP MM?

Answer:
The MRP controller is responsible for a set of materials and manages their planning results. In MD06 or
MD07, they review exception messages — like rescheduling, order proposals, stock below safety stock.
They convert planned orders to PRs, or PRs to POs, work with production planning on orders. Basically
they're the bridge between automatic planning and manual decision-making. The MRP controller code is
maintained in the material master MRP 1 view.
⚡ Cross-Questions They Might Ask:
What are exception messages in MRP and what do they indicate?
→ → Exception messages tell the planner something needs attention — like 'Reschedule In' means an
existing order should be pulled earlier, 'Reschedule Out' means push it later, 'Cancel Process' means
order can be deleted due to no requirement.

Q40. Explain the concept of quota arrangements in SAP MM.

Answer:
Quota arrangement is a way to split procurement of a material across multiple vendors based on a
percentage. For example, 60% from Vendor A, 40% from Vendor B. The system automatically determines
the source based on quota values when creating a PR or PO. It's useful when you have multi-sourcing
strategies or want to spread risk. The quota is maintained in MEQ1 and considered during source
determination.
⚡ Cross-Questions They Might Ask:
What's the priority order for source determination in MRP?
→ → Source list (fixed) → Quota arrangement → Other sources in the source list → Info records → Outline
agreements.

Q41. How does MM integrate with FI (Finance) in SAP?

Answer:
Integration is real-time and automatic. Every goods movement in MM creates an FI document — stock
accounts, GR/IR, consumption accounts are all posted automatically through account determination. Invoice
receipts (MIRO) post vendor liabilities. Payment is done in FI/AP. The valuation area (plant) maps to a
company code. Material ledger (if active) tracks actual costs. The key integration points are account
determination (OBYC) and the financial posting documents created with every MM movement.
⚡ Cross-Questions They Might Ask:
What document types are created in FI when a GR is posted?
→ → A WE material document in MM and a corresponding FI document (typically document type WE) with
the accounting entries.
Q42. How does SAP MM integrate with SD (Sales and Distribution)?
Answer:
The main integration is around stock and availability. When SD creates a sales order, it checks ATP
(Available-to-Promise) which checks MM stock. Goods issue for delivery (movement type 601) is triggered
from SD's VL02N delivery posting — this reduces inventory. Material master data and plant data are shared.
Also, trading goods procurement can be triggered by sales order — account assignment category E creates
sales order stock. Stock transfer orders also link MM and SD when one plant sells to another.
⚡ Cross-Questions They Might Ask:
What is account assignment category E and when is it used?
→ → Category E is for sales order stock. Goods received go directly to a sales order — they're reserved for
that order and not available for other purposes.

Q43. How does SAP MM integrate with PP (Production Planning)?

Answer:
PP drives component requirements to MM through production orders and MRP. When a production order is
created, it generates component reservations, which reduce available stock in MD04. MM handles the
goods issue of components to production orders (movement 261) and the goods receipt of finished products
(movement 101 against production order). MRP is the central coordination point — it looks at PP demands
and creates procurement proposals in MM.
⚡ Cross-Questions They Might Ask:
What is a reservation in MM and how is it created by PP?
→ → A reservation is a commitment of stock for a specific purpose — production order, cost center, project.
It reduces available stock in MRP planning but doesn't physically move stock until GI is done.

Q44. What is Warehouse Management (WM) and how does it relate to MM?
Answer:
MM handles inventory at storage location level. WM goes deeper — it manages stock at bin/rack level within
a warehouse. MM creates a transfer requirement, WM converts it into a transfer order for physical
movement within the warehouse. They're linked through the plant-storage location to warehouse number-
storage type mapping. In modern SAP, Extended Warehouse Management (EWM) is the more advanced
version — it handles complex warehouse processes like labor management, yard management, slotting.
⚡ Cross-Questions They Might Ask:
What is a transfer requirement in WM?
→ → A transfer requirement is the demand to move goods within the warehouse — it's the link between MM
(IM) movements and WM operations. It gets converted to a transfer order for the physical movement.

Q45. What is the Material Ledger and how does it differ from standard inventory accounting?
Answer:
Material Ledger tracks actual costs for materials — standard accounting only captures standard or MAP
value. Material Ledger does actual costing — it collects all price differences, exchange rate differences, and
overhead during the period. At period-end, it calculates the actual cost and can revalue inventory and cost of
goods sold. It's mandatory with S/4HANA. The main benefit is knowing the true actual cost of materials —
essential for accurate profitability analysis.
⚡ Cross-Questions They Might Ask:
Is Material Ledger mandatory in S/4HANA?
 → → Yes — in S/4HANA, Material Ledger is activated by default and cannot be deactivated. Actual costing
is optional.

Q46. What's your experience with SAP S/4HANA MM — how is it different from ECC?
Answer:
The biggest changes: Material Ledger is mandatory in S/4HANA. The MRP Live functionality (MD01N) is
much faster. Simplified data model — some aggregate tables are replaced by real-time calculations from
line items. Fiori apps replace many old transactions for end users — so the GR process might be done
through a Fiori tile rather than MIGO. Also, some old customizing transactions are deprecated. The
underlying logic is the same, but performance is significantly better especially for MRP runs and large
reports.
⚡ Cross-Questions They Might Ask:
What is MRP Live in S/4HANA?
→ → MRP Live uses the HANA in-memory database for faster MRP runs — it can plan the entire plant in
minutes rather than hours. It also offers better exception handling and parallel processing.

Q47. How do you handle a scenario where a vendor delivers more than the PO quantity?
Answer:
You have a few options. If the over-delivery is within the tolerance defined in the PO (over-delivery tolerance
% in PO item or info record), the system accepts it. If beyond tolerance, it'll give a warning or error. You can
post it with movement type 101 and manually accept it, then handle the excess — either return it (122) or
create a supplementary PO line. The correct approach depends on the business scenario — some
organizations have strict policies on over-delivery.
⚡ Cross-Questions They Might Ask:
Where is the over-delivery tolerance configured?
→ → In the PO item (Delivery tab) or pulled from the purchasing info record. It can also be set at the
material master level.

Q48. What is consignment processing in SAP MM and how does it work end-to-end?
Answer:
In consignment, vendor stock sits at your premises but belongs to the vendor until you consume it. Process:
Create a consignment info record with consignment price. Create a consignment PO (info category:
consignment). GR against the consignment PO — stock goes to consignment stock (special stock K),
valued at zero on your books. When you consume it (via goods issue), that's when liability is recognized.
Settlement runs via MRKO — the system creates an FI document for the consumed quantity at the
consignment price. It's a great cash flow tool.
⚡ Cross-Questions They Might Ask:
What movement type is used when consuming consignment stock?
→ → Movement type 201 (GI to cost center) or 261 (GI to production order) from consignment stock — you
just need to specify the special stock indicator K.

Q49. What are the key differences between a one-step and two-step stock transfer in SAP?
Answer:
One-step (MT 301 for plant transfer, 311 for SLoc transfer): Stock leaves the source and arrives at the
destination simultaneously. Simple, no interim stock. Two-step: First movement (303 for STO, 313 for SLoc)
removes stock from source — it goes into 'in-transit' or 'transfer' stock. Second movement (305 or 315)
receives at the destination. Two-step is better when there's physical transit time — you want to track that the
goods are in transit without showing them in either location's unrestricted stock.
⚡ Cross-Questions They Might Ask:
For a cross-company stock transfer, which process is used?
→ → Cross-company STOs typically involve SD — the selling plant creates a delivery, and the buying plant
does a GR against the STO. This creates both MM and billing documents.

Q50. How do you create a vendor (creditor) in SAP — what are all the steps?
Answer:
In S/4HANA, it's through the Business Partner (BP) transaction — you create BP with role FLVN00 (vendor
general) and FLVN01 (FI vendor). The vendor account group determines which fields are mandatory and the
number range. I always check that the reconciliation account, payment terms, and GR-based IV indicator
are set correctly before using the vendor.
⚡ Cross-Questions They Might Ask:
What is the account group in vendor master and what does it control?
→ → Account group controls: number range (internal vs external), field selection (required, optional, display,
hidden), and the type of vendor (one-time, regular, etc.).

Q51. What is a Purchase Requisition and who typically creates it?

Answer:
A PR is an internal request to procure materials or services. It can be created manually (ME51N) by any
user with the right authorization, or automatically by MRP. The PR doesn't go to the vendor — it's an internal
document. Once approved (released), it gets converted to a PO.

Q52. What is the difference between ME21N and ME59N?

Answer:
ME21N is manual PO creation. ME59N automatically converts approved purchase requisitions into POs — it
applies source determination and creates POs in batch. ME59N is heavily used by buyers to process the
MRP output.

Q53. What are the item categories in SAP MM Purchase Orders?

Answer:
Blank (standard material), B (limit/blanket — no material master, value limit), D (service), K (consignment), L
(subcontracting), S (third-party). Each category drives different procurement and GR behaviour.

Q54. What is a Delivery Completed indicator on a PO and what does it do?

Answer:
When set, it tells the system that no more deliveries are expected against that PO item, even if the ordered
quantity hasn't been fully received. It closes the item for MRP and GR purposes. Useful when you've
decided to close a partial PO item.

Q55. What is the Final Invoice indicator in MIRO?

Answer:
It tells the system that this is the last invoice expected for the PO item. After posting, the PO item is marked
complete from an invoicing perspective — no more invoices will be expected or processed against it.

Q56. How do you handle expired batches in SAP MM?

Answer:
Batch status management can automatically block batches past their expiry date if 'next inspection date' or
'shelf life expiry' is used. Expired batches move to restricted status. A batch job can be configured to
automatically update batch statuses based on dates.

Q57. What is the minimum shelf life and remaining shelf life in SAP?
Answer:
Minimum remaining shelf life is the minimum time a material must have left on its expiry date when goods
are received — configured in the material master or PO. Remaining shelf life affects FEFO batch
determination. If a batch has less than the minimum remaining shelf life, it may be rejected at GR.

Q58. What is the purpose of the Goods Receipt blocked stock (movement type 103)?
Answer:
Movement 103 posts goods to GR blocked stock — a provisional receipt where goods are received but not
yet accepted. No accounting document is created. Once inspected and accepted, movement 105 transfers
to unrestricted stock. Used when you want to inspect goods before formal acceptance.

Q59. What is MRBR and when is it used?

Answer:
MRBR is Release Blocked Invoices. It's used to review and release invoices that were blocked in MIRO due
to tolerance violations. The AP team reviews the blocking reason, investigates (contact vendor, check GR),
and manually releases after approval.

Q60. What are the different lot-sizing procedures in SAP MRP?

Answer:
EX (exact/lot-for-lot), FX (fixed lot size), HB (replenish to maximum stock level), MB (monthly requirements),
WB (weekly), TB (daily), PQ (periodic lot sizing). Each has different planning behavior and is chosen based
on procurement patterns and cost trade-offs.

Q61. What is the planning horizon in MRP?

Answer:
Planning horizon is how far into the future MRP looks when planning. It determines the time fence for which
planned orders are created. Set at the plant/MRP group level. Shorter horizon = fewer planned orders but
risk of not procuring in time. Needs to be at least as long as the longest procurement lead time.

Q62. What is the difference between the plant-level MRP run and the individual material MRP
run?
Answer:
Plant-level run (MD01) plans all materials with the selected planning file entries — used for regular planning
runs. Individual material run (MD02/MD03) is for ad-hoc planning of a specific material, or when you want to
plan without affecting the whole plant run.

Q63. What is the significance of the MRP type in the material master?
Answer:
MRP type controls whether and how MRP plans for that material. PD = standard MRP. ND = no planning.
VB = reorder point. MF = make-to-order. Choosing the wrong MRP type is a common cause of planning
failures.

Q64. What is a stock requirements list (MD04) and how is it different from MB52?
Answer:
MD04 shows the dynamic planning picture — current stock, all requirements (reservations, sales orders),
and all receipts (open POs, planned orders) over time. MB52 is a static snapshot of current stock by storage
location. MD04 is what planners live in; MB52 is for stock lookup.

Q65. What is price determination in SAP MM — how does the system find the price for a PO?
Answer:
Price determination uses the condition technique — condition types, access sequences, and condition
records. For a PO, the system searches: manual price → info record → contract → last PO. The access
sequence in the pricing procedure determines the search order. This is similar to SD pricing but from the
procurement side.

Q66. What is a statistical condition in MM pricing?

Answer:
A statistical condition in the pricing schema doesn't affect the net price — it's displayed for information
purposes only (like suggested retail price or a reference price). It's flagged as statistical in the condition type
configuration.

Q67. What is the invoice reduction function in MIRO?

Answer:
Invoice reduction (available via the 'Reduce' button in MIRO) allows you to accept a lower amount than
invoiced — the system posts the accepted amount and creates a credit memo for the difference
automatically. Useful when you partially accept an over-invoiced amount without requesting a new invoice
from the vendor.

Q68. What is a subsequent debit/credit in MIRO?

Answer:
Subsequent debit: vendor charges extra on top of an already-posted invoice (like a price adjustment).
Subsequent credit: vendor gives back money (like a rebate or over-charge correction). Both are posted in
MIRO with the appropriate transaction type — they affect inventory valuation if stock is still available.

Q69. What is the significance of the posting date in MIGO?

Answer:
The posting date determines which fiscal period the document is posted in. If you post with an incorrect
date, it goes to the wrong period — affecting monthly reports and balance sheet. Always verify the posting
date, especially near period-end. If a period is closed, you'll get an error and need to use the next open
period.

Q70. How does SAP handle taxes in MM invoice verification?

Answer:
Tax codes are entered in MIRO — either manually or defaulted from the PO. The tax calculation is based on
the condition technique (tax procedure TAXINN for India, TAXUS for US, etc.). The tax amount is calculated
automatically. FI handles the tax posting — MM just feeds the values.

Q71. What is the vendor evaluation module in SAP MM?

Answer:
Vendor Evaluation (ME61/ME62) tracks vendor performance across criteria: quality, delivery, price, and
service. Each criterion has subcriteria. The overall score helps in sourcing decisions and contract renewals.
It integrates with quality notifications, GR delivery dates, and pricing history.

Q72. What is a material group and how is it used in MM?

Answer:
Material group categorizes materials that are similar in nature (e.g., raw metals, office supplies). It's used in
purchasing for grouping, reporting, authorization, and release strategy. If a material master doesn't exist,
material group on the PO is even more important for account determination.

Q73. What is the difference between a direct GR and a planned GR?

Answer:
In most cases, GR just happens when goods arrive — there's no separate 'planning' step in standard MM.
However, with inbound delivery (Delivery-based GR), an inbound delivery is created first (via EDI/ASN or
manually in VL31N), and the GR is posted against the inbound delivery. This allows pre-processing before
physical receipt.

Q74. What are the implications of posting a GR in a closed period?

Answer:
You'll get an error — the period is closed and no FI document can be created. Solution: Either open the
previous period (OB52 — FI team), or post with the current period's date. If goods actually arrived in the
closed period, the accounting impact goes into the current period instead — a common month-end issue.

Q75. What is a material document and a financial document in MM — how are they linked?
Answer:
A material document (MBLNR) is created by every goods movement — it records what moved, when,
quantity, and movement type. A financial/accounting document (BELNR) is the parallel posting in FI. They're
linked — from the material document you can navigate to the FI document via the document flow. Not every
material document creates an FI document (e.g., STO within same company code in some configs might
not).
Q76. What is the use of the text field in a Purchase Order?
Answer:
PO texts include header text, item text, and delivery text. Header text is visible to the vendor and can include
instructions. Item text can include technical specifications or handling notes. Delivery text goes on the
delivery note. They're printed on output messages to vendors. Text can be pulled from the info record or
contract automatically.

Q77. What is the confirmation control key in SAP purchasing?

Answer:
Confirmation control key determines what kind of confirmation the vendor needs to send: order
acknowledgment, ASN (inbound delivery), or shipping notification. If set, the system can track whether the
vendor confirmed the order. Useful for critical orders where you need vendor acknowledgment before
proceeding.

Q78. What is ME2L and ME2M used for?

Answer:
ME2L shows all POs by vendor — useful for analyzing spend by supplier. ME2M shows POs by material —
useful for checking procurement history for a specific material. Both are flexible reporting transactions with
selection criteria and ALV output.

Q79. What is the GR non-valuated indicator and when is it used?

Answer:
When GR non-valuated is set (usually for free goods or certain account assignments), the goods receipt
doesn't create a financial document — no inventory value is posted. This is used when cost is managed at
the invoice level, not the receipt level. Common for certain project-based or grant-funded procurement.

Q80. What is the role of the Accounting 2 view in the material master?
Answer:
Accounting 2 contains tax data — tax indicator for material valuation (relevant for tax procedures),
LIFO/FIFO data if material ledger valuation methods are used. It's usually maintained by the finance team
and is relevant for tax and valuation reporting.

Q81. What is split invoice posting and when is it needed?

Answer:
When an invoice covers multiple POs or multiple GR documents, you post it in a single MIRO entry
referencing multiple purchase orders or delivery notes. The system splits the payable across the respective
liability lines. This is common when a vendor sends a consolidated monthly invoice.

Q82. What is a message record in SAP purchasing and how do you troubleshoot PO output
failures?
Answer:
Message records store output (printout, email, EDI) for purchasing documents. In ME23N, the messages tab
shows all message records and their status. If a PO isn't being sent, check here — a processing status of
'Error' with an error message tells you what's wrong. Common issues: missing printer, wrong partner
function, EDI config issue.
Q83. What is the difference between BAPI and IDOC for MM integration?
Answer:
BAPI (Business Application Programming Interface) is a synchronous function module call — used for real-
time data exchange. IDoc (Intermediate Document) is asynchronous — used for EDI and batch interfaces.
BAPI is used when immediate confirmation is needed (e.g., creating a PO via a procurement portal). IDoc is
used for EDI messages like purchase order output, GR confirmation, or vendor invoice receipt.

Q84. How is the number range for POs configured?

Answer:
In OMRN (or via customizing): define a number range interval for the document type. Internal numbering:
system assigns automatically. External numbering: user or interface provides the number. Typically POs use
internal numbering (range 45XXXXXXXX for document type NB). Year-dependent number ranges can also
be configured.

Q85. What is the purpose of the Quality Management (QM) info record?
Answer:
The QM info record links a vendor-material combination to quality management parameters — like whether
QM is active for this procurement, the certificate type required, QA agreements. It controls whether a quality
inspection lot is created on GR and whether the vendor needs to provide a Certificate of Analysis.

Q86. What is the difference between a partial GR and a complete GR?

Answer:
Partial GR: only some of the ordered quantity is received — PO remains open for the remaining quantity.
Complete GR: all ordered quantity received — but Delivery Completed indicator must be set manually if you
want to close the PO. If final invoice indicator is also set, the PO is fully closed from both GR and invoice
perspectives.

Q87. What is a purchase order confirmation and how is it tracked in SAP?

Answer:
Order confirmation is the vendor's acknowledgment that they received and accepted the PO. In SAP, the
confirmation is entered in ME22N (change PO) under the confirmation tab, or via EDI (ORDRSP IDoc). The
confirmation control key on the PO item must be set. You can report on unconfirmed orders — useful for
tracking vendor responsiveness.

Q88. What is a free goods receipt (movement type 511) in SAP?

Answer:
Movement 511 is used when goods are received without reference to a PO — for free samples, gifts, or
donations. No PO or obligation exists. The goods are received into stock and valued at a manually entered
price or zero. It creates a material document but no vendor liability.

Q89. What is a scheduling agreement type and how does it differ from contract types?
Answer:
Scheduling agreement types (like LP for standard, LPA for release documentation) control the release
mechanism. LP creates schedule lines directly. LPA uses separate release documents (forecast delivery
schedule + JIT delivery schedule). Contracts (MK for quantity, WK for value) don't have schedule lines —
they release via release orders (POs) against them. Different procurement strategies need different
agreement types.

Q90. What is the use of ME2A transaction?

Answer:
ME2A is used to monitor purchase order confirmations — it lists all PO items that have a confirmation
control key set and shows whether the vendor has sent a confirmation. Useful for procurement teams to
follow up on unconfirmed orders.

Q91. How does the system handle foreign currency POs — what exchange rate is used?
Answer:
The exchange rate used at GR time is the exchange rate from the OB08 table (maintained by FI) for the rate
type specified on the PO (usually M — monthly average rate). The PO shows the price in the order currency;
the GR valuation converts to local currency at the applicable rate. Exchange rate differences can arise
between PO creation and GR posting.

Q92. What is inbound delivery in SAP MM and how does it differ from a standard GR?
Answer:
Inbound delivery (VL31N or via DESADV IDoc) is created before goods physically arrive — based on
vendor's ASN. It allows pre-planning: putaway instructions, unloading point, expected time of arrival. The
actual GR is posted against the inbound delivery, not the PO directly. Inbound delivery is part of the Delivery
Monitoring (transportation) capability.

Q93. What is the goods receipt processing time on the PO and where does it come from?
Answer:
GR processing time is the number of days needed after GR to make the material available (quality check,
putaway, etc.). It's maintained in the purchasing view of the material master and used by MRP when
calculating net requirements — MRP accounts for this time when scheduling replenishment.

Q94. What are account assignment categories K and P used for?

Answer:
K is cost center — goods are consumed to a cost center, no stock created. P is project/WBS element —
goods consumed to a project (WBS), no inventory. Both result in direct expense posting at GR. The
difference: K routes cost to internal cost centers (OH accounts), P routes to project accounting (CO-PS).

Q95. What is the LSMW tool and have you used it for MM?
Answer:
LSMW (Legacy System Migration Workbench) is SAP's tool for mass data loading. I've used it for bulk
vendor master creation, material master extension, and source list uploads during implementations. You
record the transaction, create the mapping, import data from a spreadsheet, and run in simulation mode first
to check errors before actual posting.
Q96. What is a delivery tolerance in the Purchase Order and how is it configured?
Answer:
Delivery tolerance has an under-delivery % and an over-delivery %. Under-delivery: if vendor delivers less
than the ordered quantity minus the tolerance, it's still accepted (PO remains open). Over-delivery: how
much more than ordered quantity the system accepts before giving an error. Configured in the PO item
(Delivery tab) or pulled from the info record. The 'unlimited over-delivery' flag removes the upper limit check.

Q97. What is the purpose of the movement type modifier?

Answer:
Movement type modifier allows you to create movement type variants — based on the same base
movement type but with different account determination or other properties. For example, you might have
two versions of 201 (GI to cost center) that post to different accounts based on the business scenario. It's a
way to differentiate similar movements without creating entirely new movement types.

Q98. What is MB5L and when do you use it?

Answer:
MB5L is the stock valuation report — it shows total stock value at a selected date (posting date). You can
compare book value vs. actual value, useful for inventory valuation verification and as input to balance sheet
preparation. Often run at period-end by the finance team in coordination with MM.

Q99. What is automatic account determination testing — how do you test it?
Answer:
Use OMWB (Simulate MM Account Determination) — you can test which GL accounts will be determined for
a given combination of plant, movement type, transaction key, and valuation class. This is your dry-run
before going live — avoids surprises in production when goods movements post to wrong accounts.
 SECTION 2: SCENARIO-BASED QUESTIONS (50 Q&A)

These questions test how you apply SAP MM knowledge to real business situations. Interviewers at 4-5
years expect you to think through the problem, not just name a transaction. Walk them through your
reasoning.

Q1. Your MRP run is generating planned orders, but the PR conversion isn't happening.
Purchasing is complaining they're not getting anything to process. What would you check?
Answer:
First I'd look at the material's MRP type — if it's set to 'No MRP', that's your answer. Then I'd check if the
plant has the correct MRP area. Look at the PR creation indicator in the MRP group or plant parameters —
there's a setting that controls whether MRP creates PRs directly or just planned orders. Also check if there's
a quota arrangement issue or a source list with a fixed source that's blocking PR creation. MD04 (stock
requirements list) would show me what MRP actually produced.
⚡ Cross-Questions They Might Ask:
What's the difference between a planned order and a purchase requisition in MRP output?
→ → Planned orders are internal procurement proposals — for manufactured items. PRs are for external
procurement. The MRP type and procurement type in the material master determine which one gets
created.

Q2. Finance is complaining that the GR/IR account has a large unexplained balance at month
end. How would you investigate and resolve it?
Answer:
I'd start with MB5S — the GR/IR analysis report. It shows all open GR/IR items — GRs without matching
invoices and invoices without matching GRs. Common causes: vendor invoice not yet received (timing
difference), GR posted but invoice not processed, quantity mismatch between GR and invoice. For genuine
timing differences, F.19 can create a provision posting. For old items that are genuinely unresolvable, I'd
work with FI to write them off appropriately after investigation.
⚡ Cross-Questions They Might Ask:
Can you reverse a GR that's already been invoiced?
→ → Yes, but MIRO must be reversed first (MR8M or MIRO cancel), then the GR can be reversed with
MIGO reversal (movement 102). Order matters — you can't reverse GR if invoice is still active against it.

Q3. A purchase order was created with the wrong vendor. It's been released and some
deliveries have started. How do you handle this?
Answer:
Tricky one — you can't change the vendor on an open PO in SAP. The approach depends on the stage. If
partial deliveries are done, I'd work with procurement to close out what's been received, then create a new
PO with the correct vendor. The existing receipts stand with the wrong vendor — you'd need to do a credit
memo or return to adjust. For the amounts already invoiced, FI would need to do a vendor account transfer.
It's a mess — which is why vendor validation before release is critical. I'd also investigate how this slipped
past the release step.
⚡ Cross-Questions They Might Ask:
What controls prevent a wrong vendor from being selected on a PO?
→ → Source list with approved vendors, partner determination, and purchasing organization authorization.
Also, vendor evaluation and approved vendor list processes outside SAP.
Q4. A vendor sends an invoice for 1,000 units but you only received 900. MIRO is blocking the
invoice. What are the options?
Answer:
The invoice is quantity-blocked. Options: First confirm if remaining 100 units are still expected — if yes, wait
for the 2nd delivery, then process the remaining invoice quantity. If the 100 units are not coming, create a
credit memo request or contact vendor for a corrected invoice. If the business needs to pay the full 1,000
quickly, someone with authority can manually release the block in MRBR with a reason — but this should be
controlled. I'd document everything and raise a query to the vendor formally.
⚡ Cross-Questions They Might Ask:
Can you do a partial invoice posting in MIRO?
→ → Yes — you can change the quantity in MIRO to match what was received (900) and post partially. The
remaining 100 can be invoiced later when goods arrive.

Q5. Production is stopped because a critical raw material is showing zero stock in the system,
but the warehouse says they have stock physically. What do you do?
Answer:
Stock discrepancy — always stressful. Immediate action: Check MB52/MMBE to understand the stock
situation in detail — is it in a different storage location, different stock type (maybe quality inspection), or
plant? If the physical stock is genuine, initiate an emergency physical inventory count (MI01) to reconcile.
Short-term, work with warehouse to issue stock manually with proper documentation, then do the inventory
posting. Investigate root cause — was there a missing GR? A goods issue posted incorrectly? Check MB51
for recent movements.
⚡ Cross-Questions They Might Ask:
How quickly can you post a physical inventory adjustment in SAP?
→ → It's a same-day process — create PI document (MI01), enter count (MI04), post difference (MI07). If
you have the right authorizations, it can be done in an hour.

Q6. Your company just signed a new supply agreement where the same material will be sourced
from 3 vendors with split percentages. How would you set this up in SAP?
Answer:
That's a quota arrangement setup. Go to MEQ1 — enter the material and plant. Define the quota
arrangement period. Add the three vendors with their respective quota values (not percentages directly —
SAP calculates the split based on quota values and cumulative quantities). Set the quota arrangement
usage indicator in the material master so source determination picks it up. Then test by creating a PR and
checking the source determination — it should propose vendors in the right split. Also set up info records for
all three vendors with correct pricing.
⚡ Cross-Questions They Might Ask:
How does the quota system decide which vendor to use for a specific requisition?
→ → It calculates the quota rating for each vendor (existing quantity divided by quota value) and picks the
vendor with the lowest rating — ensuring the split stays proportional over time.

Q7. An invoice was posted in MIRO with incorrect price. It's already been paid by FI. How do you
correct it?
Answer:
Since it's already paid, you can't reverse the invoice directly. Options: If it was overpaid, request a credit
memo from the vendor — post it in MIRO to create a credit document. If underpaid, post a subsequent debit.
FI will handle the payment adjustment — they might do a debit memo or apply the credit to the next
payment. If it was a systematic pricing issue (wrong info record), fix the underlying price data and document
it. Also check if this is a one-off or a recurring issue — you might need a tolerance limit review.
⚡ Cross-Questions They Might Ask:
What transaction do you use to post a credit memo in MM?
→ → MIRO — but you select 'Credit Memo' as the transaction type instead of 'Invoice'. It's the same screen,
different selection.

Q8. A material is being transferred from Plant A in Germany to Plant B in India. Walk me through
how you'd set this up in SAP.
Answer:
This is a cross-company, cross-border stock transfer. First, the inter-company STO process: Create an STO
with the receiving plant as the purchasing plant and sending plant as the vendor. Plant A (vendor plant)
creates an outbound delivery using VL10B. Goods issue is posted — stock leaves Plant A, goes into transit.
Plant B does a GR using MIGO against the STO — stock lands in Plant B. On the billing side, Plant A raises
an inter-company billing document to Plant B. Customs declarations and import processes would also be
part of this. The pricing needs an inter-company condition type in the STO.
⚡ Cross-Questions They Might Ask:
How is the transfer price determined for inter-company STOs?
→ → Through pricing conditions in the STO — typically using a condition type like PI01 or custom inter-
company price. This can be a fixed amount, percentage markup, or based on standard cost.

Q9. The company wants to implement consignment processing with its top supplier. What are
all the master data and configuration changes needed?
Answer:
Master data: Update the purchasing info record for this vendor-material combination with info category
'Consignment' and the consignment price (usually different from regular PO price). Vendor master should
have the appropriate settings. Configuration: Ensure consignment movement types are configured correctly
(101 K, 201 K, etc.). Account determination for consignment — when goods are consumed (moved from
consignment to own stock), there's an accounting entry. MRKO needs to be scheduled for periodic
settlement. Also, train the GR team — they need to use the special stock indicator K when receiving.
⚡ Cross-Questions They Might Ask:
How is consignment stock valued on your books before consumption?
→ → It's valued at zero — it's not your stock yet, so it doesn't hit your inventory account. Only when
consumed does the liability and cost get recognized.

Q10. You notice that MRP is generating purchase requisitions even though you have enough
stock to last 3 months. What could be wrong?
Answer:
Several possibilities. First, check the safety stock level — if safety stock is very high, MRP might see a
deficit against it. Check the lot size procedure — if it's EX (lot-for-lot) vs. FX (fixed lot), some lot sizes create
unnecessary orders. Check if there are reservations consuming the stock in MRP logic (MD04 shows the full
picture). Also check the plant parameters — maybe the MRP horizon is set too short and not seeing far-
enough existing supply. Check if there are planned orders or open PRs that haven't been considered. MD04
is my first port of call.
⚡ Cross-Questions They Might Ask:
What's the difference between available stock in MMBE and the planned quantity in MD04?
 → → MMBE shows current physical/book stock. MD04 shows the dynamic availability considering all
reservations, open orders, purchase orders — it's the forward-looking picture MRP uses.

Q11. The procurement team wants to ensure that only approved vendors can be selected for a
specific material. How do you enforce this in SAP?
Answer:
Source list is the mechanism. Create a source list (ME01) for the material-plant combination with the
approved vendors and mark it as 'fixed source' if appropriate. In the plant parameters or material master
MRP view, set the source list usage indicator. Also, you can block unauthorized vendors by not having them
in the source list and setting the source list as mandatory in customizing. Additionally, purchasing info
records only for approved vendors — without an info record, no price will default and buyers will have
trouble creating POs.
⚡ Cross-Questions They Might Ask:
Can you prevent a buyer from manually overriding the source list?
→ → It depends on the configuration — you can set source list enforcement so the system gives an error,
not just a warning. Authorization objects can also restrict which vendors buyers can use.

Q12. You're asked to set up a Blanket Purchase Order for office supplies — a vendor will be
paid up to $50,000 over the year. How do you do this?
Answer:
Use a framework order (document type FO) or a standard PO with item category B (blanket item). For item
category B: No material number, just a description. Set the target value at $50,000 and the validity period for
the year. Account assignment (usually cost center). When purchases happen, invoices reference this PO —
each MIRO posting reduces the target value. No GR is required. The team just invoices against it until the
limit is exhausted. I'd also set up a reminder or reporting to track consumption against the limit.
⚡ Cross-Questions They Might Ask:
What's the difference between a framework order (FO) and a blanket PO item (item category B)?
→ → Framework order (FO) is a document type — it's an outline agreement. Item category B is for blanket
items within a standard PO. Both achieve similar outcomes but framework orders have more formal
release mechanics.

Q13. A batch of raw materials was received and is currently in quality inspection. Production
urgently needs it. What are the options in SAP?
Answer:
In QM-integrated scenarios, only QM can release the batch — the usage decision in QA11 moves it from
quality inspection to unrestricted. If QM is not integrated (manually managed), a quality person can do a
transfer posting using MIGO from quality inspection stock to unrestricted (movement 322 — or 321 for the
reverse). In urgent situations, many organizations have a conditional release process where the quality team
can do a provisional approval and release with documented risk. Never circumvent QM for critical materials
without proper authorization.
⚡ Cross-Questions They Might Ask:
What's the movement type to transfer from quality inspection to unrestricted stock?
→ → 322 — transfer from quality inspection stock to unrestricted use. 321 is the reverse (unrestricted to
quality inspection).

Q14. Your company acquired a new legal entity and needs to be set up in SAP MM. What's the
sequence of steps?
Answer:
It depends on whether it's a new company code or an extension. Typically: Define the new company code in
FI. Define plants under that company code. Set up the plant in MM — assign it to the company code, define
MRP parameters, warehouse structure, document number ranges. Define purchasing organizations and
assign to company code and plant. Set up purchasing groups. Create the vendor and customer master data.
Configure account determination for the new company code. Migrate or extend materials — create material
master for each plant. Test the full P2P cycle end-to-end. It's a project, not a one-day thing.
⚡ Cross-Questions They Might Ask:
Can one purchasing organization serve multiple company codes?
→ → Yes — a cross-company purchasing organization can be assigned to multiple company codes. This is
common for centralized procurement setups.

Q15. You find that goods were received against the wrong PO. Both POs are for the same
material and vendor. How do you fix it?
Answer:
First, don't panic. Cancel the incorrect GR — use MIGO reversal (movement 102) against the wrong PO.
This brings the stock back and reverses the accounting document. Then post a fresh GR (movement 101)
against the correct PO. The net effect is neutral on inventory. Check if there's an invoice already posted
against the wrong GR — if yes, that needs to be reversed too (MR8M) and reposted against the correct GR.
Always document the correction with a reason for the audit trail.
⚡ Cross-Questions They Might Ask:
Can you reverse a GR if there's already a stock transfer done from that stock?
→ → No — you can't reverse a GR if the quantity has been consumed or moved. You'd have to adjust
inventory another way and investigate the full transaction chain.

Q16. Finance wants to capitalize the cost of a newly purchased machine. How is this handled in
SAP MM?
Answer:
Use account assignment category A (Asset) on the PO. You'll need the asset number — created in FI/AA
beforehand. The PO is created with the asset account assignment. When the GR is posted, no inventory
stock is created — instead, the value is posted directly to the asset under construction or the final asset
account, depending on configuration. There's no MMBE stock because it's a capital item, not inventory. The
GR triggers the asset value increase in the asset module.
⚡ Cross-Questions They Might Ask:
What's the difference between AUC (Asset Under Construction) and a final asset in this context?
→ → AUC is typically used when the asset isn't ready for use — you're still acquiring/building it. Once
commissioned, you settle AUC to the final asset. The GR can post to either, depending on how the asset
is set up in FI/AA.

Q17. A vendor is complaining they haven't been paid, but MIRO says the invoice is posted. What
do you check?
Answer:
MM's job ends at MIRO — payment is FI's domain. I'd check: In MIRO (or MIR4), confirm the invoice posting
was successful and no error. Give FI the vendor number and invoice document number — they can check in
FBL1N (vendor line items) to see if the invoice is open or cleared. If cleared, it means payment was done —
maybe it went to a different bank account or was applied to a different invoice by the vendor. If still open and
past due, it's a payment run issue. Common causes: blocked invoice not released, bank details incorrect,
payment terms mismatch.
⚡ Cross-Questions They Might Ask:
What transaction shows all open vendor invoices?
→ → FBL1N in FI — vendor line item report. Filter for open items to see unpaid invoices.

Q18. Management wants a report of all POs raised in the last quarter, by buyer, with total spend
and vendor breakdown. How would you approach this?
Answer:
In standard SAP: ME2N (POs by PO number) or ME2M (by material) with appropriate selection criteria. For
a management-level report with totals, ME80FN (General Analysis) or ME2P (by purchasing group) would
work better. For a more sophisticated report, I'd use the infoset query or go to SAP Analytics Cloud / BW if
that's available. If it's a recurring requirement, I'd push for a proper BI report from the analytics team. Also,
EKKO/EKPO are the PO header and item tables — a custom ABAP report or SAP Query can extract exactly
what's needed.
⚡ Cross-Questions They Might Ask:
What are the key tables for PO data in SAP?
→ → EKKO — PO header. EKPO — PO item. EKBE — PO history (GR/IR documents). EKET — scheduling
agreement schedule lines. EKKN — account assignment.

Q19. You're implementing SAP for a company that has never used an ERP before. How do you
approach the MM master data migration?
Answer:
Master data migration is one of the most critical and underestimated parts. I'd start with data cleansing in the
source system — eliminate duplicates, standardize material descriptions, resolve missing data. Then map
fields from legacy to SAP (unit of measure mapping, material type, valuation class). Use LSMW or
BAPI/IDOC-based tools (BAPI_MATERIAL_SAVEDATA for materials,
BAPI_VENDOR_CREATEFROMDATA for vendors). Run pilot migration on a test system first. Data quality
is everything — garbage in, garbage out. I'd also ensure cutover plan is in place — what's the last date for
legacy transactions vs. first date for SAP transactions.
⚡ Cross-Questions They Might Ask:
What BAPI do you use to create materials in bulk?
→ → BAPI_MATERIAL_SAVEDATA for extending materials. For creating from scratch,
BAPI_MATERIAL_CREATEMRP1 or using LSMW with direct input.

Q20. A freight cost was not included in the PO but the vendor has charged it on the invoice.
How do you handle it?
Answer:
Post the invoice with the freight as an unplanned delivery cost. In MIRO, you can enter unplanned delivery
costs — these get distributed across the line items or handled as a lump sum, depending on configuration.
The unplanned delivery cost goes to a specific account (configured in OBYC under transaction key UPF).
Alternatively, if freight is a regular thing with this vendor, you should add a freight condition to the PO going
forward. Another option: if you have a freight condition type set up, you can add it as a subsequent
credit/debit.
⚡ Cross-Questions They Might Ask:
What's the difference between planned and unplanned delivery costs in MIRO?
→ → Planned delivery costs are in the PO (condition types like freight, customs). Unplanned delivery costs
are extra charges on the invoice not in the PO — entered in the unplanned delivery costs section of
MIRO.
Q21. Your company wants to implement GRIR (GR-based invoice verification) for all vendors.
What's the impact and what needs to change?
Answer:
It's a change to both vendor master and potentially existing POs. Impact: For each vendor, set the GR-
based IV flag in the purchasing data of the vendor master. For new POs, this flag defaults from the vendor
master. For existing open POs, you'd need to change them manually or via mass update. The operational
impact: AP team can no longer process invoices before GR. This improves three-way match compliance but
requires better coordination between receiving and AP. Also, make sure GR dates are timely — delayed
GRs will block invoice processing.
⚡ Cross-Questions They Might Ask:
What happens to the invoice if GR-based IV is set and the invoice arrives before the GR?
→ → The invoice can be parked in MIRO (saved but not posted). Once GR is done, it can be completed and
posted. Or it gets blocked until GR is confirmed.

Q22. The warehouse team says they're getting duplicate GR documents for the same delivery.
What would you investigate?
Answer:
Duplicate GR is a serious issue — it inflates inventory and causes invoice payment issues. I'd check: Was
there a system error during the original GR that made the user post again? Check the PO history (ME23N →
PO history) to see all GR documents. Also check if there's an EDI/interface that's posting GRs automatically
alongside manual GRs. For duplicate check, SAP has a duplicate check mechanism — the delivery note
field — if the same delivery note number is entered twice, the system warns or errors depending on config.
I'd also check user logs in SM20.
⚡ Cross-Questions They Might Ask:
How does SAP's duplicate invoice check work?
→ → MIRO checks for duplicate invoices based on company code, vendor, invoice date, invoice reference,
and currency. Tolerance and exact match rules are configured in OMR6.

Q23. You need to process a large number of GRs for a monthly delivery from the same vendor.
How do you make this efficient?
Answer:
A few options: Use ME59N for automatic PO creation from PRs and combine multiple deliveries. For GR, if
the quantities and materials are predictable, consider EDI integration — vendor sends an ASN (Advance
Shipping Notice) which auto-posts the GR. If manual, use MB01 with fast entry or MIGO with the PO
reference and just change quantities. Batch input or LSMW can handle mass GRs. If it's truly recurring and
predictable, a scheduling agreement with automatic GR posting might be the right setup.
⚡ Cross-Questions They Might Ask:
What is an ASN (Advance Shipping Notice) and how does it integrate with SAP?
→ → ASN is a vendor notification before delivery — it comes via EDI (DESADV IDoc) and can auto-create
or confirm inbound deliveries in SAP, enabling automatic GR processing.

Q24. The legal team says you need to track country of origin for all raw materials for customs
purposes. What do you set up in SAP?
Answer:
Country of origin is a field in the material master (Foreign Trade data) and also at the batch level. For
materials managed by batch, each batch can have a different country of origin. The foreign trade data in the
material master has fields for country of origin, region of origin, commodity code. This feeds into
export/import declarations, customs calculations, and compliance reports. If split valuation by origin is also
needed, that would be a more complex setup.
⚡ Cross-Questions They Might Ask:
Where in the material master is the country of origin stored?
→ → In the Foreign Trade: Import data view — Country of origin field. Also at batch classification level for
batch-managed materials.

Q25. You have a material with subcontracting where the vendor is returning back more finished
goods than expected — more than the PO quantity. How does SAP handle this?
Answer:
At GR posting, if the quantity exceeds the PO quantity, the over-delivery tolerance check applies. If within
tolerance, it posts — if not, you get a warning/error. The extra finished goods would still need to be
accounted for — either return them to the vendor or create a supplementary sub-contract PO for the excess.
The component consumption (543) would also be adjusted proportionally. The accounting gets complex —
you'd want to reconcile components issued vs. components actually consumed in the additional finished
goods.
⚡ Cross-Questions They Might Ask:
How does the system track component consumption in subcontracting?
→ → Through the bill of materials on the subcontracting PO. When you post GR for finished goods, the
system automatically calculates and posts 543 (component consumption) based on the BOM quantities.

Q26. Your company wants to track spare parts inventory that should not be consumed unless
approved by maintenance manager. How would you implement this?
Answer:
A few approaches. Quality Management block — keep spare parts in quality inspection stock and only
release when maintenance manager approves. Or use batch status management — create batches with
'restricted' status. Or use storage location restriction — keep spares in a specific SLoc with authorization
restrictions so only authorized users can issue from it. The cleanest approach for proper workflow is often a
plant maintenance (PM) integration — maintenance orders create reservations and the authorized GI
happens through the work order.
⚡ Cross-Questions They Might Ask:
How does PM (Plant Maintenance) integrate with MM for spare parts?
→ → PM work orders can have material components — when the order is created, MM reservations are
created. The goods issue happens through the work order (movement 261 with order reference), and PM
tracks the costs.

Q27. You're asked to do a mass price change for 500 materials — the standard price needs to be
updated for the new fiscal year. How do you approach this?
Answer:
Standard price update happens through standard cost estimate in CO (CK11N/CK24) and then release via
CK24 at period close. For materials where CO standard costing isn't used, the price can be changed via
MR21 (material price change). For mass update: MR21 allows multiple materials, or you can use LSMW or a
BAPI. Important: you can only change prices at the beginning of a period and it affects the MAP/standard
going forward. The accounting impact (revaluation) must be reviewed with finance before executing — it can
significantly impact the balance sheet.
⚡ Cross-Questions They Might Ask:
What accounting entry is created when you run MR21 to change a standard price?
 → → The system revalues the existing stock — debit/credit to the inventory account with the offsetting entry
going to a price difference or revaluation account.

Q28. A buyer created a PO with the wrong currency. The GR is done but the invoice hasn't come
yet. Can you correct it?
Answer:
This is tricky because the GR is already posted. The currency in the GR is linked to the PO. You can't
change currency on a PO once a GR is posted. Options: Reverse the GR (movement 102), then cancel and
recreate the PO with correct currency, then redo the GR. This is the clean but operationally disruptive
approach. Alternatively, if the currency difference is small and within tolerance, post the invoice with the
correct vendor currency (MIRO can handle currency conversion) and accept a small forex variance.
Financial impact must be discussed with FI. Prevention: release strategy should include currency validation.
⚡ Cross-Questions They Might Ask:
What exchange rate is used when posting a PO in a foreign currency?
→ → The exchange rate type in the PO header (usually M — average rate) and the rate is taken from the
currency exchange rate table (OB08). The rate at GR time is used for the valuation.

Q29. Management asks: why is our inventory value going up even though sales are increasing?
What MM-related factors would you investigate?
Answer:
Several angles. First, check if there's excess stock build-up — MRP over-procurement, safety stock too
high, demand forecast too optimistic. Check if there are slow-moving or non-moving materials clogging
inventory (MB52 sorted by last movement date). Are GRs being posted faster than goods are being
consumed (GIs)? Is there a lot of stock in quality inspection not being released timely? Any consignment
settlement delays? Also check if price increases on raw materials are inflating values. MB5L (inventory value
report) by material type gives a good starting point. Ultimately this is an inventory management and planning
discussion, not just an SAP transaction issue.
⚡ Cross-Questions They Might Ask:
What transaction gives you slow-moving and non-moving inventory?
→ → MB52 with a last goods movement date filter, or the MMBE with date analysis. There are also standard
MM reports like MC.1 for inventory analysis.

Q30. Your company uses S/4HANA and the business wants to use Fiori apps for the
procurement process. Which Fiori apps would you recommend for the MM team?
Answer:
For buyers: 'Create Purchase Order' (F0842A), 'Manage Purchase Orders' (F0842B). For requisitioners: 'My
Purchase Requisitions' (F1048). For GR: 'Manage Goods Receipts' (F2640) — Fiori version of MIGO. For
invoice verification: 'Create Supplier Invoice' (F0859). For master data: 'Manage Supplier (Vendor)' and
'Manage Product Master'. The Fiori Launchpad organizes these as tiles. Not all classic functionality is fully
replicated in Fiori yet — some complex scenarios still need GUI. I'd do a gap analysis between what the
team needs and what Fiori covers before committing to a full Fiori rollout.
⚡ Cross-Questions They Might Ask:
What's the difference between a Fiori app and a classic SAP GUI transaction?
→ → Fiori apps are modern browser-based UIs — accessible on any device, more intuitive. Classic SAP
GUI is the traditional thick client. Functionally they often do the same thing but Fiori is the strategic
direction for SAP going forward.
Q40. A new plant is being added to an existing company code. What MM steps do you need to
complete before it can be used for procurement?
Answer:
Define the plant in customizing (OX10). Assign it to company code (OX18). Set up MRP parameters for the
plant (OPPQ). Define storage locations (OX09). Create purchasing organization assignment. Extend existing
material masters to the new plant (MM01 or CMMN for mass extension). Set up source lists, info records,
and any contracts for that plant. Configure account determination if valuation classes differ. Test with a pilot
PO and GR cycle before opening to users. Don't forget to set up document number ranges if needed for the
plant.

Q41. A user accidentally posted a Goods Issue to the wrong cost center. The period is still
open. How do you fix it?
Answer:
The cleanest fix: reverse the incorrect GI (movement 202 — reversal of 201) and then repost to the correct
cost center (201 with correct cost center). In MIGO, select 'Cancellation' for the incorrect document. This
creates a reversal document, netting the incorrect posting to zero. Then do a fresh GI to the correct cost
center. Check with FI that the cost center postings are clean after the reversal. Document the reason for
audit purposes.

Q42. You need to procure a one-time service from a vendor who won't be used again. How do
you handle this without cluttering the vendor master?
Answer:
Use a one-time vendor (CPD account). In the vendor master, the account group defines it as a one-time
vendor — the address and specific details are entered at the time of transaction, not stored permanently.
Create the PO referencing this generic vendor, enter the specific vendor details when prompted. For
services, use item category D with the one-time vendor. This keeps the vendor master clean while still
maintaining proper financial records.

Q43. The MRP run completed but no purchase requisitions were created for a material that
clearly has a shortage. What would you check?
Answer:
Step through the MRP logic: Is MRP active for this material (MRP type ≠ ND)? Is the material included in the
MRP run (check planning file entry MDAB)? Is the requirement (reservation, sales order) actually visible in
MD04? Check the lot-sizing procedure — maybe the shortage is below the minimum lot size. Check the
procurement type — maybe it's set to in-house production (E) but no work center is available. Check the
planning horizon — maybe the shortage is beyond the planning horizon. Check for a fixed planned order or
PO already existing for that period.

Q44. Your client wants to implement a VMI (Vendor Managed Inventory) model where the vendor
replenishes stock based on consumption. How would you approach this in SAP?
Answer:
VMI can be supported through scheduling agreements with vendor-managed schedule lines, or through
consignment processing combined with regular consumption reporting shared with the vendor. The vendor
needs visibility into stock levels and consumption — typically via an EDI interface (INVOIC, DESADV
messages) or a vendor portal. In SAP: set up consignment info records, scheduling agreements. Share
stock reports (MB52, MB51) with the vendor via portal or EDI. The vendor sends ASNs, and SAP processes
them as inbound deliveries and GRs. Automated settlement via MRKO handles the financial side.
Q45. The accounts payable team is complaining that they're processing the same vendor
invoice twice for different plants. What could be causing this and how do you prevent it?
Answer:
Root cause is likely missing vendor invoice deduplication. SAP has a duplicate invoice check — but it
checks within the same company code. If two plants are in different company codes, the check won't catch
it. Prevention: configure duplicate check in OMR6 carefully — set the check to also consider reference
number and vendor. For cross-company-code duplicates, process-level controls are needed: AP team to
verify vendor invoices against a centralized invoice log. Some organizations implement SAP central invoice
management (available via SAP S/4HANA) for this.

Q46. A material's MAP (moving average price) is showing a value significantly higher than
market price. How would you investigate and correct this?
Answer:
First, understand why. Run MB51 for the material and look at recent GR documents — was there a high-
value GR that skewed the average? A cancelled document that only partially reversed? Check for any
incorrect invoice posting that raised the cost. To correct: MR21 (material price change) adjusts the MAP and
creates a revaluation document. But you can't just lower it without justification — the difference is posted to
a revaluation account, impacting the P&L. Document the reason and get FI sign-off before executing.

Q47. You are asked to configure a second purchasing organization for a newly acquired
subsidiary that should be kept separate from the main purchasing org. What's involved?
Answer:
Define the new purchasing organization in customizing (OX08). Assign it to the relevant company code(s)
and plant(s). Configure number ranges for purchasing documents under this Purch Org. Set up purchasing
groups assigned to this org. Extend vendor masters for this purchasing organization (purchasing data).
Create info records, contracts, and source lists specific to this org. Set up release strategy if needed. Also
review authorization roles — users from the subsidiary should only see their org's data. User access is
typically tied to purchasing organization via authorization objects.

Q48. A contract has been signed with a vendor for 10,000 units over 12 months. How do you set
this up and track utilization?
Answer:
Create a quantity contract in SAP (document type MK). Enter the vendor, material, target quantity (10,000),
validity period (12 months), and agreed price. Activate release order documentation. As buyers create
release orders (POs) referencing this contract, the system tracks cumulative released quantity vs. target.
ME33 (display contract) shows the contract overview with release history. ME3M or ME2V show releases by
material/vendor. Setup an alert or reporting to notify when 80% of contract quantity is consumed — gives
time to renegotiate.

Q49. An audit finding requires that all purchase orders above $10,000 must have at least 3
approval levels. The current system has only 1 level for POs above $5,000. What changes are
needed?
Answer:
Release strategy change in SPRO → MM → Purchasing → Purchase Order → Release Procedure →
Define Release Strategy. Add new release codes for the additional approval levels. Adjust the release
conditions (characteristic values) to set the $10,000 threshold. Define the new release indicators. Test the
multi-level release flow in the QA system thoroughly — including scenarios for partial release, rejection, and
change-triggered re-release. Also update authorization roles so the right people have the new release
codes. Communicate the change to procurement and approvers with training.

Q50. Year-end is approaching and there are many open POs that won't be fulfilled this year.
What MM activities are typically done for year-end close?
Answer:
GR/IR reconciliation (MB5S) — clear any old or erroneous items. Close POs that are complete — set
delivery complete and final invoice indicators. Check open obligations — report to finance on outstanding
PO values for accrual purposes. MRP consideration — make sure any future demand in the new year is
properly planned. Period close in MM (MMPV) to open the new posting period. Archive old closed
documents if archiving is in scope. Coordinate with FI on balance sheet cutoff — make sure all December
GRs are posted in December.
 SECTION 3: BEHAVIOURAL QUESTIONS (50 Q&A)

Behavioural questions test your soft skills, maturity, and how you've handled real situations. Use the STAR
method (Situation, Task, Action, Result) as your framework. Be specific — generic answers don't land well
at this experience level.

Q1. Tell me about a time you had to learn a new area of SAP quickly because of project
demands.
Answer:
On one of my projects, we were rolling out WM integration mid-project and I'd primarily worked on IM
(Inventory Management) before. The project couldn't afford a WM specialist, so I jumped in. I did a quick
structured self-study — SAP documentation, sandbox experiments, and called in a few favors with ex-
colleagues who had WM experience. Within three weeks I had enough to configure the basic WM-IM link,
storage type definitions, and transfer order process. I made sure to document everything I learned because I
knew others would need it. Lesson: you don't need to be an expert from day one — you need to be honest
about what you know, what you don't, and learn fast.
⚡ Cross-Questions They Might Ask:
What resources do you use when learning new SAP functionality?
→ → SAP Help Portal, SAP Learning Hub, openSAP courses, SAP Community forums, and honestly — the
sandbox system. Hands-on is always faster than reading.

Q2. Describe a situation where you found a significant error in a live SAP system. How did you
handle it?
Answer:
We had a case where account determination was incorrectly configured for a new plant — every GR for the
past two weeks had been hitting the wrong GL account. Finance flagged the discrepancy in month-end. My
first step was to scope the damage — how many documents, what value. Then I worked with FI to
understand the correct GL mapping. Fixed the OBYC configuration immediately. For the backlog, we
generated a list of all affected documents and worked with FI to do journal entry corrections on the wrongly
posted amounts. No system reversal — just FI corrections. Reported transparently to the project manager
and client. Key: don't hide it, scope it, fix it, and prevent it from recurring.
⚡ Cross-Questions They Might Ask:
How do you prevent configuration errors in a production system?
→ → Transport controls, proper testing in QA before moving to production, and peer review of configuration
before transports are released.

Q3. Tell me about a time you disagreed with a decision made by a senior stakeholder about an
SAP MM process design.
Answer:
In one implementation, the Finance Director wanted to skip GR-based invoice verification for all vendors —
they felt it slowed down payment processing. I disagreed strongly from a controls and compliance
perspective. Instead of a flat objection, I prepared a risk impact assessment — what could go wrong,
potential for duplicate payments, audit risk. I presented alternatives: GR-based IV for strategic vendors, with
auto-GR for small-value recurring vendors. We ended up implementing a tiered approach. The key was
coming with data and alternatives, not just resistance. The relationship stayed intact.
⚡ Cross-Questions They Might Ask:
 How do you handle it when your recommendation is overridden?
→ → Document your recommendation and the decision made. Implement the chosen direction
professionally. If the risk materializes later, don't say 'I told you so' — help fix it.

Q4. Give me an example of when you had to explain a complex SAP concept to a non-technical
business user.
Answer:
The GR/IR account always confuses non-finance people. I had a Finance VP who couldn't understand why
there was a 'liability' that wasn't really owed to anyone. I used a simple analogy — it's like a parking ticket
holder at a hotel. You take the ticket when you check in (GR), pay when you check out (invoice). The
parking spot (GR/IR) just holds it in between. When they're matched, it clears. She actually used that
analogy in a board meeting to explain the month-end accruals. Making complex things simple is a skill —
you have to know the concept deeply to explain it simply.
⚡ Cross-Questions They Might Ask:
What do you do when users keep coming back with the same questions?
→ → Build better documentation and training materials. If a question comes up three times, it means the
training gap hasn't been closed. Create a quick reference guide or FAQ.

Q5. Describe a time when you had to work under pressure to meet a go-live deadline.
Answer:
We were three weeks from go-live and our master data migration had a 30% failure rate on vendor masters
— mostly missing reconciliation account mappings. The team was panicking. I broke it down: identify the
failure categories, fix the root cause in the mapping template, prioritize the top 200 critical vendors for
manual cleanup, and run the remaining in batch overnight. I stayed late for five nights, coordinated with the
FI team for account mappings, and we hit go-live with 98% clean. The remaining 2% were low-activity
vendors that we cleaned post go-live. Pressure is a filter — it shows who stays focused and who goes in
circles.
⚡ Cross-Questions They Might Ask:
How do you prioritize when everything seems urgent during go-live?
→ → Categorize by business impact. What stops transactions from happening? Fix that first. What's
cosmetic or low-frequency? That can wait.

Q6. Tell me about a process improvement you proposed and implemented in an SAP MM
context.
Answer:
At one client, the AP team was spending 3 hours every week manually reconciling GR/IR. The issue was
that no one owned the old items — they just accumulated. I proposed a weekly GR/IR review process with
ownership assigned to buyers, not AP. Created a simple ALV report showing open GR/IR by buyer with
aging. Set up a monthly meeting to review items older than 60 days. Within two months, the balance
dropped by 70% and the monthly close time for GR/IR reconciliation dropped from 3 hours to 30 minutes.
Small process change, big impact.
⚡ Cross-Questions They Might Ask:
How do you build buy-in for process changes that affect other teams?
→ → Show them the personal benefit — what's in it for them. Less firefighting, fewer audit queries, less
rework. People don't resist good ideas; they resist feeling like the change is being done TO them.
Q7. Describe how you've handled a situation where user requirements kept changing during an
SAP MM implementation.
Answer:
Scope creep is real in every SAP project. In one rollout, the procurement team kept adding new
requirements every sprint — new approval workflows, additional reports, custom fields. I started
documenting every change as a formal change request with a time estimate and impact assessment. This
made the 'cost' of changes visible. It wasn't about saying no — it was about saying 'yes, and here's what it
moves.' The project manager backed this approach, and the change requests slowed down significantly.
What remained were truly important changes. Change control isn't bureaucracy — it's survival.
⚡ Cross-Questions They Might Ask:
How do you say no to a change request without damaging the relationship?
→ → Explain the impact, offer alternatives, and make it a business decision rather than a technical one. 'We
can do this, but it moves the go-live by 2 weeks — is that acceptable?' Usually reframes it quickly.

Q8. Tell me about a time you mentored or supported a junior team member on an SAP project.
Answer:
I had a junior consultant on my team who understood the theory but struggled with real-world scenario
mapping. She'd configure things textbook correctly but miss the business impact. I started a weekly 30-
minute 'connect the dots' session where we'd take a real scenario from the week and trace it end-to-end —
from business need to SAP transaction to accounting entry to report. After 2 months, her client feedback
scores improved dramatically and she started catching config gaps before testing even started. Teaching
forces you to learn deeper — it helped me too.
⚡ Cross-Questions They Might Ask:
How do you balance mentoring responsibilities with your own project deliverables?
→ → Time-boxing — structured, short sessions rather than ad-hoc. And involving them in my own work as a
learning experience rather than separate sessions.

Q9. Give me an example of a cross-functional challenge you resolved in a SAP implementation

involving MM and FI teams.
Answer:
We had a major disagreement between MM and FI about how to handle freight costs — MM wanted it as a
PO condition (planned delivery cost), FI wanted it as a separate vendor invoice. Both approaches had merit.
I organized a joint session with both teams, facilitated the discussion around the actual business scenarios,
and we landed on a hybrid: freight in PO as a condition when known upfront, separate invoice when it's
variable and not known at order time. Documented it in the design document and both teams signed off. The
key was making it about the business need, not team preference.
⚡ Cross-Questions They Might Ask:
What's your approach when two teams have technically different but both valid solutions?
→ → Document both, run a pros/cons analysis against the business requirements, and let the business
decide with informed input. Don't pick a side based on team affiliation.

Q10. Tell me about a time you had to manage multiple priorities and how you kept everything on
track.
Answer:
In one period, I was running a rollout for Plant A, supporting production issues for Plant B, and
simultaneously doing design workshops for a future Phase 2. Three completely different contexts. I used a
simple but effective method — daily prioritization at 8 AM, flagging anything that was genuinely urgent vs.
what felt urgent. I communicated proactively with stakeholders: 'I can get to this by Thursday, does that
work?' Most times it did. The Plant B production issues always got first priority as live system issues. The
rest was sequenced. The lesson: you can't do everything at once, but you can be transparent about
sequencing.
⚡ Cross-Questions They Might Ask:
How do you handle a production issue that comes in right in the middle of a critical design session?
→ → Triage immediately — is it truly down or degraded? If truly down, excuse yourself and address it. If it's
degraded with a workaround, flag it, schedule time to fix it same day, and continue. Transparency with
both groups is key.

Q11. Describe a mistake you made in an SAP project and what you learned from it.
Answer:
Early in my career, I configured release strategy for POs without testing the edge cases — specifically, what
happens when a PO is changed after release. In the client's production system, buyers found that any price
change reset the full release and required re-approval from 3 levels, even for a one-cent change. It caused
massive delays. I'd tested the standard cases but not the exception scenarios. Lesson: always test the 'what
if' scenarios, not just the happy path. Now I have a standard checklist for release strategy testing that
includes 10+ change scenarios.
⚡ Cross-Questions They Might Ask:
How do you ensure you don't repeat the same mistake in the next project?
→ → Checklist and documentation. After each issue, I add it to my personal lessons-learned tracker and
turn it into a test case for future projects.

Q12. How do you stay current with SAP MM updates and new features?
Answer:
A mix of things: SAP's release notes and product roadmaps — they publish quarterly release highlights.
SAP Community (blogs and Q&A) is excellent for real-world scenarios. LinkedIn for community discussions.
I've done a few SAP Learning Hub courses, especially when S/4HANA features were being released. And
honestly, sandbox time — just trying things out. I also follow a few SAP MVPs on social media who break
down complex topics well. The field moves fast, and staying current is just part of the job.
⚡ Cross-Questions They Might Ask:
What's one recent SAP MM feature or change that impressed you?
→ → MRP Live in S/4HANA genuinely impressed me — the planning speed improvement from hours to
minutes changes how planners can work. It makes iterative planning realistic.

Q13. Tell me about your experience working with business users during User Acceptance
Testing (UAT).
Answer:
UAT is where projects either win or lose end-user trust. My approach: prepare test scenarios in advance
with the business (not just tell them 'test everything'). Create test scripts that follow real business processes,
not just system transactions. Sit with users during UAT — not to fix things for them, but to understand what
confuses them and why. Their confusion is often your documentation gap or a UX issue. Also, I always set
up a defect log with categories — critical (blocks go-live), major (workaround exists), minor (post go-live fix).
Separating those keeps UAT focused.
⚡ Cross-Questions They Might Ask:
How do you handle a user who refuses to participate in UAT?
→ → Find out why — usually it's workload or skepticism ('IT never listens anyway'). Show them previous
cases where their input changed the design. Get their manager involved if needed. UAT participation is a
project obligation, not optional.
Q14. How do you build rapport with a client team that's skeptical about the SAP
implementation?
Answer:
Skepticism is usually earned — they've been burned before or have heard big promises. I don't fight it; I
acknowledge it. First meeting: listen more than talk. Understand what went wrong before and what they're
afraid of now. Then under-promise and over-deliver on small wins. Fix that one report they've been asking
for. Explain one confusing thing clearly. Trust is built in increments. I also make sure I'm physically present
(or virtually present if remote) when things go wrong — not just for the launch parties.
⚡ Cross-Questions They Might Ask:
How do you handle a situation where a client team member actively undermines the project?
→ → One-on-one conversation to understand the concern. Sometimes it's a legitimate grievance that the
project is ignoring. Escalate only if it's genuinely disruptive and can't be resolved directly.

Q15. Describe your approach to documentation in an SAP MM project.

Answer:
I take documentation seriously — it's the institutional memory of the project. I maintain: Business
Blueprint/design documents (what was decided and why — the 'why' is often lost). Configuration
documentation (what was configured, with screenshots, not just 'configured in SPRO'). Test scripts with
expected results. User guides — role-based, not transaction-based (tell the buyer how to do their job, not
just how to use ME21N). Issue log and resolution record. All of this lives in a shared repository —
SharePoint or Confluence. Handover docs for the support team are non-negotiable.
⚡ Cross-Questions They Might Ask:
What do you do when a project has no time for documentation?
→ → Non-negotiable minimum: at least a decision log and a configuration summary. Everything else can be
done in parallel or post-go-live. But undocumented decisions create technical debt that always comes
back.

Q16. Tell me about a time you had to deliver bad news to a stakeholder.
Answer:
We discovered two weeks before go-live that our integration between MM and a legacy WMS wouldn't work
as designed — the interface couldn't handle our GR confirmation message format. Go-live would need to
slip or we'd go live without the integration. I prepared the facts: what failed, what the options were, what
each option cost in time and money. Presented to the steering committee without sugarcoating. The
decision was made to go live with a manual workaround and fix the interface in Phase 1.5. What they
appreciated was the advance warning (not a surprise on go-live day) and that I came with options, not just a
problem.
⚡ Cross-Questions They Might Ask:
How early should you escalate a risk vs. trying to resolve it yourself?
→ → If it's within your scope to resolve in 48 hours, try first. If it requires resources, decisions, or timeline
changes beyond your authority — escalate immediately. Never sit on a risk that affects others.

Q17. How do you handle a situation where two members of your team have conflicting
approaches to the same MM design question?
Answer:
First, I make sure both approaches are documented and properly understood — sometimes people argue
without fully grasping each other's positions. Then I facilitate a structured comparison: which approach better
fits the requirements, which is more maintainable, which has fewer edge case risks. If it's still a tie, I bring in
the business process owner to decide based on their operational preference. I don't let it fester —
unresolved design conflicts always surface later as bugs or support issues.
⚡ Cross-Questions They Might Ask:
What if both approaches have significant drawbacks — how do you move forward?
→ → Document the chosen approach, the drawbacks, and any mitigations. Make it a known and accepted
risk, not a hidden one. Sometimes there's no perfect answer — just the best available one.

Q18. Give me an example of where you went beyond your defined role to help a project
succeed.
Answer:
On a rollout, our FI consultant left mid-project (personal reasons). The automatic account determination for
MM was half-done and I had enough FI knowledge to see that it would cause issues at go-live. I volunteered
to complete the OBYC configuration working closely with the client's finance lead. It wasn't my original
scope, but waiting for a replacement consultant would've delayed by weeks. The finance lead and I worked
through every transaction key together. It became one of the smoothest areas in testing. Going beyond role
isn't about doing others' jobs — it's about owning the outcome.
⚡ Cross-Questions They Might Ask:
How do you make sure stepping up in a gap doesn't become a permanent expectation?
→ → Clear communication: 'I can cover this gap for X weeks, but a proper resource is needed.' Document
the temporary arrangement. Hand over properly when the right person is in place.

Q19. How do you deal with pressure from business users who want to cut corners in the SAP
MM process to save time?
Answer:
I understand where they're coming from — processes feel like speed bumps when you're busy. But corner-
cutting in SAP often creates invisible technical debt. I explain the downstream impact specifically: 'If we skip
the three-way match, we risk duplicate payments, which your CFO will ask about in the next audit.' I try to
find genuine shortcuts — can we automate something? Can we reduce manual steps legitimately? But I
won't agree to bypassing controls that exist for good reasons. Saying no with an alternative is usually
accepted; flat no rarely is.
⚡ Cross-Questions They Might Ask:
Can you give an example of a legitimate shortcut in an MM process you've implemented?
→ → ERS (Evaluated Receipt Settlement) is a great example — removes the manual invoice matching step
for trusted vendors. Or MIGO with fast GR posting using barcode scanning. Real efficiency without
compromising controls.

Q20. Where do you see yourself in the SAP MM space over the next 3 years?
Answer:
I want to deepen my S/4HANA expertise — particularly around the integration of SAP Ariba with S/4HANA
for end-to-end procure-to-pay, and also get stronger in SAP Fiori app design from a functional perspective.
I'm also interested in moving toward solution architecture — not just configuring what's asked but actively
shaping how companies should structure their MM/procurement processes. I want to lead full-cycle
implementations, not just workstream roles. And frankly, I want to mentor more junior consultants — I get a
lot of satisfaction from that.
⚡ Cross-Questions They Might Ask:
What SAP certification are you targeting next?
 → → SAP Certified Application Associate for SAP S/4HANA Sourcing and Procurement is on my list. Also
exploring the SAP Ariba certification as procurement technology becomes more integrated.

Q21. How do you handle a situation where you don't know the answer to a question in an
interview or in front of a client?
Answer:
I say 'I don't know — but here's how I'd find out.' Then I tell them the exact steps: which SAP help resources
I'd check, who I'd consult, whether it's a configuration or functional question. Nobody knows everything, but
how you handle not knowing says a lot. What you never do is bluff — experienced people see through it
instantly and it destroys credibility far faster than admitting a gap.

Q22. Describe how you keep your work organized when managing multiple SAP module
workstreams simultaneously.
Answer:
I'm a simple system person — a shared spreadsheet or project tracker with tasks, owners, and dates. Daily
status update to the team. Weekly review of what's slipping and why. I use email folders religiously —
nothing important lives in an inbox. Important decisions always follow up in writing even after verbal
discussions. On large programs, I've worked with proper MS Project plans, but even on smaller projects, the
discipline of tracking and communicating is what keeps things on track.

Q23. Tell me about a time you helped improve a team process that wasn't working well.
Answer:
Our change request process was informal — people would send Slack messages requesting changes with
no documentation. Things slipped through, priorities were unclear, and testing was haphazard. I introduced
a simple intake form: what's the change, what's the business reason, what's the priority, what's the testing
approach. Took 15 minutes to set up in Confluence. Within a month, our change backlog was visible to
everyone, the QA team could plan testing in advance, and nothing fell through the cracks. Simple solutions
are usually the best ones.

Q24. What do you do when a user asks you to bypass a control or process 'just this once'?
Answer:
'Just this once' is where it always starts. I explain why the control exists — not in a lecture way, but
specifically: 'If we skip the three-way match today, we risk paying twice if the original invoice comes in next
week — and explaining that to audit is harder than fixing it now.' If there's a genuine emergency with
executive authorization, I document it in writing: who authorized it, what was bypassed, and why. But I never
do it on someone's verbal say-so.

Q25. How do you approach knowledge transfer when you're rolling off a project?
Answer:
I start the handover at least 3-4 weeks before rolling off — not at the last minute. I create a 'who to call for
what' guide, walk the support team through the top 20 issues they'll encounter, and do shadowed sessions
where they handle a ticket while I watch. I also review any open issues and document their status so there's
no 'orphaned' work. The goal is: when I leave, the client shouldn't feel a gap. That's the only clean exit.

Q26. Tell me about a time when a project's scope was much larger than originally
communicated. How did you handle it?
Answer:
Classic case — what was described as a 'simple MM rollout' turned out to involve WM, QM, and a legacy
interface nobody had disclosed during scoping. When I got on-site and did the detailed requirements
workshop, the reality became clear. I documented the delta scope, estimated the effort honestly, and
presented it to the project manager with options: increase timeline, add resources, or reduce scope. We
ended up doing a phased approach — core MM in Phase 1, WM in Phase 2. The key was raising it early
and with evidence, not absorbing the scope silently until it became a crisis.

Q27. How do you maintain quality when you're under time pressure and tempted to skip steps?
Answer:
I have a personal 'non-negotiable' list — things I won't skip regardless of pressure. Testing in QA before
production is one. Documenting configuration changes is another. Informing affected stakeholders before
making live changes. These aren't optional based on how stressed I am — they're the baseline. Everything
else can be flexed, shortened, or simplified. But if those three go, the quality goes with them and the cost of
cleanup is always higher than the time saved.

Q28. Describe a time when you had to quickly adapt your communication style for a different
audience.
Answer:
In one steering committee, I was presenting a technical issue with the GR/IR account to a room that
included the CFO, operations director, and IT head. Each needed a different angle. For the CFO: financial
exposure and compliance risk. For operations: what it means for the team's daily process. For IT: what
system changes were needed. I'd prepared a one-page summary that addressed all three without requiring
them to read the technical document. Being able to translate between technical and business language is
probably the most underrated consulting skill.

Q29. Tell me about a time you had to rebuild trust after something went wrong on a project.
Answer:
We had a go-live that had more issues than expected in the first week — a few critical ones in the goods
receipt process. The client was unhappy. The first thing I did was stop defending and start listening. I sat
down with the business lead, asked them to walk me through every issue they were experiencing. Then I
came back the next day with a fix plan for each one, with timelines I could commit to. Fixed the critical ones
within 48 hours. Trust is rebuilt through consistent follow-through on smaller commitments — not grand
gestures or apologies.

Q30. How do you handle negative feedback from a client or manager?

Answer:
First I listen without interrupting or justifying. Then I ask clarifying questions to understand what specifically
wasn't working. If the feedback is valid, I acknowledge it and commit to a specific change. If I think it's
inaccurate, I'll say so respectfully with evidence — but I separate that from my emotional reaction to the
feedback. Most people give feedback because they want things to improve, not because they enjoy
criticizing. Treating it as useful information rather than an attack is the right frame.
 FINAL INTERVIEW TIPS

Top 10 Things to Remember

1. Have 3-4 real project stories ready. 'In my project at [Company], we handled X by doing Y' beats any
textbook answer.
2. For every technical answer, think about the business reason behind it. Interviewers want to know you
understand WHY, not just HOW.
3. Cross-questions are how interviewers probe depth. If you give a solid answer, expect a follow-up that
goes one level deeper.
4. For scenario questions, always start with what you'd investigate FIRST, not what you'd do immediately.
Good consultants diagnose before prescribing.
5. It's completely fine to say 'I'd verify this in the system' or 'I'd check the config' — that's what professionals
do. Bluffing is a disqualifier.
6. Know your transactions cold. At 4-5 years, not knowing basic transaction codes raises eyebrows.
7. Integration knowledge differentiates mid-level from senior consultants. Show that you think about MM in
the context of FI, PP, SD, and WM.
8. For behavioural questions, be specific. 'I always communicate clearly' means nothing. 'In Project X, I
noticed Y was unclear, so I did Z which resulted in W' means everything.
9. Ask good questions at the end. 'What does the SAP landscape look like?' and 'What are the biggest
challenges the MM team is facing?' show genuine interest.
10. Confidence is different from arrogance. Confident: 'I've worked on similar scenarios and here's how I'd
approach it.' Arrogant: 'I know all of this.' Stay humble and curious.

💡 Best of luck! Remember — the interviewer is rooting for you to succeed. They have a problem to solve,
and they're hoping you're the person who can solve it.