Skip to content

Demand Planning execution profile

An execution profile groups reusable parameters that identify how a Demand Planning cycle opens and is governed. It defines the historical source, planning calendar, reference unit, and manual-edit window. The selected calendar determines buckets and horizon.

The profile does not contain clusters, model-history depth, the aggregation/disaggregation rule, or collaboration stages. Those settings have their own contracts and are connected to the profile during execution.

Path in the platform

Demand Planning > Configuration > Execution Profiles

This setting is not maintained under Data; it belongs to the Demand Planning functional area.

Grain and key

One row represents one reusable profile identified by id.

The same profile can originate multiple Demand Plans. Changing its configuration affects future runs; it does not silently rewrite plans already generated.

Required fields

Field Meaning
id Stable, unique profile identifier with at most 50 characters
calendarProfileId Identifier of an existing calendar profile, selected in Calendar profile

Optional fields

Field Meaning Default Value When Not Provided
description Human-readable name shown to the planner The profile id when created through the screen
historicalSalesDocumentType Sales History Source used by the process Sell-out
constrainPlanEditPeriods Whether manual editing is limited to a window false: open editing
initialPlanEditPeriod First editable relative period; 1 is the plan's first bucket No initial limit
finalPlanEditPeriod Last editable relative period No final limit
defaultDemandPlanningUomId Unit suggested when configuring cluster parameters Demand Planning default unit in Global Parameters
mapeMaterialAggregationLevelId Enterprise material level used to consolidate MAPE errors and run HTS No level selected
mapeLocationAggregationLevelId Enterprise location level used to consolidate MAPE errors and run HTS No level selected
defaultAutoTunedDemandPlanConfigurationId Enterprise AutoFit model promoted as the profile default No default model on a new profile; an update without a promotion command preserves the current default

Availability by edition

Capability Community Enterprise
Identity, description, calendar, and edit window Available Available
Profile default unit Available Available
Historical sales source Sell-out only Sell-out, Sell-in, and Sales Orders
Material and location levels for MAPE/HTS Unavailable Available
Default AutoFit model selection Unavailable Available

Parameters used to generate an AutoFit model — strategy, objective function, backtest periods, lag, and tree settings — belong to the AutoFit run, not to the profile. The Enterprise profile only selects a model that has already been generated and promoted as its default.

What is configured elsewhere

Decision Correct configuration
Plan buckets and horizon Calendar profile associated through calendarProfileId
Which materials and locations form each cluster Forecast clusters
Forecast level, history, aggregation, disaggregation, and manual parameters Cluster-level configuration
AutoFit generation, backtests, and candidate selection Cluster-level AutoFit
Collaboration stages, key figures, and owners Demand Planning workflow

Calendar and read compatibility

Create or select the calendar before saving an execution profile. A simple monthly calendar with 12 periods uses type = SIMPLES, baseBucketSize = Monthly, and numberOfBasePeriods = 12 in the calendar record. The execution profile receives the calendarProfileId association; do not duplicate bucket and horizon as independent profile settings.

Reading an execution profile may return bucketSize and planningHorizonInPeriods for compatibility. These values are derived from the selected calendar. The calendar's firstPeriodBucketSize read value is also derived and must not be edited as a separate bucket definition.

Chapter 5 of the Community tutorial applies the monthly calendar to the demand profile. When reusing a calendar across Demand Planning and Supply Planning profiles, check the effect of calendar changes on future runs of both profiles.

Edit-window behavior

When constrainPlanEditPeriods is true, both bounds must form a valid window. Periods are relative to the beginning of the Demand Plan:

  • 1 is the first bucket;
  • 2 is the second bucket;
  • and so on.

If the restriction is disabled or the bounds are absent or inverted, the plan is created without a limited edit window.

Dependencies

Used by

  • official Demand Planning execution;
  • Demand Plan creation and identity;
  • historical-sales source selection in the sales projection;
  • editable-date materialization in the Planning Book;
  • initial unit selection in cluster-level configuration;
  • Enterprise MAPE/HTS assignment resolution;
  • Enterprise default AutoFit-model resolution, without a persisted inverse relationship on the profile.

Validations

  • id present, unique, and no longer than 50 characters;
  • calendarProfileId is present and identifies an existing calendar;
  • a valid calendar, including a positive period count and a recognized bucket when using the simple type;
  • historical source available in the selected edition;
  • referenced UOM exists;
  • coherent edit bounds when the window is enabled;
  • referenced MAPE levels exist and are compatible when selected;
  • default AutoFit model exists, is complete, and belongs to the same profile.

Continue