Project Procurement: WBS, Networks, PRs and Commitments (Part 2)
Integrate SAP PS with MM procurement so project demand creates traceable purchase requisitions, purchase orders, commitments and actual cost against the correct project object.
Explanation
📌 KEY POINTS
✅ A PR is planned demand; a PO is a converted commitment — both stay visible to project cost control.
⚠️ A project can look "under budget" while unbilled POs already consume the remaining capacity.
💡 Procurement lead time belongs IN the schedule, not outside it.
━━━━━━━━━━━━━━━━━━━━
▶ 1. THE COMMITMENT LIFECYCLE
- A purchase requisition represents planned external demand
- Converted to a purchase order → the commitment changes form but remains visible to cost control
- Goods receipt, service entry, and invoice posting move cost through the lifecycle
━━━━━━━━━━━━━━━━━━━━
▶ 2. WHERE REQUIREMENTS ORIGINATE
- WBS or network activities, depending on process design
- Account assignment ensures commitments and actuals flow to the correct project object
━━━━━━━━━━━━━━━━━━━━
⚠️ 3. THE BUDGET ILLUSION
- A project may appear under budget while unbilled purchase orders already consume the remaining capacity
- Monitor commitments AND actual costs — not actuals alone
━━━━━━━━━━━━━━━━━━━━
▶ 4. SCHEDULING INTEGRATION
- Procurement lead time should be reflected in network or project scheduling
- Material arriving after the activity that needs it is a schedule failure, not just a procurement one
✅ CHECKPOINT: explain how a project can be "under budget" and still be at real risk.
Real project scenario
A project manager approved new subcontract work because actual cost was low, but existing POs had already consumed the remaining budget. Commitment-aware project reporting prevented further overspend.
Common mistakes
- Looking only at actual cost.
- Using wrong WBS or network account assignment.
- Ignoring procurement lead time.
- Closing project objects with open POs.
- Treating PR/PO integration as only an MM issue.
Best practices
- Monitor commitments.
- Validate account assignment.
- Align procurement and project dates.
- Reconcile open POs before closure.
- Keep PS and MM ownership aligned.
Interview angle
Trace project requirement → PR → PO → receipt/service → invoice → project actual cost.
Practice this lesson
Quick check
1. A project team faces this situation in "Project Procurement: WBS, Networks, PRs and Commitments": A project manager approved new subcontract work because actual cost was low, but existing POs had already consumed the remaining budget. Which action is the most appropriate next step?
2. When a purchase requisition item linked to a network activity is converted into a purchase order, what happens to the commitment shown in project cost reporting?
3. Which standard report is typically used to display purchase orders that have been assigned to WBS elements or network activities of a specific project?
Interview questions
1. A production issue is reported in Project Procurement around Project Procurement: WBS, Networks, PRs and Commitments. How would you troubleshoot it systematically and avoid the common failure patterns?
Answer it in your own words first, then compare.
2. Describe the procurement lifecycle for an externally procured material required for a project, from the initial requirement to the final actual cost posting. How does the system help in tracking costs throughout this process?
Answer it in your own words first, then compare.
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.