Manufacturing › Plan
Material Planning
What the netting run decided, ranked by what each exception costs. The run itself is Supply Chain’s — these are its records seen from the plant.
In Manufacturing → Plan · 6 screens
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Planning Workbench | Workspace | What a planner actually opens: not four thousand planned orders, but the exceptions ranked by what each one costs. The first twenty rows are the morning. | 0 | 0 | 0 |
| Supply Plans | Read-only list | The netting runs, seen from the plant. Supply Chain owns the engine — a second one would be a second answer to "what should we build". Read-only here. | 10 | 0 | 0 |
| Planned Orders | Read-only list | What the run proposed. Firming a make proposal here creates the works order and records why — which is the one thing the planning table cannot keep. | 9 | 0 | 1 |
| Planning Exceptions | Read-only list | What the run wants somebody to look at. A run that produced four thousand orders and no exceptions has told nobody anything. | 8 | 0 | 0 |
| Planning Decisions | Read-only list | Why a planner firmed a proposal early, split it, or moved it. The planning table records that it was firmed; only this records the judgement, which is the whole content of a planner’s day. | 10 | 0 | 0 |
| Low-Level Codes | Read-only list | The deepest level each item appears at, which is what makes a netting run process components after their parents. A circular structure is flagged rather than thrown. | 8 | 0 | 1 |