Supply Plans
What would have to happen for the demand to be met. An INFINITE run assumes the factory can do whatever the plan asks; a FINITE one does not, and comparing them is exactly how a planner finds the bottleneck.
Where to find it
- Module: Supply Chain
- Group: Planning
- Section: Supply Planning
- Screen: Supply Plans
Address in the console: /scm/supply-plans
List · 14 columns · 20 fields on its form · 5 of them required · 2 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 |
| Type | Status | plan_type |
| Capacity | Status | capacity_mode |
| Grain | Status | bucket |
| From | Date | horizon_from |
| To | Date | horizon_to |
| Items | Number | items_planned |
| Proposed | Number | orders_proposed |
| Firmed | Number | orders_firmed |
| Exceptions | Number | exceptions_raised |
| Overloads | Number | capacity_overloaded_periods |
| Ran in (s) | Number | run_seconds |
| 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 | ||
| Type required | Choice | mrp, mps, drp, rough_cut, simulation, what_if | |
| Capacity required | Choice | Configuration list | Infinite is fast and optimistic. Finite respects the calendars and pushes work later rather than pretending. |
| Scheduled | Choice | forward, backward, bidirectional | |
| Demand plan | Choice | Looked up from existing records | |
| Grain | Choice | day, week, month | |
| Plan from required | Date | ||
| Plan to required | Date | ||
| Frozen until | Date | Inside this window the plan changes nothing, because the work has started. Without it a re-run reschedules the job that is on the machine right now. | |
| Warehouse | Choice | Looked up from existing records | |
| Location | Choice | Looked up from existing records | |
| Category | Choice | Configuration list | |
| Include the forecast | Yes or no | ||
| Respect safety stock | Yes or no | ||
| Count what is already on order | Yes or no | ||
| Apply lot sizing | Yes or no | ||
| Currency | Choice | Configuration list | |
| A what-if — may not be firmed | Yes or no | ||
| Compare against | Choice | Looked up from existing records | |
| Notes | Long text |
What you can do here
Run it primary
Asks for confirmation: Net demand against supply and propose planned orders? Nothing is ordered and no money is committed.
Firm a batch
Turn proposals into real documents
Asks for: Only Wanted on or before
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.