When you sit down with a client who runs a manufacturing plant or a distribution center, you soon discover that standard procurement covers only part of what actually happens on the shop floor. Some materials sit in the warehouse but still belong to the supplier until the moment they get used. Others get sent out to a vendor who turns them into something else before they come back. And then there are materials that never really sit anywhere at all—they just flow in continuously and get consumed as needed. These are the three special procurement processes that every SAP MM consultant ends up configuring sooner or later: consignment, subcontracting, and pipeline stock. They are not complicated once you see how the system tracks ownership, stock, and financial impact, but they do require a clear understanding of the master data, movement types, and integration points. Getting them right early in a project saves weeks of rework later when the finance team starts questioning why inventory values look off or why vendor liabilities are appearing in unexpected places.The beauty of these processes is that they follow the same core logic as regular procurement—purchase order, goods movement, invoice—but the system treats ownership, valuation, and stock location differently. In a typical project you will set them up during the blueprint phase, test them thoroughly in integration scenarios, and then train the key users on the exact transactions they will touch every day. Once live, they run quietly in the background, handling thousands of movements without anyone noticing until month-end reconciliation or physical inventory time. The goal here is to walk through each one in the order you usually encounter them in real implementations: first consignment because it is the simplest to explain, then subcontracting because it touches production, and finally pipeline because it is the most different from everything else.