# Master Plan — build the plan for a Plan Month, group SO lines into Big Plans (Style + Model + Base Color + SPRAY/Logo + Area), one Work Order per Big Plan, release the Work Orders directly to I/J Plan

> Fine Chemical (FC) · MES module · v0.7 · 01/10/2026 · Standard flow — for implementation, testing and development
>
> Generated from the diagram by `sync.js` — do not edit by hand. The diagram is authoritative: report any mismatch with the diagram page.
>
> Diagram page: /en/mes/master-plan

## How to read

- Every box on the diagram has a code `Bxx`, numbered in flow order (from the start event, following the arrows).
- "Goes to" lists every arrow leaving the box; text in square brackets is that arrow's condition label.
- "Optional branch" = a dashed arrow on the diagram: may be done or skipped.
- "Data" boxes in the Input lane are incoming data; in the Output lane they are results / end points of the flow.

## Process Flow (swimlane)

### Roles (lanes)

- Input
- Planner
- Output

### Steps

| Code | Role | Type | Content | Platform · Screen | Goes to |
| --- | --- | --- | --- | --- | --- |
| B01 | Input | Data | Sales Order (lines per size, ship-to Country) |  | B06 |
| B02 | Input | Data | Internal Production Request |  | B08 |
| B03 | Input | Data | Master data: Country (Area) | Master data | B11 |
| B04 | Input | Data | Master data: Item · Routing · Routing Mapping | Master data | B13 |
| B05 | Input | Data | Master data: Machine · Capacity Calendar | Master data | B14 |
| B06 | Planner | Start | Start |  | B07 |
| B07 | Planner | Task | Open the Create Plan wizard | Web · Master Plan | B08 |
| B08 | Planner | Task | Select SO size lines | Web · Master Plan | B09 |
| B09 | Planner | Task | Enter Plan Qty per line | Web · Master Plan | B10 |
| B10 | Planner | Task | Select Plan Month | Web · Master Plan | B11 |
| B11 | Planner | Task | Group SO lines into Big Plan | System (auto) · Master Plan | B12 |
| B12 | Planner | Task | Calculate Common Stock | System (auto) · Master Plan | B13 |
| B13 | Planner | Task | Pick a Routing for each Work Order | Web · Master Plan | B14 |
| B14 | Planner | Task | Calculate Plan From / To from lead time | System (auto) · Master Plan | B15 |
| B15 | Planner | Decision | Any process over Capacity? |  | B16 [Yes]; B17 [No] |
| B16 | Planner | Task | Flag Over capacity | System (auto) · Master Plan | B17 |
| B17 | Planner | Task | Create Master Plan | Web · Master Plan | B18 |
| B18 | Planner | Task | Generate Work Order per Big Plan | System (auto) · Master Plan | B19 |
| B19 | Planner | Task | Release Work Order | Web · Master Plan | B20 |
| B20 | Planner | Task | Send WOs to I/J Plan | System (auto) · Master Plan | B21 |
| B21 | Planner | Task | Create NEW plans for each planned process | System (auto) · Master Plan | B22; B23 |
| B22 | Output | Data | Plan RELEASED · Work Order RELEASED → I/J Plan (one row one Detail Plan, grouped into Big Plan I/J) + NEW Trimming / Spray Out / Packing + Common Stock (surplus) |  | (end) |
| B23 | Planner | End | End |  |  |
| B24 | Planner | Start | Drop the plan |  | B25 |
| B25 | Planner | Decision | Plan currently in which status? |  | B26 [DRAFT]; B27 [RELEASED] |
| B26 | Planner | Task | Delete Master Plan | Web · Master Plan | B28 |
| B27 | Output | Data | No delete in Master Plan — handled at Work Order |  | (end) |
| B28 | Planner | Task | Restore SO line Remaining | System (auto) · Master Plan | B29; B30 |
| B29 | Output | Data | SO Remaining restored |  | (end) |
| B30 | Planner | End | End |  |  |
| B31 | Planner | Start | ETD needs changing |  | B32 |
| B32 | Planner | Task | Enter new Current ETD | Web · Master Plan | B33 |
| B33 | Planner | Task | Build Reschedule Preview | System (auto) · Master Plan | B34 |
| B34 | Planner | Decision | Planner picks which action? |  | B35 [Apply Reschedule]; B36 [Save as Simulation]; B37 [Cancel] |
| B35 | Planner | Task | Apply new schedule | System (auto) · Master Plan | B38 |
| B36 | Planner | Task | Save Simulation | System (auto) · Master Plan | B39; B40 |
| B37 | Output | Data | Keep ETD and process schedule |  | (end) |
| B38 | Output | Data | New Current ETD + rescheduled process dates |  | (end) |
| B39 | Output | Data | Simulation copy · live schedule unchanged |  | (end) |
| B40 | Planner | End | End |  |  |

### Step details (hover content on the diagram)

#### B07 · Open the Create Plan wizard

- Planner · Web · Master Plan
- Comes from: B06
- Goes to: B08 · Select SO size lines

> The Planner opens the Master Plan creation wizard from the plan list.  
> Action: Master Plan › Plan List › "Create Plan" button.  
> System: Plan List has an "Area" field outside the grid (All / Europe / Asia / America) to filter plans — a plan shows when at least one SO line ships to a Country in that Area; the "Area" column lists the Areas of the plan's SOs.  
> Result: opens the 3-step wizard "Sales Orders" · "Items" · "Review".  
> Test:  
> - Filter "Area" = Asia → only plans with SO lines shipping to a Country in Asia remain  
> Open: the real Area list in Master Data Country — prototype v0.56 uses sample data by continent.  
> Source: Q-20261001-04 · prototype v0.12 · v0.22 · v0.56  

#### B08 · Select SO size lines

- Planner · Web · Master Plan
- Comes from: B02, B07
- Goes to: B09 · Enter Plan Qty per line

> The Planner selects the Sales Order lines, per size, to put into the plan.  
> Action: Step 1 "Select SO Lines" › tick lines; each size (W5–W11) is one line ("Each shoe size (W5–W11) is its own item line").  
> System: each line shows "ORDERED" · "REMAINING" · "PLAN QTY" and the ship-to Country · Area (Area looked up from the Country in Master Data Country); Internal Production Requests can be selected too.  
> Source: BRD §6.1 · Q-20260918-29 · Q-20261001-04 · prototype v0.22 · v0.56  

#### B09 · Enter Plan Qty per line

- Planner · Web · Master Plan
- Comes from: B08
- Goes to: B10 · Select Plan Month

> The Planner enters the production quantity for each selected line.  
> Action: the "PLAN QTY" cell of each line.  
> System: defaults to the line's "REMAINING"; entering more than Remaining is allowed, the excess becomes Common Stock.  
> Test:  
> - Remaining 100, enter 120 → saved, Common Stock = 20  
> Source: BRD §6.1 · Q-20260923-03  

#### B10 · Select Plan Month

- Planner · Web · Master Plan
- Comes from: B09
- Goes to: B11 · Group SO lines into Big Plan

> The Planner picks the production month (Plan Month) for the whole Master Plan.  
> Action: Step 2 "Item Lines" › "Plan Month" field ("Master plan is built for production month <yyyy.mm>").  
> System: a Master Plan has exactly one Plan Month; on Release every WO of the plan gets "P.O (Month)" = Plan Month; changing the Plan Month while the plan is DRAFT changes the P.O Month, after Release it does not change.  
> Blocked when: no Plan Month selected → the plan cannot be created.  
> Test:  
> - Plan Month 2026.10 → every WO of the plan has "P.O (Month)" 2026.10  
> - SO lines needed for month 2026.11 → build another Master Plan  
> Open: the message when no Plan Month is selected does not exist yet; prototype v0.56 does not yet save the Plan Month to the plan / WO.  
> Source: Q-20261001-03 · prototype v0.51 · v0.56  

#### B11 · Group SO lines into Big Plan

- Planner · System (auto) · Master Plan
- Comes from: B03, B10
- Goes to: B12 · Calculate Common Stock

> The system groups the selected size lines into Master Plan Big Plans; each Big Plan becomes one Work Order.  
> System: grouping key = Style + Model + Base Color + SPRAY/Logo + Area. Style, Model, Base Color, SPRAY/Logo are Item attributes of the line; Area is the Area of the ship-to Country on the SO line, looked up in Master Data Country. The Plan Month is shared by the whole plan, so every Big Plan has the same month.  
> Result: Step 2 "Item Lines" shows one row per Big Plan, one column per size, with chips Style · Color · SPRAY/Logo · Area (Country); text "Selected SO lines are consolidated into n Big Plan(s) by Style + Model + Base Color + SPRAY/Logo + Area".  
> Test:  
> - Same Sandal Black, one SO shipping to DE (Europe), one to JP (Asia) → 2 Big Plans  
> - Same Style, Model, Base Color, SPRAY/Logo, Area; different SOs or different Countries in the same Area → 1 Big Plan  
> - Same Style, Model, Base Color, Area; one SPRAY line, one Logo line → 2 Big Plans  
> Open: block ticking an SO line whose Country has no Area — proposal, not confirmed; within one Area, does the WO show Destination "Mixed" or split by Country (OQ-12).  
> Source: Q-20261001-04 · Q-20261001-02 (D1) · prototype v0.56  

#### B12 · Calculate Common Stock

- Planner · System (auto) · Master Plan
- Comes from: B11
- Goes to: B13 · Pick a Routing for each Work Order

> The system calculates the surplus quantity not tied to any order.  
> System: Common Stock = Plan qty − total allocated to SO lines.  
> Result: the surplus goes with the Work Order created with the plan.  
> Test:  
> - Plan qty 500, SO allocation 480 → Common Stock = 20  
> Source: BRD §6.1 · BRD §9  

#### B13 · Pick a Routing for each Work Order

- Planner · Web · Master Plan
- Comes from: B04, B12
- Goes to: B14 · Calculate Plan From / To from lead time

> The Planner picks the Routing (process sequence) for each Work Order to be created.  
> Action: Step 3 "Review & Create" › Work Order card (WO-NEW-nn) › "Routing" field.  
> System: defaults to the item's default routing from Routing Mapping; can be changed to another routing. Process table: "Seq" · "Code" · "Process" · "Lead" · "Plan From" · "Plan To" · "Source".  
> Open: the routing picked in Step 3 is not yet carried to the Work Order screen on the prototype (OQ-49).  
> Source: prototype v0.16  

#### B14 · Calculate Plan From / To from lead time

- Planner · System (auto) · Master Plan
- Comes from: B05, B13
- Goes to: B15 · Any process over Capacity?

> The system calculates each process start / end date from its lead time.  
> System: Plan To = Plan From + Lead Time − 1; next process Plan From = Plan To + Buffer Days. Changing the Routing rebuilds and recalculates the process table.  
> Test:  
> - Plan From 01/10, Lead Time 3 → Plan To 03/10  
> Source: BRD §6.1 · prototype v0.16  

#### B15 · Any process over Capacity?

- Planner
- Comes from: B14
- Goes to [Yes]: B16 · Flag Over capacity
- Goes to [No]: B17 · Create Master Plan

> The system compares each process load with the machine / work center capacity.  
> Yes: load exceeds the Capacity Calendar → flag Over capacity.  
> No: create the plan as normal.  
> System: Plan List has a "Capacity" column and an "Over Capacity" quick filter.  
> Source: BRD §6 step 4 · BRD §9  

#### B16 · Flag Over capacity

- Planner · System (auto) · Master Plan
- Comes from: B15
- Goes to: B17 · Create Master Plan

> The system flags the plan as Over capacity.  
> Result: warning only — does not block creating or releasing the plan; the Planner decides to reduce load or release anyway.  
> Test:  
> - Plan over capacity → "Create Plan" and "Release Work Order" still allowed, with a warning  
> Source: Q-20260923-02 · Q-20260924-04  

#### B17 · Create Master Plan

- Planner · Web · Master Plan
- Comes from: B15, B16
- Goes to: B18 · Generate Work Order per Big Plan

> The Planner creates the Master Plan as a draft.  
> Action: Step 3 › button "Create Plan".  
> Result: plan → DRAFT, editable until Release; the system immediately creates one Work Order per Big Plan in the next step.  
> System: Master Plan does not check materials — this is done in I/J Plan · Compound Calculate.  
> Test:  
> - Click "Create Plan" → plan DRAFT, toast "created as Draft — review it, then Release Work Order (no approval step)"  
> Source: prototype v0.22 · v0.28 · Q-20260923-19 (E) · Q-20260924-04 · Q-20261001-04  

#### B18 · Generate Work Order per Big Plan

- Planner · System (auto) · Master Plan
- Comes from: B17
- Goes to: B19 · Release Work Order

> The system creates one Work Order per Big Plan as soon as the Master Plan is created.  
> Result: one WO per Big Plan (running WO number), status NOT RELEASED, carrying the Routing and process schedule chosen in Step 3; Common Stock goes with the WO.  
> System: the WO carries the Big Plan key ("Style", "Model", "Base Color", SPRAY/Logo, Area) so each field has a single value; "P.O (Month)" = the Master Plan's Plan Month; "Destination" takes the SO line Country, shown as "Mixed" when several Countries of one Area are combined; "Start I/J Date" / "I/J ETC" = Plan From / Plan To of the Injection process.  
> Result: a NOT RELEASED WO is not yet in I/J Plan; it is visible in Plan List (expand icon in the "WO" column) and Plan Details › tab "Work Orders".  
> Test:  
> - Selected SO lines group into 7 Big Plans → "Create Plan" → Plan List expands to 7 NOT RELEASED WOs; I/J Plan has no row yet  
> Open: when a DRAFT plan is edited, are the WOs recreated or updated — no source yet; prototype v0.56 does not yet write the Plan Month to the WO.  
> Source: Q-20260924-08 · Q-20261001-03 · Q-20261001-04 · prototype v0.30 · v0.56  

#### B19 · Release Work Order

- Planner · Web · Master Plan
- Comes from: B18
- Goes to: B20 · Send WOs to I/J Plan

> The Planner releases the plan's Work Orders directly — there is no approval step.  
> When: plan is DRAFT.  
> Action: "Release Work Order" button.  
> Result: plan → RELEASED; every WO of the plan NOT RELEASED → RELEASED; the WO "P.O (Month)" is fixed to the Plan Month and does not change after Release; from now on the plan cannot be edited or deleted in Master Plan.  
> Open: BRD §7 has the Production Supervisor "Approve" "Create / revise Work Order" and "Release WO / Generate WI" — to be confirmed with the customer or the BRD updated.  
> Test:  
> - DRAFT plan → "Release Work Order" works immediately, with no waiting-for-approval status  
> - RELEASED plan → no "Release Work Order" button  
> Source: Q-20260924-04 · Q-20261001-03 · BRD §6.1 Step 5  

#### B20 · Send WOs to I/J Plan

- Planner · System (auto) · Master Plan
- Comes from: B19
- Goes to: B21 · Create NEW plans for each planned process

> The system sends the newly released Work Orders to I/J Plan for injection planning.  
> Result: each WO becomes one Detail Plan in I/J Plan, with the Master Plan number (Injection is the first process of the Routing); toast "n Work Order(s) sent to I/J Plan".  
> System: I/J Plan groups Detail Plans into I/J Big Plans by Style + Model + Base Color + Plan Month + Area, not by SPRAY/Logo — a SPRAY WO and a Logo WO with the same key share one I/J Big Plan; a Detail Plan's Order Q'ty = the WO Q'ty per size, SO allocation plus Common Stock.  
> Test:  
> - 2 WOs with the same Style, Model, Base Color, Plan Month, Area, one SPRAY and one Logo → I/J Plan has 2 Detail Plans in one Big Plan  
> - WO of 1,100 pairs (SO allocation 1,000 + Common Stock 100) → Detail Plan Order Q'ty 1,100  
> Source: BRD §6.1 Step 5 · Q-20260924-04 · Q-20261001-02 (D3) · Q-20261001-04 · prototype v0.30  

#### B21 · Create NEW plans for each planned process

- Planner · System (auto) · Master Plan
- Comes from: B20
- Goes to: B22 · Plan RELEASED · Work Order RELEASED → I/J Plan (one row one Detail Plan, grouped into Big Plan I/J) + NEW Trimming / Spray Out / Packing + Common Stock (surplus)
- Goes to: B23 · End

> The system pre-creates NEW plans for the processes that have a Plan screen in the WO Routing.  
> Result: each Trimming · Spray Out · Packing process in the Routing gets one NEW plan (customer note: generated automatically from the WO and routing).  
> System: no Injection WI at this step — Injection WIs are created only when scheduling in Injection Schedule.  
> Test:  
> - Routing without Spray → no NEW Spray Out plan  
> Source: OQ-46 · Q-20260923-19 (G) · Q-20260924-04  

#### B25 · Plan currently in which status?

- Planner
- Comes from: B24
- Goes to [DRAFT]: B26 · Delete Master Plan
- Goes to [RELEASED]: B27 · No delete in Master Plan — handled at Work Order

> Only a plan that has not been released can be deleted.  
> DRAFT: delete the plan.  
> RELEASED: no delete in Master Plan — handled in Work Order.  
> Source: Q-20260923-03 · Q-20260924-04  

#### B26 · Delete Master Plan

- Planner · Web · Master Plan
- Comes from: B25
- Goes to: B28 · Restore SO line Remaining

> The Planner deletes a draft plan that is no longer needed.  
> When: plan is DRAFT.  
> Action: Delete.  
> Result: the plan is deleted.  
> Test:  
> - RELEASED plan → no Delete  
> Open: the NOT RELEASED WOs of the deleted plan are deleted with it — proposed, not yet confirmed.  
> Source: Q-20260923-03 · Q-20260924-04  

#### B28 · Restore SO line Remaining

- Planner · System (auto) · Master Plan
- Comes from: B26
- Goes to: B29 · SO Remaining restored
- Goes to: B30 · End

> The system gives back the remaining-to-produce quantity to the SO lines of the deleted plan.  
> Result: each SO line's "REMAINING" is increased by exactly the Plan qty taken; the SO line can be picked again in another plan.  
> Test:  
> - SO line Remaining 0 (plan took 100) → delete plan → Remaining 100  
> Source: Q-20260923-03  

#### B32 · Enter new Current ETD

- Planner · Web · Master Plan
- Comes from: B31
- Goes to: B33 · Build Reschedule Preview

> The Planner enters a new expected delivery date (Current ETD) for the plan.  
> When: plan is RELEASED.  
> Action: Plan Details › "Update ETD" button › "NEW CURRENT ETD *" · "RESCHEDULE SOURCE *" › "Preview Reschedule".  
> Open: whether a DRAFT plan uses "Update ETD" or is edited directly in Plan Details; keeping Frozen processes unchanged is a proposal, not yet confirmed.  
> Source: Q-20260923-05 · prototype v0.22  

#### B33 · Build Reschedule Preview

- Planner · System (auto) · Master Plan
- Comes from: B32
- Goes to: B34 · Planner picks which action?

> The system builds a preview of the process schedule after moving the ETD.  
> System: process table with "Has Qty?" · "Frozen" · Old / New From–To · "Change Status"; Frozen processes keep their actuals and are not moved ("Frozen processes keep their actuals and are never auto-rescheduled.").  
> Test:  
> - A process with quantities (Frozen) → new From–To = old From–To  
> Source: prototype v0.22  

#### B34 · Planner picks which action?

- Planner
- Comes from: B33
- Goes to [Apply Reschedule]: B35 · Apply new schedule
- Goes to [Save as Simulation]: B36 · Save Simulation
- Goes to [Cancel]: B37 · Keep ETD and process schedule

> The Planner chooses to apply, save as a trial, or cancel.  
> Apply Reschedule: move the ETD and the real schedule.  
> Save as Simulation: save the scenario only, the real schedule stays.  
> Cancel: discard, ETD and schedule unchanged.  
> Source: prototype v0.22  

#### B35 · Apply new schedule

- Planner · System (auto) · Master Plan
- Comes from: B34
- Goes to: B38 · New Current ETD + rescheduled process dates

> The system applies the new schedule to the plan.  
> Action: "Apply Reschedule" button.  
> Result: Current ETD changes; Plan From / To of non-Frozen processes move accordingly.  
> Open: no Supervisor approval step for rescheduling yet — differs from BRD §7.  
> Source: Q-20260923-05 · BRD §7  

#### B36 · Save Simulation

- Planner · System (auto) · Master Plan
- Comes from: B34
- Goes to: B39 · Simulation copy · live schedule unchanged
- Goes to: B40 · End

> The system saves the rescheduling scenario for review without changing the real schedule.  
> Action: "Save as Simulation" button.  
> Result: a Simulation copy exists; the real Current ETD and process schedule stay unchanged.  
> Source: prototype v0.22  

## Status lifecycle

#### Master Plan

`DRAFT` → `RELEASED`

Transitions:

- `DRAFT` -- Release Work Order --> `RELEASED`
- `DRAFT` -- Delete --> `Deleted`

## Input

| # | Input | Type | Used in step |
| --- | --- | --- | --- |
| I-1 | Sales Order (lines per size, carrying the ship-to Country) — Plan qty may exceed Remaining, the excess becomes Common Stock | Document — Sales module | Start → Create Plan: select SO lines |
| I-2 | Internal Production Request | Internal document | Create Plan: select SO lines |
| I-5 | Country — Area field (Area of the ship-to Country on the SO line) | Master data | Step 2: group SO lines into Big Plans (Area is part of the grouping key) |
| I-3 | Item · Routing · Routing Mapping (the item's default routing + alternative routings) | Master data | Step 3 Review: pick a Routing for each Work Order |
| I-4 | Machine · Capacity Calendar | Master data | Calculate Plan From / To from lead time, check Capacity |

## Step ↔ screen

| Step | Role | Screen · UI button |
| --- | --- | --- |
| Open the Create Plan wizard | Planner | Master Plan · Plan List · `Create Plan` |
| Filter plans by Area (view only, not a business step) | Planner | Master Plan · Plan List · field `Area` outside the grid (All / Europe / Asia / America) · column `Area` |
| Select SO size lines · Enter Plan Qty per line | Planner | Master Plan · Step 1 · Select SO Lines |
| Select Plan Month | Planner | Master Plan · Step 2 · Item Lines · field `Plan Month` |
| Group SO lines into Big Plans · Calculate Common Stock | System (auto) | Master Plan · Step 2 · Item Lines (one row per Big Plan) |
| Pick a Routing for each Work Order | Planner | Master Plan · Step 3 · Review & Create (the `Routing` field of each WO) |
| Calculate Plan From / To from lead time · Flag Over capacity (warning only) | System (auto) | Master Plan · Step 3 · Review & Create |
| Create Master Plan | Planner | Master Plan · Step 3 · `Create Plan` |
| View the plan's Work Orders (view only, not a business step) | Planner | Master Plan · Plan List · column `WO` with an expand icon (1 plan → n WOs, with `Process` · `Progress` · `Status`); Plan Details › tab `Work Orders` › `Process view` (tree WO → processes, status and quantity of each process) |
| Release Work Order · Delete Master Plan · Enter new Current ETD | Planner | Master Plan · Plan Details (`Release Work Order`, `Update ETD`) |
| Create Work Orders per Big Plan · Send WOs to I/J Plan · Create NEW plans for processes with a Plan · Restore SO line Remaining · Build Reschedule Preview · Apply new schedule · Save Simulation | System (auto) | Master Plan (`Preview Reschedule`, `Apply Reschedule`, `Save as Simulation`) |

## Output

| # | Output | Produced when |
| --- | --- | --- |
| O-2 | Plan = `RELEASED`; Work Orders (one WO per Big Plan, created at `Create Plan`, `NOT RELEASED`; P.O Month = Plan Month) carrying the chosen Routing turn `RELEASED` → I/J Plan, each WO one Detail Plan with the Master Plan number, grouped by I/J into an I/J Big Plan by Style + Model + Base Color + Plan Month + Area; Order Q'ty = WO Q'ty incl. Common Stock — + plan `NEW` for Trimming / Spray Out / Packing (per the WO's Routing) + Common Stock (the surplus). The Injection WI is not created here — it is created when scheduled on Injection Schedule | Plan `DRAFT`, the Planner clicks Release Work Order (no approval step) |
| O-3 | SO line Remaining given back | Delete plan `DRAFT` |
| O-4 | No delete in Master Plan — handled in Work Order | Plan already `RELEASED` |
| O-5 | New Current ETD + rescheduled process dates (Frozen processes unchanged) | Planner clicks Apply Reschedule |
| O-6 | Simulation copy, live schedule unchanged | Planner clicks Save as Simulation |
| O-7 | Keep ETD and process schedule | Planner clicks Cancel in Reschedule Preview |

## Glossary

| Glossary | Meaning in this flow |
| --- | --- |
| `SO` | Sales Order — each size is one line |
| `Internal Production Request` | Internal request to produce, not tied to a customer order |
| `Plan qty` | Quantity the Planner decides to produce for a line |
| `REMAINING` | Quantity of the SO line still to be planned |
| `Big Plan (Master Plan)` | Group of SO lines with the same Style + Model + Base Color + SPRAY/Logo + Area in one Master Plan; each Big Plan becomes one Work Order |
| `Area` | Field of Master Data Country; the SO line carries the ship-to Country and the system derives the Area |
| `Plan Month · P.O Month` | Production month the Planner picks for the whole Master Plan · month recorded on the WO, equal to the Plan Month, unchanged after Release |
| `SPRAY / Logo` | Item attribute telling whether goods go to Spray or Logo printing — two different Routings, so it is part of the Master Plan grouping key |
| `Master Plan` | Overall plan for one Plan Month; one Master Plan → n Big Plans → n Work Orders |
| `Work Order (WO)` | Production order, created for each Big Plan when the Master Plan is created (NOT RELEASED), released when the Master Plan is released; its status in Master Plan follows the whole Routing: NOT RELEASED → RELEASED → IN PROGRESS → COMPLETED |
| `Routing` | The item's process sequence; defaults from Routing Mapping |
| `Lead Time · Buffer Days` | Days per process · buffer days before the next process |
| `Common Stock` | Surplus not tied to any SO line = Plan qty − total SO allocation |
| `Capacity Calendar` | Daily machine / work center capacity, used for Over capacity warnings |
| `Current ETD` | The plan's current estimated delivery date |
| `Frozen` | A process with actuals, never rescheduled automatically |
| `Simulation` | A saved trial reschedule that does not change the real schedule |