Mecalux/mcp-wms-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lint(standard): corrections completes mode standard

Browse Source 
- Em dashes: 1712 remplaces par tirets simples (86 fichiers + _index.md,
  en-tete section Limagrain conserve)
- Checklists: 24 '- [ ]' -> '- ☐' (3 pages operations, plus de todos Obsidian)
- Ancres: 33 reparees (slugs GitHub + ancres HTML <a id> reconnues),
  1 reciblee (manuel de reten)
- related: tenseflow -> tense-flow, pie -> mechanical-elements,
  group.md retire (doublon shipping)
- Registre: compteur global 122 -> 131 pages
- Rapport racine _lint_report.md mis a jour (scan v2 + re-scan final: 0 anomalie)
- Aucun fichier limagrain/ modifie (cloisonnement)
This commit is contained in:
Arthur
2026-07-20 13:01:21 +02:00
parent 7496aafe64
commit 9ce6ae37be
88 changed files with 1769 additions and 1871 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/concepts/kits.md
+23 -23
View File
@@ -27,12 +27,12 @@ A **kit** is an article resulting from the assembly of several component article
ERP integration sends kit definitions via the **KIT** message. Individual components must already exist as items in the WMS.
A kit record consists of:
- **Kit code** — the item code of the assembled article
- **Component 1..N** — each component's item code + required quantity
- **Kit code** - the item code of the assembled article
- **Component 1..N** - each component's item code + required quantity
Kits can be configured with or without physical assembly.
> ⚠️ **Profile requirement** — an article can only be configured as a kit if its logistic profile carries the **`Version`** logistic attribute. Otherwise the activation fails with a profile-mismatch error and the item must be reassigned to a profile that has `Version` and a reception control method.
> ⚠️ **Profile requirement** - an article can only be configured as a kit if its logistic profile carries the **`Version`** logistic attribute. Otherwise the activation fails with a profile-mismatch error and the item must be reassigned to a profile that has `Version` and a reception control method.
## Creating a kit article (SmartUI)
@@ -52,7 +52,7 @@ Add components with **"Ajouter composant"** : item, quantity, main component.
### 1. Kit without assembly (no mounting)
The kit article has **assembled = NO**. When a shipping order requests a kit, the WMS splits picking into separate tasks — one per component — without any physical assembly step. The kit is "assembled" implicitly by delivering all components.
The kit article has **assembled = NO**. When a shipping order requests a kit, the WMS splits picking into separate tasks - one per component - without any physical assembly step. The kit is "assembled" implicitly by delivering all components.
**Example**: A "Garden Set" kit containing 1 table + 4 chairs: picking generates two tasks (table pick, chairs pick). The final delivery is the two components together.
@@ -60,11 +60,11 @@ The kit article has **assembled = NO**. When a shipping order requests a kit, th
The kit article has **assembled = YES**. A physical work order is required: components are picked and brought to an assembly zone, the kit is built, and the resulting kit item is added to stock.
**Sub-type — on-demand assembly** (`assembled = YES`, `assembly_on_demand = YES`): the assembly can be triggered by a shipping order when kit stock is zero, without a pre-existing work order. Used when the ERP can create work orders autonomously.
**Sub-type - on-demand assembly** (`assembled = YES`, `assembly_on_demand = YES`): the assembly can be triggered by a shipping order when kit stock is zero, without a pre-existing work order. Used when the ERP can create work orders autonomously.
**Sub-type — ERP-driven assembly** (`assembled = YES`, `assembly_on_demand = NO`): the assembly is only triggered by a Work Order (WOR) from the ERP or a manually created order. No automatic kit fabrication request is generated when stock is insufficient.
**Sub-type - ERP-driven assembly** (`assembled = YES`, `assembly_on_demand = NO`): the assembly is only triggered by a Work Order (WOR) from the ERP or a manually created order. No automatic kit fabrication request is generated when stock is insufficient.
### SAGE 100C Connector — Nomenclature types
### SAGE 100C Connector - Nomenclature types
When integrated with SAGE 100C, EasyWMS maps SAGE nomenclature types to kit configurations:
@@ -97,7 +97,7 @@ ERP sends WOR → WMS creates work order
3. All components arrive at the assembly zone
4. Operator scans and confirms assembly on TRF
5. Component stock automatically decremented; kit stock created
6. Kit returned to storage — available for shipping orders
6. Kit returned to storage - available for shipping orders
7. `WOF` sent to ERP at work order close or cancellation (only if originated from ERP)
8. If work order was created manually: `KST` sent to ERP to notify consumed and created stock
@@ -119,22 +119,22 @@ ERP sends WOR (disassembly) → WMS creates work order
2. WMS generates picking tasks for kit items to assembly zone
3. Operator disassembles kits at the zone
4. Kit stock decremented; each component's stock incremented
5. Components returned to storage — available for picking
5. Components returned to storage - available for picking
6. `WOF` sent to ERP at close/cancellation (only if ERP-originated)
7. If manual: `UNK` sent to ERP to notify consumed (kits) and created (components) stock
---
## Work Order Lifecycle — Creation, Modification, Cancellation
## Work Order Lifecycle - Creation, Modification, Cancellation
### Creation modes
| Mode | Description |
|---|---|
| **From ERP** | `WOR` file — Work Order created with status **En attente** ; `WOF` sent at close/cancel |
| **Manual (SmartUI)** | Menu `Ordres de travail → Ordres de travail` — `KST` sent at close |
| **Manual (RFT)** | Menu `Kits → Demande de composants` — WO created **and released automatically**. ⚠️ **No ERP feedback** — neither `KST` nor `WOF` is generated |
| **Automatic** | Requires `Montage sur demande = OUI` — triggered at integration of an outbound order containing a kit shortage |
| **From ERP** | `WOR` file - Work Order created with status **En attente** ; `WOF` sent at close/cancel |
| **Manual (SmartUI)** | Menu `Ordres de travail → Ordres de travail` - `KST` sent at close |
| **Manual (RFT)** | Menu `Kits → Demande de composants` - WO created **and released automatically**. ⚠️ **No ERP feedback** - neither `KST` nor `WOF` is generated |
| **Automatic** | Requires `Montage sur demande = OUI` - triggered at integration of an outbound order containing a kit shortage |
### Modifications allowed, by status
@@ -151,8 +151,8 @@ When a WO is released, the WMS checks available stock in the kit zone. If insuff
## Closing a Work Order
- **Automatic** — once every requested kit has been assembled / disassembled.
- **Manual** — allowed at any time as long as **at least one** kit has been processed.
- **Automatic** - once every requested kit has been assembled / disassembled.
- **Manual** - allowed at any time as long as **at least one** kit has been processed.
- On close : `WOF` is sent to the ERP (for ERP-originated and SmartUI-manual WOs ; not for RFT-manual).
## Kit Shortage Handling
@@ -171,8 +171,8 @@ When a WO is released, the WMS checks available stock in the kit zone. If insuff
- Multiple components per kit; each component has item code + required quantity
- Stock consumed at assembly is tracked per lot/batch for traceability purposes
- Kit articles can have their own logistic profiles (reception, shipping, putaway) like any item
- **No automatic re-order**: WMS never requests fabrication when kit stock is insufficient — this is always a manual or ERP-driven action
- Component stock shortage at kit assembly time does not block the work order — operator must resolve
- **No automatic re-order**: WMS never requests fabrication when kit stock is insufficient - this is always a manual or ERP-driven action
- Component stock shortage at kit assembly time does not block the work order - operator must resolve
- For kits with `assembled = YES`, a work order (WOR) is mandatory before assembly can begin in the WMS
---
@@ -222,8 +222,8 @@ When a WO is released, the WMS checks available stock in the kit zone. If insuff
## Related
- [[product-item]] — Kit articles and components are both standard items with logistic profiles
- [[stock]] — Component stock is consumed; kit stock is created at assembly
- [[order-outbound]] — Outbound orders trigger component picks (no assembly) or reference assembled kit stock
- [[erp-interface]] — KIT, WOR, WOF, KST, UNK are the ERP messages for kit management
- [[manufacturing]] — Similar concept but for raw material → finished goods transformation; manufacturing module handles additives, production stations, and automated consumption
- [[product-item]] - Kit articles and components are both standard items with logistic profiles
- [[stock]] - Component stock is consumed; kit stock is created at assembly
- [[order-outbound]] - Outbound orders trigger component picks (no assembly) or reference assembled kit stock
- [[erp-interface]] - KIT, WOR, WOF, KST, UNK are the ERP messages for kit management
- [[manufacturing]] - Similar concept but for raw material → finished goods transformation; manufacturing module handles additives, production stations, and automated consumption