ERPClimb logoERPClimb

SAP MM / P2P Goods Receipt and Goods Issue Interview Questions

Goods Receipt and Goods Issue comes up in SAP MM / P2P interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

This page carries 18 reviewed SAP MM / P2P goods receipt and goods issue interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 10 mid-level and 6 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for goods receipt and goods issue.

18 Goods Receipt and Goods Issue questions with answers

easyGoods Receipt and Goods Issue

1. What is the purpose of an inbound delivery in SAP MM, and how does its document type configuration influence downstream goods receipt processing?

An inbound delivery represents the advance notification of incoming goods, typically triggered by ASN from a vendor or created manually referencing a PO. The document type (e.g., EL) controls number ranges, item categories, and whether the delivery supports batch determination, handling unit management, or warehouse task creation. It enables goods receipt via MIGO with reference to the delivery, improving dock scheduling, put-away planning, and reducing manual data entry errors at receipt.
easyGoods Receipt and Goods Issue

2. What is the purpose of movement type 122 in a return delivery to vendor, and how does it differ from a standard goods issue in terms of GL account impact?

Movement type 122 reverses a prior goods receipt (101) against a purchase order, returning stock to the vendor. It debits the GR/IR or vendor-related account and credits stock, mirroring the original posting logic rather than using consumption accounts like a normal issue (201/261). It requires reference to the original PO/GR so quantities and values reverse correctly, keeping vendor liability and inventory value consistent.
mediumGoods Receipt and Goods Issue

3. During Fit-to-Standard workshops for a P2P migration to S/4HANA Public Cloud with EWM integration, the client asks why several of their current ECC customizations around goods receipt confirmation and quality inspection cannot simply be carried forward. How would you explain this and guide the workshop outcome?

I'd explain that Public Cloud enforces standard, pre-configured scope items with limited extensibility, so custom ECC enhancements like modified goods receipt screens or custom quality inspection logic aren't directly portable; EWM-integrated inbound processes follow standard scope items (e.g., decentralized EWM warehouse integration), and any gaps must be addressed through configuration within released BAdIs/CDS extensibility or accepted as process change. The workshop outcome should document each gap, classify it as standard-fit, configurable, or requiring BTP-based extension, and get business sign-off on adopting standard processes where extension isn't feasible.
mediumGoods Receipt and Goods Issue

4. In an EWM-integrated warehouse scenario, goods receipt is confirmed in EWM before the ERP GR posting, and the invoice includes withholding tax. What architecture considerations ensure tax and withholding calculation align correctly with the GR/IR timing?

EWM confirmation triggers the ERP goods movement via CIF/embedded EWM integration, which posts the GR and updates GR/IR; tax code and withholding tax base are determined at MIRO time from the PO and vendor master, independent of EWM timing, but delays in EWM-to-ERP GR posting can cause invoices to be blocked or held pending GR (evaluated receipt matching). I'd ensure GR posting latency is monitored and withholding tax base date logic (invoice date vs posting date) is validated in tax configuration to avoid period misalignment.
mediumGoods Receipt and Goods Issue

5. A goods receipt is posted to quality inspection stock, later rejected and moved to blocked stock, and finally scrapped. Walk through the FI-GL postings triggered at each stage and the account determination involved.

GR to quality stock (movement 103/105 or QM-triggered 101 to inspection) debits inventory via BSX and credits GR/IR via WRX, with quality stock still valuated and part of inventory value. Moving to blocked stock (movement 350/349) is typically a quantity-only transfer within valuated stock, no GL impact. Scrapping from blocked stock (movement 551/552) debits an expense/scrapping account via transaction key VBR and credits inventory BSX, removing value from stock and hitting P&L.
mediumGoods Receipt and Goods Issue

6. Warehouse goods receipts processed in a decentralized EWM system are arriving in ERP/S4 with a noticeable delay, causing GR/IR aging reports to show open items that later resolve automatically once the EWM confirmation syncs. How would you architect monitoring to distinguish this from real reconciliation issues?

Design monitoring that tags GR/IR open items by source system and includes an EWM sync-latency indicator, so items pending EWM confirmation within an expected SLA window are excluded from exception reporting. Implement interface queue monitoring for EWM-to-ERP GR confirmations, track average sync latency, and set aging thresholds beyond the SLA to trigger true exception alerts rather than flagging every delayed item as a defect.
mediumGoods Receipt and Goods Issue

7. Your MDG system pushes vendor master changes into the SAP ERP backend nightly, but a batch of GR/IR clearing postings failed overnight because vendor bank data updates from MDG created a lock on vendor master records mid-posting run. How would you diagnose and resolve this integration conflict?

I would check application logs (SLG1) and the MDG replication monitor for the timing of the change pointer/IDoc processing versus the batch job schedule, review vendor master change document history (XK04) for the affected vendors, and confirm whether a lock (SM12) was held during posting. Resolution typically involves rescheduling MDG replication outside the FI batch window, or using a distribution lock exception for critical postings, plus retrying failed GR/IR clearing documents via F.13 or manual clearing.
mediumGoods Receipt and Goods Issue

8. A material is purchased in pallets as the order unit but received and valuated in the base unit 'each', with the conversion factor rounded to a whole number. Finance notices small price variance postings on nearly every goods receipt for this material. Explain the root cause and how unit-of-measure design impacts GR/IR and inventory valuation postings.

Rounding the pallet-to-each conversion factor causes the derived per-unit price to differ slightly from the PO order-unit price, so at GR the system posts the rounding delta to a price difference or GR/IR clearing account rather than fully to inventory. This repeats on every receipt. The fix is maintaining a more precise conversion factor with additional decimals where supported, or using an alternate UoM with an exact ratio, and validating PO price unit against order unit before rollout.
mediumGoods Receipt and Goods Issue

9. You are architecting output management for goods receipt confirmations against purchase orders in an S/4HANA environment integrated with an embedded/decentralized EWM warehouse, and cutover requires reliable packing slip and GR notification output. What design approach ensures this works consistently across legacy and new plants during transition?

Map output determination in EWM (via condition-based output/ BRF+ or PPF depending on deployment) separately from MM PO output, since GR confirmations and packing outputs are EWM-triggered, not NAST-driven in embedded EWM. Validate warehouse-specific output profiles per plant, ensure printer/device master data is cut over plant-by-plant, and run parallel output tests for both migrated and greenfield plants before go-live to catch profile gaps.
mediumGoods Receipt and Goods Issue

10. Interface monitoring alerts show intermittent failures in the EWM-to-ECC/S4 goods receipt confirmation feed, resulting in invoices being blocked for 'no GR found' even though physical receipt occurred in the warehouse three days prior. How would you conduct root cause analysis across this integration?

I'd start by checking the EWM outbound queue and qRFC/IDoc monitor (if applicable) for failed or delayed confirmation messages, then verify if the delay correlates with peak warehouse processing times causing queue backlogs. I'd trace a specific failed document through EWM's physical inventory/GR confirmation log into the ERP goods movement table to pinpoint where the message stalled, then check for duplicate or conflicting confirmations that could cause reprocessing failures, before escalating a fix for queue capacity or retry logic.
mediumGoods Receipt and Goods Issue

11. A plant is experiencing incorrect goods receipt confirmations where quantities recorded don't match actual deliveries because Confirmation Control keys are misconfigured on service and inbound delivery scenarios. How would you approach reviewing and correcting the confirmation control setup?

I would review the confirmation control key assigned at PO item level to check which confirmation categories are active (order acknowledgment, inbound delivery, shipping notification) and whether the sequence/relevance flags force goods receipt to only accept quantities matching a prior confirmation category. Misconfiguration often occurs when 'GR relevant' confirmations are marked mandatory but upstream categories were never actually transmitted, causing GR blocking or quantity mismatches. Correction involves adjusting the confirmation control key definition or reassigning a simpler key for scenarios without EDI-based inbound confirmations, then reprocessing affected open POs.
mediumGoods Receipt and Goods Issue

12. A plant reports incorrect stock quantities after a goods receipt because the alternate unit of measure conversion factor was set up incorrectly. Walk through the impact and resolution approach.

Incorrect UoM conversion causes mismatched quantities between base unit (used for valuation/stock) and order/GR unit, leading to inflated or understated inventory value and quantity in MMBE/stock reports. Correct the conversion factor in the material master additional data (Units of Measure view), but note existing open documents and historical postings retain old conversion, so a manual stock/value adjustment (physical inventory or MB1B) may be needed. Prevent recurrence by validating EAN/UoM setup during data migration checks.
hardGoods Receipt and Goods Issue

13. Walk through the end-to-end process and accounting impact when a return delivery to vendor is posted against a goods receipt that was already counted in a completed physical inventory cycle.

The return delivery (movement type 122 or similar) reduces stock quantity and value, reversing the original GR posting proportionally, debiting the vendor-related account and crediting inventory. If the physical inventory count already recorded that stock, the count difference posting must be adjusted or the count re-validated, since the return changes book quantity after the count date. Reconciliation requires comparing count date, return posting date, and inventory document sequence to avoid double adjustment in inventory-to-finance postings.
hardGoods Receipt and Goods Issue

14. A plant allows negative stock, and a goods issue posted before the corresponding goods receipt causes valuation distortion once the GR is finally entered at a different price. What is happening and how would you architect a solution to prevent recurring financial misstatement?

With negative stock allowed, the issue is valuated at the current moving average or standard price at issue time; when the delayed GR posts at a different price, the system revalues retroactively only for moving average materials, potentially creating unexpected price swings or incorrect COGS in prior periods if periods are already closed. Architecturally, restrict negative stock to specific storage locations/movement types where truly needed, enforce strict process sequencing via workflow or batch job scheduling for GR-before-GI, and consider Material Ledger multi-period valuation to allow proper cost layer correction without hard period reopening.
hardGoods Receipt and Goods Issue

15. A physical inventory count at a distribution center reveals significant unexplained stock differences concentrated in materials with open GR/IR balances. As the solution architect, how would you determine whether the discrepancy is a physical count issue or a GR/IR clearing problem masking real inventory quantities?

I would first reconcile the GR/IR account balance against open purchase order line items to identify quantities goods-receipted but not yet invoiced, or invoiced without receipt, since these don't represent physical stock discrepancies but timing differences. Next, I'd cross-check MB5S aging against the physical count document to see if count variances correlate with recent GR postings not yet reflected in bin locations, or with movement types that bypass GR/IR (like 561 initial entry). If discrepancies persist after excluding GR/IR timing noise, it points to genuine physical handling or process gaps.
hardGoods Receipt and Goods Issue

16. A middleware integration via BTP Integration Suite posts goods receipts from a third-party warehouse system, but GR/IR clearing accounts are accumulating unexplained open items after a recent interface change. How do you approach root-cause analysis?

Start by comparing the interface payload mapping against expected IDoc/OData fields for quantity, PO number, and movement type, since a mapping change can cause duplicate or partial GR postings. Reconcile MB5S aging report against interface logs in Integration Suite (message monitoring) to identify mismatched or replayed messages. Check for idempotency handling—if retries aren't deduplicated, GRs may double-post. Validate reversal postings are also correctly relayed. Engage integration team to trace message IDs against SAP material document numbers for a definitive root cause before proposing a fix.
hardGoods Receipt and Goods Issue

17. A goods receipt was posted into quality inspection stock (movement type 103/105 flow) just before period close, but the corresponding invoice and inspection release happen after the period is closed for MM. When the period reopens, the release to unrestricted use and invoice posting affect the prior period's inventory valuation figures. Walk through the movement types involved and how you would architect the close process to avoid distorted period-end reporting.

Movement 103 posts GR into blocked/inspection stock without immediately affecting valuated unrestricted stock value in some configurations, while 105 posts the value-relevant GR to inspection stock account. If the inspection release (321/322 or direct GR into unrestricted) and invoice happen after period close, the valuation impact lands in the new period, which is generally correct since the transaction wasn't complete. The real risk is if the GR was value-relevant in the closed period but invoice price differs significantly, causing PRD postings in the new period that finance didn't expect. Architect the close by ensuring MMPV/period-lock discipline, requiring GR/invoice matching before final close sign-off, and communicating cutoff rules to procurement.
hardGoods Receipt and Goods Issue

18. A production order reservation for a component is not being consumed by the goods issue, causing the reservation to remain open even after the GI is posted. As a senior consultant, how would you troubleshoot the root cause?

I'd check whether the goods issue was posted with reference to the reservation number (using MIGO with the reservation, or backflush via order confirmation) versus a standalone movement type 201/261 not linked to the reservation, which would explain why the reservation stays open. I'd also verify the reservation's movement type matches what was actually posted, check for partial quantity issues, and confirm the reservation wasn't manually created with a final delivery indicator unset, which keeps it visible even after full consumption.

Related topics

Invoice VerificationValuationAutomatic Account DeterminationService ProcurementSupplier and Business PartnerSource DeterminationS/4HANA MM Transformation, Ariba, Migration, Public Cloud and ArchitectureMaterial MasterPurchase OrderRelease StrategyFlexible WorkflowPhysical Inventory

Next practice step

Practice with Interview AITake a mock test