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
- Data model and import order
The tables behind SCM with Demand Forecasting
SCM with Demand Forecasting ships with 31 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 31
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Planning foundations:
Items, planning entities, planning horizons, historical sales and historical adjustments establish the item-market period series.
Forecast modeling:
Forecast models, forecast model runs, Forecasts, seasonality profiles and forecast error metrics keep method, execution and output separate.
Commercial adjustments:
Promotions, promotion uplift, NP is and launch curves retain market assumptions and their period effects.
Consensus planning:
Consensus plans and consensus contributions attach named input to a cycle.
S&OP review:
SOP cycles, SOP meetings, SOP decisions and forecast versions preserve snapshots and decisions.
Supply targets and exceptions:
Exceptions, what if scenarios and safety stock targets connect anomalies, alternatives and item-location targets.
Every table, by feature
- Planning foundations5
- Forecast modeling8
- Commercial adjustments8
- Consensus planning6
- S&OP review8
- Supply targets and exceptions8
- Planning entities
The unique Item x Region x Channel x Customer Segment series that is forecast.
Linked to Users, Items, Planning horizons - Planning horizons
Bucket and rolling-horizon configuration, one per planning program.
Linked to Users - 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.
Linked to Planning entities, Items - Historical adjustments
Outlier removal and promotion-strip adjustments to Historical Sales.
Linked to Users, Historical sales, Planning entities
- Forecast models
Statistical model assigned to a Planning Entity.
Linked to Users, Planning entities - Forecast model drivers
Per-model regressor list.
Linked to Forecast models, Driver data - Driver data
External regressors fed to regression with drivers models.
- Forecast model runs
Execution log per model run per Planning Entity with error metrics.
Linked to Forecast models, Planning entities - Seasonality profiles
Per-Planning Entity seasonal index.
Linked to Planning entities - Seasonal index points
Per-period seasonal index points.
Linked to Seasonality profiles - Forecasts
Per-period forecast number per Planning Entity across the four progressive columns.
Linked to Planning entities, Planning horizons, Forecast model runs - Forecast error metrics
Per-cycle, per-Planning Entity error metrics rolled up across model runs.
Linked to SOP cycles, Planning entities, Forecast versions
- Promotions
Known promotional activity overlaid on the statistical baseline.
Linked to Users, Items - Promotion uplift
Calculated per-Period uplift line written by the promotion uplift workflow.
Linked to Promotions, Planning entities - NP is
New Product Introductions sized by launch curves.
Linked to Users, Items, Launch curves - Launch curves
Reusable ramp-up and churn-down curve templates.
Linked to Users - Launch curve shape points
Per-month relative weight points for a launch curve.
Linked to Launch curves - Items
Read-only shadow of the Item master carried locally for planning references.
- Planning entities
The unique Item x Region x Channel x Customer Segment series that is forecast.
Linked to Users, Items, Planning horizons - Forecasts
Per-period forecast number per Planning Entity across the four progressive columns.
Linked to Planning entities, Planning horizons, Forecast model runs
- Consensus plans
The collaborative plan that walks the S&OP cycle.
Linked to Users, SOP cycles - Consensus contributions
Per-contributor input on the consensus plan.
Linked to Users, Consensus plans, Planning entities - SOP cycles
The monthly S&OP cycle header.
Linked to Users - Planning entities
The unique Item x Region x Channel x Customer Segment series that is forecast.
Linked to Users, Items, Planning horizons - Forecasts
Per-period forecast number per Planning Entity across the four progressive columns.
Linked to Planning entities, Planning horizons, Forecast model runs - Users
Users
Linked to Users
- SOP cycles
The monthly S&OP cycle header.
Linked to Users - SOP meetings
The four meetings that drive a cycle.
Linked to Users, SOP cycles - SOP meeting attendees
Per-meeting attendee list.
Linked to Users, SOP meetings - SOP decisions
Recorded decisions per meeting.
Linked to Users, SOP meetings - SOP decision entities
Per-decision affected Planning Entity list.
Linked to SOP decisions, Planning entities - Forecast versions
Snapshot of all Forecasts rows at each S&OP cycle stage.
Linked to Users, SOP cycles, Forecast versions - Forecast error metrics
Per-cycle, per-Planning Entity error metrics rolled up across model runs.
Linked to SOP cycles, Planning entities, Forecast versions - Consensus plans
The collaborative plan that walks the S&OP cycle.
Linked to Users, SOP cycles
- Exceptions
Flagged anomalies worked off in the Demand Review meeting.
Linked to Users, Planning entities, SOP cycles - What if scenarios
Branch the baseline without mutating it.
Linked to SOP cycles, What if scenarios - What if scenario entities
Per-scenario affected Planning Entity list with quantity impact.
Linked to What if scenarios, Planning entities - Safety stock targets
Calculated safety stock per Item x Location pushed outbound to inventory.
Linked to Items, SOP cycles - Planning entities
The unique Item x Region x Channel x Customer Segment series that is forecast.
Linked to Users, Items, Planning horizons - Items
Read-only shadow of the Item master carried locally for planning references.
- SOP cycles
The monthly S&OP cycle header.
Linked to Users - SOP decisions
Recorded decisions per meeting.
Linked to Users, SOP meetings
Keys and references
Keep item SKU and planning entity code stable across loads. A planning entity links an item to region, channel and horizon; history, model runs and forecasts refer back to it. A forecast period is meaningful only with that entity and horizon. Keep source period and load date on historical sales, and retain the original quantity when recording an adjustment.
Cycle snapshots attach to the S&OP cycle. A contribution attaches to both a consensus plan and a planning entity. A decision attaches to its meeting, while affected entities are recorded separately. Safety stock targets use the item and exact location value. Carry source IDs through any exchange with the item, sales or inventory systems.
Migration order
- Load Users, Items and planning horizons; confirm identifiers, units and calendars.
- Load planning entities and dated historical sales for the selected item-region-channel series.
- Add historical adjustments, model assignments, driver data and seasonal profiles where relevant.
- Review forecast model runs and Forecasts before adding Promotions, NP is and other commercial assumptions.
- Open SOP cycles, consensus plans and meetings, then attach contributions, decisions and versions.
- Reconcile Exceptions and safety stock targets against the published cycle before inventory handoff.
Set up SCM with Demand Forecasting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.