Subcontracting
MM / P2Pbeginner

MM Subcontracting Part 1: The Subcontracting Process End to End

Key takeaway

In subcontracting you provide components to a supplier who processes them into a product and charges a service fee. Learn the flow: subcontract PO (item category L) with components, provision of components (541) to stock at supplier, GR of the finished product with automatic consumption (543), and invoice for the processing fee.

What this complete series covers

Learn Subcontracting in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for
Best for SAP consultants, developers, and learners who want a practical understanding of Subcontracting.
Prerequisites
Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome
By the end, you should be able to explain Subcontracting clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: MM Subcontracting Part 1: The Subcontracting Process End to End

    Understand subcontracting as external processing where you provide components to a supplier and receive the finished material, with component consumption posted during the subcontract receipt.

  2. Part 2: MM Subcontracting Part 2: Subcontracting BOM, Component Determination and Provision

    Control which components are provided to a subcontractor through BOM-driven or manually maintained component determination, quantity calculation and validity logic.

  3. Part 3: MM Subcontracting Part 3: Stock at Supplier and Reconciliation

    Manage and reconcile company-owned component stock held at subcontractors so shortages, excess stock and aging are visible rather than hidden outside the plant.

  4. Part 4: MM Subcontracting Part 4: Valuation, Price Differences and Accounting

    Understand financial impact of subcontracting as the combination of externally purchased processing value and company-owned component consumption, with valuation and price differen

  5. Part 5: MM Subcontracting Part 5: Troubleshooting Components, Stock, GR and Invoice Issues

    Troubleshoot subcontracting with a fixed sequence from PO item category and component list through stock at vendor, goods receipt consumption and invoice matching.

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ Subcontract PO: item category L for the finished material, with components (from BOM or entered).

✅ Components are provided with 541 into stock at supplier (special stock O) — still your stock.

✅ GR 101 of the finished product consumes components automatically (543).

✅ Supplier invoices only the processing fee (from subcontracting info record/PO price).

⚠️ Posting components as normal goods issues (201) loses track of stock at the supplier.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: The process end to end

Part 2: Subcontracting BOM, component determination and provision

Part 3: Stock at supplier and reconciliation

Part 4: Valuation, price differences and accounting

Part 5: Troubleshooting\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 1. PO\n• Item category L, processing fee price, components list.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PROVISION

  • 541 from own stock to stock provided to supplier (O); ME2O subcontracting cockpit.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PROCESSING

  • Supplier converts components to product.

━━━━━━━━━━━━━━━━━━━━
▶ 4. GOODS RECEIPT

  • 101 finished product + 543 component consumption; by-products 545.

━━━━━━━━━━━━━━━━━━━━
▶ 5. INVOICE

  • Processing fee; finished product value = components + fee.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Create L-PO with components.
  2. Provide components with 541.
  3. Post GR of finished product.

✅ CHECKPOINT: stock at supplier decreases by consumed components, finished stock increases.

Code example

ABAP Code
===== STEP 1: PO =====ME21N item category L, material FG-100, 100 PC, fee 5.00 per PC → components (from BOM): C-1 2 PC each, C-2 1 PC each ===== STEP 2: provision =====ME2O subcontracting cockpit / MIGO 541 → special stock O at supplier 300500 (MBLB stock with supplier) ===== STEP 3: GR =====MIGO 101 FG-100 → automatic 543 consumption of C-1 200, C-2 100

Real project scenario

A supplier reported receiving components that SAP didn't show at their site: staff had issued them with 201 to a cost center. Stock at supplier was invisible and product costs were wrong. Switching to 541 via the subcontracting cockpit restored visibility and correct costing.

Common mistakes

  • 201 instead of 541.
  • PO without components.
  • Missing subcontracting info record.
  • Ignoring by-products.
  • No reconciliation with supplier.

Best practices

  • Use the subcontracting cockpit.
  • Maintain subcontracting BOMs.
  • Use subcontracting info records.
  • Reconcile stock at supplier.
  • Train receiving staff on 543.

Interview angle

Questions: "Explain subcontracting in SAP", "What is movement type 541?", "What happens at GR?"
Strong answer: L-PO with components, 541 to special stock O, GR 101 with 543, fee invoice, valuation.

Practice this lesson

Quick check

1. What happens automatically when the finished product of a subcontract PO is received?

2. Which item category is used for a subcontracting PO item?

3. A supplier received components that SAP doesn't show at the supplier. They were issued with 201. What should have been used?

Interview questions

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

Answer it in your own words first, then compare.

2. 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?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics