PS 202 · SCHEDULE
When should a project use networks and activities?
Use networks, activities, relationships, milestones, work centers, durations, resources, and components when detailed sequence and execution matter.
READ THE CAPABILITY
Use networks when the project needs executable sequence
WBS elements define accountable scope and cost boundaries; networks and activities add the sequence, dates, relationships, resources, components, and confirmations needed to run detailed work.
The right design is the smallest structure that can explain dependencies and progress. A network is justified when the project must schedule or confirm work at activity level, not simply because a project contains many tasks.
WORKING FLOW
From business decision to controlled evidence
Follow the capability through the records and decisions that make the result explainable.
Define the work package
Set the responsible WBS, outcome, location, acceptance boundary, and level of detail required.
Model executable work
Create activities, relationships, milestones, work centres, components, and external-work boundaries where needed.
Schedule and release
Calculate dates and capacity, resolve predecessors, and release only work that is permitted by project status.
Confirm and replan
Record progress, actual work, delays, remaining effort, and approved change without losing the baseline.
DIAGNOSTIC EVIDENCE
What should be traceable?
When the result looks wrong, start with the last trusted record and follow the owning boundary.
WBS assignment, network and activity type, responsible work centre, component or service requirement, and status.
Relationships, dates, milestones, planned work, capacity assumptions, baseline, and approved constraints.
Release, confirmation, goods or service evidence, delay reason, progress, forecast, and change decision.
SCENARIO
A shutdown must coordinate maintenance work across several teams
The project uses WBS elements for accountable areas, then networks for tasks with dependencies, shared resources, and required completion evidence. A delayed predecessor moves the affected schedule visibly, while unrelated packages retain their own ownership and control boundary.
- 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.
Header- versus activity-assigned networks
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns02Internal, external, service, and cost activities
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns03Relationships, milestones, and scheduling
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patternsSee how this capability changes across valid integration models.