B2A 202 · STRUCTURE
How should the capital project be structured?
Choose WBS-only, network-driven, maintenance-order-supported, or mixed execution without confusing the business outcome with one SAP object.
READ THE CAPABILITY
Choose a structure that can carry work and accountability
Project structure is the translation layer between an approved investment and executable work. WBS elements create accountable scope and cost boundaries; networks and activities add sequence, dates, resources, components, and confirmation detail when the build needs it.
The right design is the smallest structure that can answer the required control questions. A WBS-only build can be sufficient for responsibility and budget, while a network-driven or mixed pattern is justified when dependencies, progress, or technical execution must be planned and evidenced.
WORKING FLOW
From business decision to controlled evidence
Follow the capability through the records and decisions that make the result explainable.
Define delivery packages
Break the approved outcome into responsible work packages, milestones, locations, and acceptance boundaries.
Select execution depth
Choose WBS-only, networks, maintenance orders, or a mixed pattern based on scheduling and technical work needs.
Assign control objects
Align cost collection, procurement, status, dates, responsibility, and settlement relevance to the structure.
Baseline and govern change
Approve the plan, monitor progress and forecast, and preserve an auditable change path when scope moves.
DIAGNOSTIC EVIDENCE
What should be traceable?
When the result looks wrong, start with the last trusted record and follow the owning boundary.
Project profile, WBS hierarchy, network/activity design, responsible owner, location, and status rules.
Dates, dependencies, milestones, planned cost, resource or material assumptions, and approved baseline.
Progress, forecast, commitments, actual cost, change decision, and impact on delivery and capitalization.
SCENARIO
A plant expansion needs both accountability and sequence
The project uses WBS elements for civil works, utilities, and equipment packages, then adds networks only where installation dependencies and confirmations matter. This keeps budget and settlement responsibility clear without forcing every work package into the same scheduling depth.
- Business rule and accountable owner are explicit
- SAP object and source evidence remain connected
- Exception or outcome is reconciled before closure
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
Delivery breakdown and accountability
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns02Scheduling and milestone depth
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns03Cost-object and status design
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patternsSee how this capability changes across valid integration models.