Demand Plans
A named, dated statement of what is expected. Versioned rather than overwritten: last month plan is what this month accuracy is measured against, and editing one in place destroys the only evidence anybody has.
Where to find it
- Module: Supply Chain
- Group: Planning
- Section: Demand Planning
- Screen: Demand Plans
Address in the console: /scm/demand-plans
List · 13 columns · 17 fields on its form · 5 of them required · 6 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Plan | Code | plan_no |
| Name | Text | name |
| Version | Number | version |
| Type | Status | plan_type |
| Grain | Status | bucket |
| From | Date | horizon_from |
| To | Date | horizon_to |
| Model | Text | model_name |
| Items | Number | item_count |
| Quantity | Number | total_quantity |
| Error % | Number | mape |
| Bias % | Number | bias_pct |
| Status | Status | status |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Name required | Text | ||
| Version | Number | ||
| Supersedes | Choice | Looked up from existing records | |
| Type required | Choice | statistical, consensus, budget, sales, marketing, collaborative, scenario, baseline | |
| Grain required | Choice | Configuration list | A weekly plan and a monthly plan are different documents, and adding them together is the classic way to double-count. |
| Plan from required | Date | ||
| Plan to required | Date | ||
| History from | Date | ||
| History to | Date | ||
| Warehouse | Choice | Looked up from existing records | |
| Location | Choice | Looked up from existing records | |
| Category | Choice | Configuration list | |
| Customer | Choice | Looked up from existing records | |
| Forecast model | Choice | Looked up from existing records | |
| Currency | Choice | Configuration list | |
| Owner | Choice | Looked up from existing records | |
| Notes | Long text |
What you can do here
Calculate primary
Run the statistical forecast
Asks for: Overwrite manual overrides too
Score it
Measure how good it turned out to be
Send for review
Asks for confirmation: Send this plan for review? Somebody other than you approves it.
Approve primary
Asks for confirmation: Approve these numbers as the agreed demand? Recalculating later clears the approval.
Send back
Send it back to the planner
Asks for: Why*
Publish primary
Asks for confirmation: Publish this plan as the number of record? The version it supersedes steps down, and a published plan is not recalculated — copy it to a new version instead.
* required
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.