Released Demand¶

A Released Demand identifies which Demand Plan was official for each sales period. It does not duplicate the forecast: it connects dated Demand Plan versions to inclusive sales ranges so the organization can compare what was planned at the time with what was later sold.

This distinction prevents hindsight. When January sales are evaluated, the comparison uses the plan that was released for January rather than the newest plan available today.

Paths in the platform¶

Header:

Data > Data Operations > Planning Data > Demand Planning > Released Demand > Released Demand

Official plan by sales range:

Data > Data Operations > Planning Data > Demand Planning > Released Demand > Released Demand Item

Structure and key¶

A Released Demand has two connected datasets:

• Released Demand: the header that defines bucket, sales source, optional aggregation levels, and optional collaboration workflow;
• Released Demand Item: the Demand Plan that became official for one inclusive sales range.

The header key is id. The item key is the combination:

releasedDemandId × salesStartDate × salesEndDate

Released Demand — required field¶

Released Demand — optional fields¶

The accepted enum payloads are documented in Planning Bucket Size and Sales History Source. Use the exact English value shown in those articles.

Released Demand Item — required fields¶

There are no optional fields in Released Demand Item, so this dataset has no default-value column.

Example¶

Suppose the monthly forecast is revised every month:

The Demand Accuracy page then compares each month with the version that was genuinely available for that month.

Dependencies¶

• one or more existing Demand Plans;
• a common Planning Bucket Size for the Released Demand and every connected Demand Plan;
• the selected Sales History Source and its transactional sales data;
• Global Planning Parameters when the sales source is not informed;
• optional material and location aggregation levels;
• optional Demand Planning workflow when accuracy must retain each collaboration stage;
• calendar conversion and, when required, temporal split curves for consumers that use a different calendar grain.

Used by¶

• Demand Accuracy, including comparison by workflow stage;
• Supply Planning when the released demand is the official requirement;
• inventory policy and optimization as the expected-demand input;
• plan projections that need to apply the correct Demand Plan only inside its official sales range;
• audit and governance processes that must reproduce what was known at each planning cycle.

Validation rules¶

• id must be filled and unique;
• ranges belonging to the same Released Demand must not overlap;
• salesEndDate must be on or after salesStartDate;
• each range must cover complete buckets: month start to month end, ISO week Monday to Sunday, or the same date for a daily bucket;
• a range may cover more than one complete bucket;
• the Demand Plan and Released Demand must have the same bucket size;
• every informed dependency ID must exist; an unknown ID is an error rather than a fallback;
• changing the bucket is rejected when existing item dates are incompatible with the new bucket.

Edition availability¶

Continue¶

• Measure Demand Plan accuracy
• Understand the Demand Plan
• Configure the Demand Planning workflow
• Demand Planning data model