These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Demand Forecasting
- Features
- Planning foundations
Planning foundations
Define each demand series, its time horizon and the sales history used to plan it.
OverviewActive planning entities×
SCM with Demand Forecasting · Planning foundations
New
Active planning entities
Planning entities
| Entity code | Item | Region | Channel | Customer segment | Horizon | |
|---|---|---|---|---|---|---|
| EC-343 | ITM-6018 | West | Retail | SMB | PH-6041 | |
| EC-884 | ITM-8201 | Central | Wholesale | Mid market | PH-7885 | |
| EC-751 | ITM-7051 | East | Direct | Enterprise | PH-5269 | |
| EC-281 | ITM-3955 | South | Ecommerce | Consumer | PH-7309 | |
| EC-312 | ITM-3052 | National | OEM | Government | PH-5496 |
6 of 6 records
EC-343Planning entities · PE-36806
WestItemITM-6018
ChannelRetail
Customer segmentSMB
HorizonPH-6041
StatusActive
What you can do
Start with a planning entity
Demand planning works at a defined item, region and channel. A customer segment can narrow that series where the business needs a separate forecast. The Demand Planning Manager agrees that grain before opening a cycle, because combining different channels can hide a promotion or a new customer’s effect. Each active planning entity points to an item and a planning horizon; the assigned planner owns the review of that series.
The item record carries its SKU, description, unit, lifecycle stage and active setting. Keep one consistent identifier when loading sales history. A forecast for a mature retail item should not quietly absorb an introduction sold through a different channel. The region and channel values on history and the planning entity help the team check that the periods belong to the intended series.
How the work is organized
- Define the grain. Choose the item, region, channel and optional customer segment that will receive a distinct forecast.
- Set the calendar. Use a planning horizon to choose bucket, bucket count, history lookback, fiscal calendar and currency.
- Review the past. Compare dated shipment or invoice quantities with adjustments that strip a one-time order or promotion effect.
What to agree during setup
Decide which source owns item identity and which shipment or invoice history is authoritative. Record the load source and date. Agree the period cutoff, unit of measure and how backfills will be reviewed. A historical adjustment retains the original and adjusted quantity, reason, method, author and date. It should be possible to explain why a source period changed before the model is rerun.
A paused or retired entity remains visible for analysis, but the team should decide which active entities join the current operating cycle. Demand Planner and Demand Planning Manager should also agree who can change the assigned planner and when the horizon settings may change. A bucket change in the middle of a review makes period comparisons hard to interpret.
Check the handoff on an actual case
Take a finished item sold in the West retail channel. Load several monthly sales periods and identify one unusually large one-time order. The planner records the adjustment against that source sale, then checks that the adjusted history remains tied to the same planning entity. Compare the item, region and channel on the source with those on the entity. Open the next period and confirm the intended horizon and owner are clear. This is a practical way to catch a series mapped to the wrong channel before forecasting starts.
What your team sees
- Active planning entities — The item, region, channel, horizon and assigned planner for each active series.
- My planning entities — The series assigned to the current planner for the next review.
Follow the work through
Continue with baseline preparation and consensus to publication.
What it keeps track of
Data model- Planning entities
- The unique Item x Region x Channel x Customer Segment series that is forecast.
- Planning horizons
- Bucket and rolling-horizon configuration, one per planning program.
- Items
- Read-only shadow of the Item master carried locally for planning references.
- Historical sales
- Cleaned shipment and invoice history the statistical engine trains on.
- Historical adjustments
- Outlier removal and promotion-strip adjustments to Historical Sales.
Who uses it
Permissions- Demand Planning Manager
- Defines scope and ownership.
- Demand Planner
- Reviews history and corrections.
- Sales Rep
- And Marketing Manager use the same entity boundaries when contributing commercial information.
Set up SCM with Demand Forecasting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.