ERPClimb logoERPClimb

SAP MM / P2P Subcontracting Interview Questions

Subcontracting 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 9 reviewed SAP MM / P2P subcontracting interview questions, each with a complete written answer and no sign-in required. The set breaks down into 1 foundational and 8 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 subcontracting.

9 Subcontracting questions with answers

easySubcontracting

1. What is source determination in a subcontracting scenario, and how does it differ from source determination for standard stock or service procurement?

Subcontracting source determination identifies which vendor (subcontractor) will perform the operation on components you supply, typically via a subcontracting info record (category 3) or source list entry tied to item category L. Unlike standard procurement, the 'price' reflects only the processing fee, not material value, and the BOM/component list drives what stock is issued to the vendor. Source list and quota arrangement can still apply, but material valuation and component provisioning are unique to this process.
hardSubcontracting

2. How would you architect a subcontracting solution where the subcontractor also performs external services requiring service entry sheets, and components must be provided cross-company from a different legal entity?

Design the subcontracting PO with item category L for material components combined with service line items using account assignment for the labor portion, ensuring the BOM/component provision is triggered via 543 movement types against the subcontractor stock. For cross-company component provision, use a stock transport order or intercompany billing process to move components to the subcontractor's stock account before consumption, and configure separate service entry sheets for labor confirmation with three-way match against the service line. Ensure FI-AP intercompany reconciliation accounts are aligned to avoid mismatched postings.
hardSubcontracting

3. What controls should be designed to prevent GR/IR imbalances when a PP subcontracting interface repeatedly fails to post goods receipts for components sent to a subcontractor?

Controls should include interface monitoring alerts for failed subcontracting GR IDocs, a reconciliation job comparing PP subcontracting purchase orders against actual GR postings, and a block on invoice posting (MIRO) for subcontract POs lacking a confirmed GR beyond a defined threshold. Additionally, segregation between subcontracting component consumption postings and finished goods GR should be validated periodically to catch silent interface failures before they accumulate GR/IR variances.
hardSubcontracting

4. A subcontracting vendor's special stock (movement type 541 issued components) shows a large unexplained variance versus the vendor's confirmed consumption at period close, and the GL account for subcontracting consumption is out of balance with the physical component stock at the vendor. How would you architect the root-cause investigation and remediation?

Investigate whether components were issued (541) but the subsequent goods receipt of the finished/semi-finished material (101 with movement 543 backflush) was delayed, incomplete, or posted with incorrect BOM consumption quantities, since special stock at vendor (O) is tracked separately in MSKA/MSLB-type records and only clears on GR. Reconcile using MB25 (list of stock provided to vendor) against vendor consumption confirmations, verify subcontracting info records and PO components, and check whether GR postings triggered 543 movements correctly consuming the vendor stock account. Root cause is often timing mismatches or wrong component quantities in the subcontracting PO, not GL misconfiguration.
hardSubcontracting

5. Walk through how source determination works for a subcontracting process in SAP MM, including how the subcontractor is selected and components are provided.

A subcontracting PO uses item category L, with the subcontractor set up as a vendor and the finished material's BOM exploded to determine component requirements. Source determination can use a source list entry marking the subcontractor as the fixed source for that material, or a purchasing info record maintained with subcontracting info category. Components are transferred to the vendor's stock via a transfer posting (movement type 541) based on the BOM, and consumption occurs automatically at goods receipt of the finished product (movement type 101/543).
hardSubcontracting

6. During Fit-to-Standard workshops for a P2P migration, the client's PP team insists on retaining a custom subcontracting reconciliation process built in ECC that has no standard equivalent in S/4HANA Public Cloud. How do you handle this in the fit-to-standard methodology and what integration risk must be flagged?

Document the gap formally in fit-to-standard, first testing whether standard S/4HANA subcontracting monitoring (e.g., stock/consumption reconciliation reports) can partially satisfy the requirement before considering a custom extension. If a gap remains, evaluate side-by-side extensibility on BTP rather than core modification, since Public Cloud disallows in-app custom code for this scenario. Flag the PP-MM integration risk that subcontracting component consumption and reconciliation timing may diverge from legacy behavior, requiring parallel testing during migration.
hardSubcontracting

7. A global rollout wants to extend inbound delivery processing (currently used only for scheduling agreements with materials) to cover components supplied to a subcontractor performing external services, so goods receipt and FI-AP invoice matching align with a common document type architecture. What architectural considerations would you evaluate before extending inbound delivery to this scenario?

Assess whether the subcontracting PO item category (L) and confirmation control key support inbound delivery creation, since inbound delivery is primarily designed for stock transfer and standard procurement scenarios, not subcontracting component provision. Evaluate whether extending it adds value versus using standard goods issue against the subcontract PO, check impact on component consumption postings, GR/IR account determination, and whether FI-AP three-way match (PO, GR, invoice) remains consistent. Document type segregation is needed to avoid mixing subcontracting and standard procurement inbound delivery types.
hardSubcontracting

8. A client running S/4HANA Public Cloud with tight clean core governance discovers that a PP-integrated procurement scenario (subcontracting with component provisioning) needs custom logic that standard scope items don't cover. As architect, how do you evaluate whether this justifies an extension versus a process change, and what monitoring implications follow?

I'd first validate against standard scope item documentation and released BAdIs/CDS extension points to confirm no standard configuration path exists, then assess business criticality: if the gap is core to competitive differentiation, propose a side-by-side BTP extension using released APIs/events rather than in-app modification; if it's a minor variance, recommend process adaptation to standard subcontracting/PP-MM integration flows. Either way, added extensions increase integration monitoring scope, requiring API usage monitoring and event-based error handling in the BTP layer, and must be revalidated against future release compatibility.
hardSubcontracting

9. In a subcontracting scenario, a subcontract PO (item category L) posts goods issue of components automatically at goods receipt, but stock discrepancies are appearing between the subcontractor stock (special stock indicator O) and the component consumption. As the architect, what document type and configuration areas would you investigate?

Investigate whether the subcontracting PO document type is correctly linked to movement types 541 (transfer to vendor) and 101/543 (goods receipt with consumption), and whether the BOM/component list on the PO item is accurate and current. Check for unplanned consumption, scrap postings, or manual adjustments via MB1B that bypass the automatic backflush. Also verify subcontractor stock monitoring (ME2O) matches actual component provision, and confirm no partial deliveries created mismatched consumption ratios against the BOM quantity.

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