Enterprise Resource Planning Blog Posts by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
Leelamohan
Participant
0 Kudos
657

In today’s complex manufacturing landscape, businesses often rely on multiple subcontractors to produce goods efficiently. SAP’s multi-level subcontracting process simplifies this by allowing seamless material flow between vendors without unnecessary stock movements.

Business Scenario Process:
  1. Create a PO for Subcontract Vendor 1 (31000) with Subcontract Vendor 2 (11002) as the delivery address.

  2. Issue components to Vendor 1 via ME2O (Movement Type 541 O) – stock is assigned as "Stock provided to vendor."
  3. After Vendor 1 confirms production, post GR – components are consumed (543 O), and semi-finished goods move to Vendor 2 (101 O).
  4. Create a PO for Vendor 2 (no component issue needed, as stock is already with them).
  5. Post GR – semi-finished goods are consumed (543 O), and the final product is received in stock (101).

This process eliminates redundant stock handling, ensuring smooth production across multiple vendors. 

Step 1: Maintain Special Procurement for Finished and Semi-Finished materials

Leelamohan_0-1746868544872.png

Step 2: Create a BOM for the final & semi-finished product (Transaction: CS01)

BOM for finished material HF9000987

Leelamohan_1-1746868602435.png

BOM for semi-finished material HR1000005

Leelamohan_2-1746868665293.png

Step 3: Create Purchase Order (Transaction: ME21N)

Supplier as subcontracting vendor 1

Leelamohan_3-1746868698415.png

Explode the BOM components in the Material Data tab under Item details.

Leelamohan_4-1746868760182.png

Maintain the subcontractor vendor 2 address under the delivery address tab

Leelamohan_5-1746868793738.png

Step 4: Issue the components to the vendor from the subcontract cockpit (Transaction: ME2O)

Select the item and click on Post Goods Issue

Leelamohan_6-1746868858451.png

Mention the storage location, Batch, and click create document.

Leelamohan_8-1746868938650.png

Leelamohan_7-1746868903927.png

No accounting entries will be generated in this step.

Step 5: Check the stock (Transaction: MMBE/MB52)

Goods will be moved from unrestricted to Stock provided to the subcontracting vendor 1

Leelamohan_9-1746869004712.png

Step 6: Post Goods Receipt upon confirmation received from the 1st subcontractor sending goods to the 2nd subcontractor

Since the SC supplier checked in the PO, the semi-finished product was automatically posted with movement type 101 O. 

Components will be consumed with 543 O movement, accounting entries will be generated.

Leelamohan_10-1746869355943.png

Step 7: Check the Stock(Transaction: MMBE/MB52)

Leelamohan_0-1746894351476.png

Step 8: Post Incoming Invoice (Transaction: MIRO)

In PO, the semifinished product net price is maintained as 100 SAR for 1 EA.

Total Price: 200 SAR, including 5% Tax: 204 SAR.

Leelamohan_1-1746894451813.png

Step 9: Create a subcontract PO for Finished Product from Subcontracting vendor 2 (Transaction: ME21N)

Supplier will be subcontractor 2 11002

Click on Components and check for the BOM.

Leelamohan_2-1746894581995.png

Finished Product BOM

Leelamohan_3-1746894653794.png

Maintain the delivery address to the plant where you will receive the finished product under the delivery address tab in Item details

Leelamohan_4-1746894675418.png

Step 10: Post Goods Receipt (Transaction: MIGO)

 Subcontracting vendor 2 sent the finished product to our location.

Finished product will be posted with movement type 101, components (semifinished product will be consumed with 543 O movement type)

Leelamohan_5-1746894897566.png

Leelamohan_6-1746894963798.png

Step 11: Check the Stock for finished product (Transaction: MMBE/MB52)

2 EA posted to location 1005 with 101 movement.

Leelamohan_7-1746895004924.png

Refer blog below for the Assembly subcontracting process.

Assembly Subcontracting Process in Production Planning - SAP S/4 HANA

 

Regards,

Leelamohan Mannem