Skip to content

Demand Planning data model

The Demand Planning core is a time series identified by:

material × location × period

Master data defines dimensions, history provides observations, configuration defines calculation, Demand Plans persist output, and workflows organize collaboration.

Main relationships

Origin Relationship Destination
Sell-out references material, selling location, unit, and date
Sell-in references material, origin, destination, unit, and date
Material cluster groups materials by rule or characteristic
Location cluster groups locations by rule or characteristic
Global Parameters provide fallback for unit, history source, and other settings
Execution profile defines historical source, bucket, horizon, unit, edit window, and Enterprise links
Cluster-level configuration defines statistical model, aggregation, split, history, and unit for each profile and cluster pair
AutoFit evaluates candidates for each cluster pair
Demand Plan produces material/location/period lines
Released Demand assigns the official Demand Plan to each inclusive sales range
Workflow organizes stages and key figures selected by collaboration views
Configured Planning View presents and governs input for one user's Demand Planning Book

Transformation flow

  1. Load materials, locations, and units under Data.
  2. Load sales referencing those keys.
  3. Group materials and locations into clusters.
  4. Define source, bucket, horizon, unit, and edit window in the profile.
  5. Configure model, aggregation, split, history, and unit for each cluster pair.
  6. In Enterprise, an approved AutoFit model can resolve the effective winner for each pair.
  7. Run and persist material/location/period lines.
  8. Open the plan through a configured view and add traceable collaboration adjustments.
  9. Assign official versions to sales ranges through Released Demand.
  10. Measure actual accuracy and the contribution of each workflow stage.

Integrity rules

  • every sale needs valid material, location, date, and quantity; its unit can be supplied on the row or resolved from Global Parameters;
  • an ID must keep the same meaning through history;
  • unit conversion must exist before calculation;
  • clusters must cover the planned scope without ambiguity;
  • the latest historical period must be closed;
  • plan lines preserve their originating version;
  • collaboration never silently replaces the baseline.
  • official sales ranges do not overlap and use Demand Plans with the same bucket size.

Continue