<aside> <img src="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" alt="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" width="40px" />
This page explains why S/4HANA needs a specific document type for subcontracting for procurement teams, manufacturing teams, and anyone trying to avoid chaos in the supply chain. In short, subcontracting uses its own document type because the process is half procurement, half production, and SAP needs a way to track both sides cleanly. It matters because without this distinction, SAP cannot manage component consumption, goods movements, or cost flows correctly. Use it when external suppliers perform part of your production, and avoid ignoring it unless you enjoy mismatched stock, blocked invoices, or subcontracting that behaves like a confused purchase order.
</aside>
Subcontracting sits in the awkward middle of procurement and manufacturing. You buy a finished material from a supplier, but you provide the components. That means SAP must treat the purchase order differently to a normal one. Assigning a dedicated subcontracting document type tells SAP “this is not a standard purchase” and activates the logic that handles component issue, movement of goods, external processing, and valuation. Without this document type, the system cannot recognise which materials are supplied by In-House Secure and which are provided by the vendor, and the entire chain collapses into confusion.
A Document Type tells SAP how a purchasing document behaves and which rules apply.
Subcontracting means buying a finished good while supplying your own components to the supplier who assembles or completes it.
A Subcontracting Purchase Order triggers SAP to expect components, track their consumption, and handle special goods movements.
A Movement Type defines how stock quantities and values change during the process.
When In-House Secure sends components to a supplier to build a product, SAP must separate the value of the components from the cost charged by the supplier. Because of this, subcontracting requires its own document type. When that type is assigned, SAP activates the subcontracting flow: reserving components, issuing them to the vendor, tracking work in progress externally, and reconciling the supplier’s invoice against both the service provided and the components consumed. As a result, stock accuracy is maintained, costs end up in the right place, and the goods receipt reflects the true value of what returns.
When the document type is missing or incorrect, SAP defaults to normal purchasing. As a result, components never leave the warehouse properly, finished goods reappear from nowhere, valuation breaks, and invoices fail three-way matching. The system tries to treat a manufacturing process like a shopping trip, and everyone loses.
In-House Secure outsources assembly of certain smart sensors during peak sales months. Components like casings, lenses, and chipboards are shipped to a UK subcontractor who assembles the finished unit. By using the correct subcontracting document type, SAP ensures that component stock is issued, tracked, and valued correctly, while the subcontractor’s fee is accounted for without inflating inventory. If the team used a normal purchase order type, the system would ignore the components entirely, the warehouse would show phantom stock, and Finance would wonder why assembly costs look like a bulk purchase from a mystery supplier.
If SAP cannot see that you are outsourcing part of production, it will guess. And its guesses are terrible.