P2M 202 · ANTICIPATE
Demand planning creates a reasoned view of what customers or operations are likely to need.
History, promotions, orders, market intelligence, and forecast models form a baseline that planners review for bias, exceptions, and consensus.
HOW IT WORKS
Expected demand becomes a planning signal
Planning begins before SAP knows exactly what will be sold or consumed. Historical consumption, customer orders, promotions, seasonality, and business knowledge can be combined into a view of future demand. The further into the future planning looks, the less certain individual transactions become, so planning works with forecasts and time periods rather than exact orders.
Concept flow: Forecast or expected demand is progressively replaced by actual demand such as sales orders or dependent requirements.
CAPABILITY MODEL
Understand the input, decision, and result
Read the capability as a connected planning decision before moving into detailed SAP controls.
Business expectation
History, promotions, customer signals, and operational knowledge create an initial view of likely need.
Time-phased demand
Planners review the signal by product, location, period, and version, then align assumptions with the business.
Agreed planning demand
The approved signal becomes an input to material planning until actual demand replaces or changes it.
OPERATIONAL FLOW
How the capability performs
The sequence connects business need to a planning or execution result.
Gather demand signals
Combine relevant history, orders, promotions, seasonality, and market knowledge without treating any one source as the complete answer.
Challenge the baseline
Review bias, exceptions, consensus, horizon, and version so the forecast is a deliberate business view.
Expose the plan
Publish the time-phased demand signal to the planning process and preserve the assumptions behind it.
Learn from actuals
As orders and dependent requirements arrive, compare actual demand with the earlier expectation and replan.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong planning outcome.
Signal design
Planning level, time bucket, key figure, version, and horizon determine what the demand signal means.
Business review
Ownership, consensus, bias review, exceptions, and approval distinguish an agreed plan from an unreviewed forecast.
Demand hand-off
Integration and timing determine when planning demand is available to MRP and how actual demand changes it.
DIAGNOSTIC EVIDENCE
What proves the result?
Use the business input, system objects, and resulting state together.
Forecast or planned demand by material, location, period, version, and quantity.
Sales orders, dependent requirements, consumption, changes, and forecast-versus-actual history.
Owner, review status, assumptions, exceptions, and release or integration evidence.
PLANNING MOMENT
A seasonal product needs more supply before customer orders are visible.
The planner increases the approved period demand, records the seasonal assumption, and sends the signal into material planning. Later sales orders replace part of the expectation and expose the remaining forecast error.
- Assumption is visible
- Demand is time-phased
- Actuals can replace expectation
- Next plan uses the result
IN SAP
Simple representation
These are the main planning objects to recognize before moving into detailed controls.
Forecast or planned demand · PIR where relevant · Actual demand such as sales orders
How SAP controls it
Planning levels, time buckets, key figures, versions, forecast models, and integration to S/4HANA define the usable signal.
A seasonal uplift increases the consensus forecast for fans before the demand reaches material planning.
Connect this capability to the complete execution and integration story.