Demand Planning workflow¶
The workflow models how a statistical baseline becomes consensus demand. It organizes stages, responsibilities, and editable series.
Path in the platform¶
Data > Data Operations > Configuration > Demand Planning > Workflow Design > Demand Plan Workflow
Objects and fields¶
Workflow¶
| Field | Required? | Meaning |
|---|---|---|
| ID | Yes | Stable key |
| Description | No | Process purpose |
| Active | No | Availability for new cycles |
Stage¶
| Field | Required? | Meaning |
|---|---|---|
| ID | Yes | Stage key |
| Position | Yes | Deterministic order |
| Description | No | Review role |
| Adjustment key figure | Yes | Series receiving the delta |
| Owner | No | Authorized role or audience |
| Completion rule | No | Completion and handoff criterion |
Stage key figures¶
Each stage declares visible series, their order, and permission. Baseline, actuals, prior adjustment, current adjustment, and resulting total must be visually distinct.
Dependencies¶
- Materials, Locations, and periods used by filters and views.
- Key figures, permissions, and roles available to the process.
- Each stage's order, closing rule, and adjustment destination.
- Configured Planning Views that select the stage when opening the Planning Book.
- Released Demand when the released version must retain the workflow used for stage-level reading or accuracy.
Used by¶
- stage instantiation in the Demand Plan;
- Demand Plan collaboration;
- control of visible and editable series by stage;
- change history with value, author, time, and rationale;
- consensus-demand consolidation and release.
- Demand Accuracy, which compares the incremental contribution of each stage.
Integrity¶
- positions do not repeat;
- a stage has one unambiguous adjustment destination;
- protected series are not editable;
- aggregate changes have a disaggregation rule;
- closing a stage does not erase earlier stages;
- conflicts have an explicit precedence rule.