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/quality-control.md
+13 -13
View File
@@ -30,7 +30,7 @@ EasyWMS controls stock quality from reception through shipping. Statuses can be
- **In the warehouse** (web interface, RFT, or ERP message)
- At **shipping** (to require or prefer stock in a specific status for a shipping order line)
> **Important:** The _Expired_ state is **not** a stock status — stock expires automatically when logistic attribute dates (expiry date, best before date, end of life) are reached.
> **Important:** The _Expired_ state is **not** a stock status - stock expires automatically when logistic attribute dates (expiry date, best before date, end of life) are reached.
---
@@ -48,8 +48,8 @@ Each stock status is configured to block or allow specific operations:
| Internal use (manufacturing) | Yes |
A single stock record can have two simultaneous statuses:
- **Receiving status** — set at reception time (from profile, order line, or operator)
- **User status** — applied manually by an operator, manager, or via ERP message
- **Receiving status** - set at reception time (from profile, order line, or operator)
- **User status** - applied manually by an operator, manager, or via ERP message
---
@@ -187,7 +187,7 @@ Both partial and total locks can be performed from **RFT** or **ERP** (STR messa
|---|---|
| `CST.STK` | Stock status applied or removed (when reception is closed) |
Note: `CST.STK` is **not** generated if the reception is still open — changes are visible in the interface but not audited until reception closes.
Note: `CST.STK` is **not** generated if the reception is still open - changes are visible in the interface but not audited until reception closes.
---
@@ -206,8 +206,8 @@ STC is only sent when the **reception is closed**. For stock from open reception
- A stock can have both a **receiving status** (set at reception) and a **user status** (set manually) simultaneously.
- When a lock is applied, EasyWMS immediately checks all active tasks and assignments using that stock and adapts them (cancels or decrements) based on the operations the lock blocks.
- Expired stock (`_Expired_` state) is handled by the logistic attributes expiry system — not the quality lock system.
- Only locations that allow inventory can have their stock counted. Quality locks do not change this — but locks that prevent counting block task generation.
- Expired stock (`_Expired_` state) is handled by the logistic attributes expiry system - not the quality lock system.
- Only locations that allow inventory can have their stock counted. Quality locks do not change this - but locks that prevent counting block task generation.
- The 15-minute job for automatic unlock means that very short-duration locks (< 15 min) are not reliably supported.
---
@@ -253,10 +253,10 @@ STC is only sent when the **reception is closed**. For stock from open reception
## Related
- [[stock]] — Quality locks are stored as stock status fields; stock must have no movement-blocking lock to be picked, replenished, or shipped
- [[container]] — Locks can be applied at container granularity; all stock in a container can be locked in one operation
- [[reception]] — Receiving status is applied at reception time via profile, order line, or operator; STC sent at close
- [[order-outbound]] — Shipping order lines can specify required/preferred stock status for assignment
- [[product-item]] — Item receiving profile defines automatic lock status and duration at inbound
- [[stock-adjustment]] — Both quality control and stock adjustment use STC/STK.ADJ transactions; quality locks affect task/assignment eligibility
- [[cutting-stock]] — Cutting stock has partial/total lock behavior; lock can propagate to cut portions
- [[stock]] - Quality locks are stored as stock status fields; stock must have no movement-blocking lock to be picked, replenished, or shipped
- [[container]] - Locks can be applied at container granularity; all stock in a container can be locked in one operation
- [[reception]] - Receiving status is applied at reception time via profile, order line, or operator; STC sent at close
- [[order-outbound]] - Shipping order lines can specify required/preferred stock status for assignment
- [[product-item]] - Item receiving profile defines automatic lock status and duration at inbound
- [[stock-adjustment]] - Both quality control and stock adjustment use STC/STK.ADJ transactions; quality locks affect task/assignment eligibility
- [[cutting-stock]] - Cutting stock has partial/total lock behavior; lock can propagate to cut portions