PSbeginner
Work Breakdown Structure
Learn SAP Project System WBS design as the stable project-control hierarchy for scope, responsibility, planning, budgeting, account assignment, settlement and reporting. Focus on choosing the right granularity rather than modeling every task as a WBS element.
Overview
Learn SAP Project System WBS design as the stable project-control hierarchy for scope, responsibility, planning, budgeting, account assignment, settlement and reporting. Focus on choosing the right granularity rather than modeling every task as a WBS element.
Lessons in this topic
- WBS Design: Project Definition, Hierarchy and Account AssignmentDesign a Project System WBS as the stable project-control hierarchy for scope, responsibilities, dates, planning, budgeting, account assignment and reporting rather than mirroring every task in the schedule.
Interview questions covered
- What are the core concepts of Work Breakdown Structure, and how would you explain them clearly in an SAP interview?
- How would you apply Work Breakdown Structure in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Work Breakdown Structure. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Work Breakdown Structure?
- Suppose you inherit an existing Work Breakdown Structure solution. How would you review it before making a change?
- You are the senior consultant/architect responsible for WBS Design: Project Definition, Hierarchy and Account Assignment. The project situation is: A project created one WBS element per engineering task, producing 12,000 account-assignment objects and unusable reports. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?