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/picking.md
+43 -43
View File
@@ -117,7 +117,7 @@ The ordering logic lives in the code activity **"Order stock when none location
When a line allows excess shipping, EasyWMS first tries to assign the exact quantity. If all strategies are exhausted without fulfilling the line completely, the first stock discarded by the last strategy is assigned as excess. Excess is minimized by unassigning the last-assigned stock. The "strict shipping logic on excess" flag prevents excess assignment from using better-logic stock over what was already being shipped.
## Picking Modes — Manual Warehouse
## Picking Modes - Manual Warehouse
Manual warehouse picking is RFT-driven, following the **picking path** (optimal route minimizing operator travel). The path starts at the picking start point and ends at the shipping area.
@@ -135,7 +135,7 @@ Manual warehouse picking is RFT-driven, following the **picking path** (optimal
| **Voice picking** | Operator receives spoken instructions, confirms by voice; both hands free for handling | RFT + headset |
| **Advanced picking** | Picks client containers before dock/stage assigned; containers placed on shelf until assignment | RFT |
**Cutting stock picking** (rope, cable, chain — indivisible lengths):
**Cutting stock picking** (rope, cable, chain - indivisible lengths):
- Requires a physical cut before picking
- Two models: **integrated cut** (cut performed at the location) or **delegated cut** (cut performed at a dedicated cutting station)
- Cutting stations can have dedicated equipment and procedures for item-specific cutting complexity
@@ -155,27 +155,27 @@ Manual warehouse picking is RFT-driven, following the **picking path** (optimal
**Flow (RFT):**
1. Enter the **outbound code** (a default is proposed)
2. Choose the **shipping dock**
3. Add lines — **item + quantity** — repeat per line
4. **Release** the order — creates the outbound, its lines, and the picking tasks in SmartUI (can take time for large orders)
3. Add lines - **item + quantity** - repeat per line
4. **Release** the order - creates the outbound, its lines, and the picking tasks in SmartUI (can take time for large orders)
5. The RFT is redirected into the **standard picking loop**
**Module interactions:**
- **3PL module** — SOC and SOF use different document codes (the owner is appended to the SOF only). Example: SOC `MAN0000000000000000010`, SOF `MAN0000000000000000010-CECOA`.
- **Carrier module** — manual picking does **not** expose a carrier field, which can block downstream carrier processing. If the module is enforced, expect a post-release manual intervention.
- **3PL module** - SOC and SOF use different document codes (the owner is appended to the SOF only). Example: SOC `MAN0000000000000000010`, SOF `MAN0000000000000000010-CECOA`.
- **Carrier module** - manual picking does **not** expose a carrier field, which can block downstream carrier processing. If the module is enforced, expect a post-release manual intervention.
Entry workflow: `EasyWMS.ManualPicking_ByItem_UI` (cf. [RF Menu reference](../architecture/rf-menu.md#4-ordres-dexpédition-sharedmenu_shippingorders)).
Entry workflow: `EasyWMS.ManualPicking_ByItem_UI` (cf. [RF Menu reference](../architecture/rf-menu.md#4-shipping-orders---sharedmenu_shippingorders)).
### Location Carts (chariots à emplacement) for Multi-Order Picking
Location carts let one operator prepare **several orders at once without creating one client container per order**. The WMS maps cart divisions (column × row) to orders automatically.
- **Usable only in multi-order picking modes** — groups of orders and waves
- **Usable only in multi-order picking modes** - groups of orders and waves
- Removes the need for a secondary *"TRF à emplacement"* configuration in many layouts
- After picking, the cart is dropped directly onto the packing station
**Setup — SmartUI:**
**Setup - SmartUI:**
1. **Create division types** — define the number and codes of cart slots (tested up to 20×20). The WMS temporarily labels slots `Section{sequence}`; the name entered guides the operator during picking.
1. **Create division types** - define the number and codes of cart slots (tested up to 20×20). The WMS temporarily labels slots `Section{sequence}`; the name entered guides the operator during picking.
2. **Create the cart** (tab **"Carts"**):
| Field | Description |
@@ -184,14 +184,14 @@ Location carts let one operator prepare **several orders at once without creatin
| Storage location | **Mandatory** |
| Division type | If empty → the cart behaves as one slot |
Cart statuses : **Open** (available), **Closed** (stock in progress — not yet packed).
Cart statuses : **Open** (available), **Closed** (stock in progress - not yet packed).
**Picking with a cart (RFT):**
- At wave/group start, the RFT proposes to use a cart — scan its code.
- At wave/group start, the RFT proposes to use a cart - scan its code.
- On the first drop, the WMS asks which slot (division) to use; subsequent tasks for the same order are auto-routed to the same slot.
- Column **"Division"** shows `CartCode_SectionCode`.
**Edge case — closed cart with no free slot:** the RFT reports no task available and flips the cart back to **Open**. To unload: **"Fermer"** on the task list → RFT menu **Rangement → Stock de chariots** → either "Ranger le chariot entièrement" (no redirection to packing) or "Décharger en mode stock libre".
**Edge case - closed cart with no free slot:** the RFT reports no task available and flips the cart back to **Open**. To unload: **"Fermer"** on the task list → RFT menu **Rangement → Stock de chariots** → either "Ranger le chariot entièrement" (no redirection to packing) or "Décharger en mode stock libre".
**Packing:** scan the cart code → WMS indicates divisions → scan the division to pack (or list divisions with stock). Standard packing runs with `CartCode_SectionCode` as origin.
@@ -211,7 +211,7 @@ Paper picking is used when RF coverage is missing, when a customer wants a print
6. Back at the station, click **Confirmer le lot** and **scan the batch number** on the printed sheet :
- If the order is complete → scan the batch number a second time to close the preparation.
- Otherwise → scan the incomplete tasks one by one and enter the actual picked quantity.
7. Scan the batch number one last time to mark the preparation done — the order transitions to **"Prepared"** and stock is transferred to the staging buffer / dock.
7. Scan the batch number one last time to mark the preparation done - the order transitions to **"Prepared"** and stock is transferred to the staging buffer / dock.
### Picking Incidences (Manual Warehouse)
@@ -219,9 +219,9 @@ During picking, issues are recorded when containers are not where expected or ex
- **Mark to review**: creates a lock and count on the container/location; does not interrupt the current process; lock removed when count completes
- **Stock adjustment**: ERP is notified of any inventory corrections via messenger service
**Wait for replenishment**: configurable behavior — system can auto-trigger replenishment tasks when a picking location is empty to complete the pick.
**Wait for replenishment**: configurable behavior - system can auto-trigger replenishment tasks when a picking location is empty to complete the pick.
By default, when an outbound order is released and no picking location has stock (but stock exists in replenishment sources), picking tasks are created on empty PDLs — these are **silently skipped at execution time** if the PDL is still empty when the operator reaches it. Three global parameters relax this default :
By default, when an outbound order is released and no picking location has stock (but stock exists in replenishment sources), picking tasks are created on empty PDLs - these are **silently skipped at execution time** if the PDL is still empty when the operator reaches it. Three global parameters relax this default :
| Parameter | Effect | Key workflow(s) |
|---|---|---|
@@ -242,7 +242,7 @@ Operator flow for the third parameter :
**Excess reduction**: if multiple tasks exist for the same item and one is over-picked, the remaining tasks are reduced by the excess amount (or canceled if already satisfied).
## Picking — Automatic Warehouse (Picking Conveyor / PK)
## Picking - Automatic Warehouse (Picking Conveyor / PK)
In automatic warehouses, picking is goods-to-person. The TMS extracts containers from storage and brings them to a **picking conveyor (PK)** station. One PK can serve multiple **preparation zones (MP)**; each MP is a physical table where the operator deposits picked stock into client containers.
@@ -259,14 +259,14 @@ Configuration of picking + preparation pairs (robotics-specific, from EasyS + Sm
- **Virtual** route → consolidation zone
- **Max concurrent orders** (SmartUI): **Menu → Control → Workstations** → select PK → set the value. Must **equal the number of preparation tables** linked to the PK
- **MP assignment mode** (SmartUI): **Menu → Control → Workstations** → select MP(s) → **Modify assignment mode**
- **Automatic** — WMS assigns the next order to a table
- **Manual** — operator assigns via **Menu → Control → Picking-station assignment**. ⚠️ In manual mode, **tasks do not generate until the order is assigned**
- **Route requirement**: the MP must have a route to the shipping dock of the order — otherwise tasks won't generate
- **Automatic** - WMS assigns the next order to a table
- **Manual** - operator assigns via **Menu → Control → Picking-station assignment**. ⚠️ In manual mode, **tasks do not generate until the order is assigned**
- **Route requirement**: the MP must have a route to the shipping dock of the order - otherwise tasks won't generate
**Three ways to trigger container extraction from the miniload:**
1. Demand the container from the picking workstation (specific support, empty supports, or specific item)
2. Request empty containers
3. Launch an order — assigns PK + generates `pickingContainer` tasks
3. Launch an order - assigns PK + generates `pickingContainer` tasks
For detailed bring-up in simulation and the "Store container" + "Liberate" test flow, see [Galileo Simulation](../operations/galileo-simulation.md).
@@ -322,7 +322,7 @@ After all picking tasks for a shipping order are completed at the PK:
- Physical PK pushbutton is pressed to signal completion
- TMS generates movement tasks to return the source container to its storage location or to a rejection station
## Picking — Pick and Pack Mode
## Picking - Pick and Pack Mode
In Pick and Pack warehouses, operators pick stock directly into the final shipping carton (client container). Two integration levels:
@@ -359,7 +359,7 @@ The picking path is the optimal traversal order of locations for picking tasks.
The picking path starts at the **picking start point** (configured per sub-warehouse or warehouse) and ends at the shipping area. The path selects the next closest task, but overall path optimality depends on warehouse layout.
## Order Planning — Waves, Groups, and Shipment Templates
## Order Planning - Waves, Groups, and Shipment Templates
### Order priorities
@@ -367,11 +367,11 @@ Each shipping order carries a priority that determines task sequence:
| Priority | Relative urgency |
|----------|-----------------|
| **Urgent** | Highest — processed first in all queues |
| **Urgent** | Highest - processed first in all queues |
| **High** | Above normal |
| **Normal** | Default |
| **Low** | Below normal |
| **Very Low** | Lowest — processed last |
| **Very Low** | Lowest - processed last |
Priorities are set per order (from the ERP or manually) and apply across all picking and shipping task generation.
@@ -418,7 +418,7 @@ Shipment templates automate wave and group creation by applying a set of selecti
### Order fusion
**Fusion** merges multiple shipping orders from the same client/destination into a single preparation batch. This is a **manual-only** operation — EasyWMS does not auto-fuse orders.
**Fusion** merges multiple shipping orders from the same client/destination into a single preparation batch. This is a **manual-only** operation - EasyWMS does not auto-fuse orders.
Conditions for fusion:
- Same client (account)
@@ -458,23 +458,23 @@ After fusion, the combined order is prepared as a single batch, reducing travel
| Interface | Path |
|---|---|
| RFT — picking (manual warehouse) | Menu "Picking" → task mode selection |
| RFT — picking conveyor (automatic warehouse) | Workstation "Picking" view |
| Web — stock assignment strategies | "Configuration" → "Stock assignment strategies" |
| Web — shipping order + stock assign | "Shipping" → "Shipping orders" → order → "Stock assign" |
| Web — workstations (PK config) | "Control" → "Workstations" |
| Web — docks and stages | "Control" → "Docks and stages" |
| RFT - picking (manual warehouse) | Menu "Picking" → task mode selection |
| RFT - picking conveyor (automatic warehouse) | Workstation "Picking" view |
| Web - stock assignment strategies | "Configuration" → "Stock assignment strategies" |
| Web - shipping order + stock assign | "Shipping" → "Shipping orders" → order → "Stock assign" |
| Web - workstations (PK config) | "Control" → "Workstations" |
| Web - docks and stages | "Control" → "Docks and stages" |
## Related
- [Shipping](shipping.md) — picking is part of the shipping process; picking leads to truck loading
- [Replenishment](replenishment.md) — picking from dedicated locations triggers replenishment when stock runs out
- [Container (LPN)](container.md) — client containers are created during picking; source containers are extracted from storage
- [Stock](stock.md) — stock assignment determines which specific stock unit is picked
- [Reception](reception.md) — received goods enter inventory and become eligible for stock assignment
- [Task](task.md) — picking generates Picking tasks; negative picking and cut picking are specific task types
- [Outbound Order](order-outbound.md) — shipping orders are the source of picking demand; order priority drives task sequence
- [Location](location.md) — picking dedicated locations (PDLs) are the primary source for picking; location logics control eligibility
- [[cutting-stock]] — cutting stock picking (shelf, integrated station, delegated station) are specialized picking modes
- [[stations]] — PK (type 2), MP (type 16), Workzone (type 64), Decision (type 63), Cutting Station (type 61) all support picking
- [Tense Flow](tense-flow.md) — tense-flow picking bypasses storage : pick directly from a source support into a client container via the `PREPARATION` buffer
- [Shipping](shipping.md) - picking is part of the shipping process; picking leads to truck loading
- [Replenishment](replenishment.md) - picking from dedicated locations triggers replenishment when stock runs out
- [Container (LPN)](container.md) - client containers are created during picking; source containers are extracted from storage
- [Stock](stock.md) - stock assignment determines which specific stock unit is picked
- [Reception](reception.md) - received goods enter inventory and become eligible for stock assignment
- [Task](task.md) - picking generates Picking tasks; negative picking and cut picking are specific task types
- [Outbound Order](order-outbound.md) - shipping orders are the source of picking demand; order priority drives task sequence
- [Location](location.md) - picking dedicated locations (PDLs) are the primary source for picking; location logics control eligibility
- [[cutting-stock]] - cutting stock picking (shelf, integrated station, delegated station) are specialized picking modes
- [[stations]] - PK (type 2), MP (type 16), Workzone (type 64), Decision (type 63), Cutting Station (type 61) all support picking
- [Tense Flow](tense-flow.md) - tense-flow picking bypasses storage : pick directly from a source support into a client container via the `PREPARATION` buffer