Material procurement for projects connects project-specific needs in SAP Project System with the purchasing and inventory processes that secure materials on time. A requirement may originate from a WBS element or a network activity; how the material is assigned and procured affects purchase requisitions, reservations, project stock, delivery timing, commitments and actual costs. The central business question is not only whether a buyer has placed an order, but whether the right material will be usable for the right project activity when it is needed.
Why a project needs different procurement decisions
Routine replenishment can serve recurring warehouse demand. A project may instead require one-off engineered components, site-specific deliveries and a committed installation date. A missing cable, valve or specialized item can delay an entire network of dependent activities. Project managers need purchasing visibility; buyers need the correct project account assignment; controllers need reliable cost attribution. SAP PS bridges these views rather than replacing Materials Management.
Where demand is defined: WBS and network activities
A WBS element defines a piece of project scope and responsibility. A network activity expresses work and scheduling relationships. Materials linked to network activities can use planned consumption dates to align purchasing and supply. The document trail depends on how the material component and project stock settings are configured: a reservation, a purchase requisition, or both may become relevant. Some purchases can also be assigned directly to a WBS element. Do not assume that every project material follows a single automatic path.
Stock material versus direct project procurement
For commonly stocked material, an internal reservation or stock withdrawal may be appropriate. For specialized or externally sourced material, requirements can trigger purchase requisitions and subsequent purchase orders. Non-stock consumption items and external services have their own receiving and account-assignment rules. SAP Help identifies network material-component settings, the material master procurement type and project stock indicators as controls that influence this route.
What the document chain tells the team
A requirement describes the need; a purchase requisition requests purchasing action; a purchase order creates an external commitment; a goods receipt documents delivered material where applicable; and accounting captures the relevant financial effects. A buyer can report a purchase order as placed while the construction team still has no usable stock at site. Project tracking therefore separates ordered, delivered, received and usable quantities. SAP's Manage Project Procurement documentation describes monitoring requisitions, orders and delivered-versus-ordered quantities by project or WBS.
A practical example: a valve before commissioning
Consider a plant project that needs a calibrated valve before commissioning. Engineering identifies the specification, project planning sets the activity's need date, and procurement confirms supplier lead time. If the requested valve will arrive after the commissioning dependency, project management must consider approved alternatives: expedited sourcing, rescheduling, substitute stock if technically accepted, or a formally agreed scope change. A premature goods receipt or an unsupported promise from the supplier does not solve the real dependency. The receipt and final project cost must still be traceable to the proper project object.
Procurement commitments are not the same as project actual costs
A purchase order can contribute to a project commitment before the financial postings represented by delivered goods or an invoice occur. Controllers review commitments alongside actual costs, especially where a budget or availability-control framework applies. When a requisition is converted to a purchase order, the team must avoid reading the same demand twice as two separate obligations. Delivery timing and value evidence belong to different questions and should be reviewed together.
Decisions and controls a consultant should clarify
Ask whether demand is tied to a WBS or a network activity, whether project stock is intended, whether the item is stock or non-stock, how dates will be derived, who may change quantities, and how account assignments are validated. Then establish who follows up requisitions, approves orders, records goods movements, investigates shortages and reconciles commitments to costs. Distinguish material physically at a site from material available and approved for use.
Common misunderstandings
“A purchase order means the material is ready.” It only establishes an order; promised, delivered and accepted quantities may differ. “All project procurement hits the project the same way.” Stock, consumption, direct procurement and service routes differ in their documents and accounting behavior. “Project scheduling and purchasing are separate.” A late component can change activity dates and handovers. The exact integration behavior depends on the SAP product version and configuration.
Read next
Explore network activities, project scheduling, project commitments, and actual project costs. Return to SAP PS / EPPM.