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/shipping.md
+43 -43
View File
@@ -47,7 +47,7 @@ last_compiled: "2026-04-17"
## Overview
Shipping is the end-to-end process of fulfilling customer orders: from order receipt through stock assignment, preparation (picking or container shipping), consolidation, truck loading, and closure. EasyWMS represents outbound work through **shipping orders** — the central document linking customer demand to warehouse operations.
Shipping is the end-to-end process of fulfilling customer orders: from order receipt through stock assignment, preparation (picking or container shipping), consolidation, truck loading, and closure. EasyWMS represents outbound work through **shipping orders** - the central document linking customer demand to warehouse operations.
Shipping orders typically arrive from the ERP via `SOR` messages but can be created manually from the web interface. For the canonical shipping order lifecycle and all statuses (Waiting, Reserved, Released, In Preparation, Paused, Closed/Archived, etc.) see [Outbound Order](order-outbound.md).
@@ -119,7 +119,7 @@ Release can be:
**ERP message sent:** `SOC` (order status change)
**Transaction recorded:** `OUT.CST`
**Parameter:** `MAX_AUTORELEASED_OUTBOUNDORDERS` — maximum orders auto-released simultaneously
**Parameter:** `MAX_AUTORELEASED_OUTBOUNDORDERS` - maximum orders auto-released simultaneously
### Release by Sub-warehouse
@@ -140,7 +140,7 @@ Multiple shipping orders are picked together (same picking path). After picking,
### Fusions
Multiple shipping orders are shipped together without ungrouping — typically for orders going to the same customer. Picked stock can be placed in shared containers without redistribution.
Multiple shipping orders are shipped together without ungrouping - typically for orders going to the same customer. Picked stock can be placed in shared containers without redistribution.
### Waves
@@ -177,17 +177,17 @@ A stock-assignment strategy and/or a prepackaging strategy can be attached to th
**Per-type tabs** :
- **Picking d'ordres groupés** : grouping criteria (carrier, mono-ligne, mono-unité, critère personnalisé), group size (max orders / lines / volume), filters (stock rangé, crossdocking, UdM, critère perso), ungrouping (UAP + packing buffer), minimum conditions (min qty, min orders).
- **Vague de picking** : carrier + critère perso ; max orders, volume, UdM, min orders. Checkbox **"Generate tasks on release"** — if set, tasks are created when the wave is released ; otherwise at operator pickup time.
- **Vague de picking** : carrier + critère perso ; max orders, volume, UdM, min orders. Checkbox **"Generate tasks on release"** - if set, tasks are created when the wave is released ; otherwise at operator pickup time.
- **Picking d'ordre** : for single-order templates. Filters on UdM + critère perso only.
**Scheduler.** Templates can run between two hours on selected weekdays, with a configurable interval in minutes. Two daily windows (e.g. 9–10h and 15–16h) require **duplicating** the template.
**Criteria** are mandatory (at least one per template). Each criterion rejects orders that don't match — two tabs are available :
**Criteria** are mandatory (at least one per template). Each criterion rejects orders that don't match - two tabs are available :
- **Ordre d'expédition** : Code, Description, Type (`Customer`, `Transfer`, `DirectTransfer`, `Fabrication`, `Manuel`, `Retour`…), Class, Owner, Mono-ligne, Mono-unité, Follow sequence, Auto-release, Carrier, Transport type, N hours before release/loading, N hours late, Country/City/Postal code.
- **Ligne d'ordre d'expédition** : item type, item family, danger, stackability, voluminous, single parcel.
**Critère personnalisé — LINQ syntax** :
**Critère personnalisé - LINQ syntax** :
```csharp
// Criterion on the outbound order itself (ex: orders imported with source = "WEB")
@@ -227,10 +227,10 @@ Typical need: order prepared from multiple origins (manual + automatic aisles, d
3. Empty source containers are deleted if configured; task cancellation follows
**Transactions:**
- `CON.CREATE` — new consolidation container created
- `STK.MOVE` — stock moved from source to destination
- `CON.DELETE` — empty source container deleted
- `TSK.CANCEL` — tasks for deleted container canceled
- `CON.CREATE` - new consolidation container created
- `STK.MOVE` - stock moved from source to destination
- `CON.DELETE` - empty source container deleted
- `TSK.CANCEL` - tasks for deleted container canceled
HPKS (laser pick-term tray) illuminates the destination division for easy identification.
@@ -262,7 +262,7 @@ When route sequencing is planned by a TMS, the ERP sends a **`RUT` file** instea
Operational flow :
1. **Integrate the RUT file.** Orders appear in the orders view but must be handled from the **routes view** — releasing them individually is not the nominal path.
1. **Integrate the RUT file.** Orders appear in the orders view but must be handled from the **routes view** - releasing them individually is not the nominal path.
2. **Launch the route** → each order is auto-released with its stock assignment.
3. **Prepare the orders** in any convenient internal order.
4. **Create a truck load** and attach it to the route. A template can create the load automatically at route release.
@@ -300,14 +300,14 @@ Loads represent a physical transport vehicle (truck, van) that will carry one or
### Multi-zone Loading (Virtual Dock)
Warehouses with multiple storage/preparation areas can use a **virtual dock** — a common dock reference for all zones. Carriers collect stock from different physical zones, but all are referenced to the same virtual dock for tracking purposes.
Warehouses with multiple storage/preparation areas can use a **virtual dock** - a common dock reference for all zones. Carriers collect stock from different physical zones, but all are referenced to the same virtual dock for tracking purposes.
### Truck Loading — SmartUI configuration reference (Mecalux France)
### Truck Loading - SmartUI configuration reference (Mecalux France)
Standard EasyWMS exposes two truck-loading modes at dock level :
- **No buffer** — order auto-ships as soon as it lands on the dock
- **Buffer + dock** — an intermediate control step validates pallets against the load before shipment
- **No buffer** - order auto-ships as soon as it lands on the dock
- **Buffer + dock** - an intermediate control step validates pallets against the load before shipment
**Load creation modes (per order type: unitary, route, group, merged, wave, by carrier):**
@@ -316,12 +316,12 @@ Standard EasyWMS exposes two truck-loading modes at dock level :
| **Automatic (planned)** | Load created at order release; strict container control (scanning a container from another order raises an error) |
| **Non planifié** | Load created at release; **no container control** |
| **Manuel (planned)** | Load created manually; strict container control |
| RFT — manual, no control | Created from RFT; no container control (indicative only) |
| RFT — from a route | Load tied to an existing route |
| RFT - manual, no control | Created from RFT; no container control (indicative only) |
| RFT - from a route | Load tied to an existing route |
EasyS minimum: **one buffer + one dock** per dock used. The buffer can be carried in `<PrpPackingLocation>` on SOR02, or assigned manually via SmartUI **Ordres de sortie → "Assigner quai/poumon"**.
**SmartUI — Configuration → Chargements:**
**SmartUI - Configuration → Chargements:**
| Option | Effect |
|---|---|
@@ -332,24 +332,24 @@ EasyS minimum: **one buffer + one dock** per dock used. The buffer can be carrie
| Quantity validation | Same semantics as picking |
| **Allow load of all stock** | Adds a RFT button to load all free stock in one action |
**RFT — create a load from the floor:** `Ordres de sortie → Chargement camion → Charger les conteneurs → Nouveau`. To **disable** this path, set every order-type mode to something other than "Non planifiée". As soon as one type is "Non planifiée", operators can create loads from RFT.
**RFT - create a load from the floor:** `Ordres de sortie → Chargement camion → Charger les conteneurs → Nouveau`. To **disable** this path, set every order-type mode to something other than "Non planifiée". As soon as one type is "Non planifiée", operators can create loads from RFT.
**RFT — execute a load (`EasyWMS.TruckLoad_GetLoads_UI`):**
**RFT - execute a load (`EasyWMS.TruckLoad_GetLoads_UI`):**
1. `Ordres de sortie → Chargement camion → Charger les conteneurs`
2. Filter by dock/buffer or by load
3. Select the load (status `Ready to load` if the whole order is prepared)
4. Scan pallets — button **"Conteneur"** lists remaining containers ; **"Effectuer"** closes the load even if pallets are missing
4. Scan pallets - button **"Conteneur"** lists remaining containers ; **"Effectuer"** closes the load even if pallets are missing
> ℹ️ During loading the load status reads **"Loading"** (red on RFT).
**Delivery-note printing at load close:** when the BL is configured to print on order close, **closing the truck load triggers the print** — including for a partial close. On a two-step load (remainder), the BL is printed at each close and always covers **all shipped lines of the order**.
**Delivery-note printing at load close:** when the BL is configured to print on order close, **closing the truck load triggers the print** - including for a partial close. On a two-step load (remainder), the BL is printed at each close and always covers **all shipped lines of the order**.
**Truck unloading (RFT):** menu `Décharger les conteneurs` → scan the container → scan the drop-off location (default: the end-of-preparation buffer).
### Order Merge vs Load
Truck loading handles **loads** — merging happens **before** load creation on the shipping orders themselves. A merged order behaves as a single order when assigning a load, but ERP traceability remains per-original-order (see [Outbound Order → Merge](order-outbound.md#merge-order-fusion)).
Truck loading handles **loads** - merging happens **before** load creation on the shipping orders themselves. A merged order behaves as a single order when assigning a load, but ERP traceability remains per-original-order (see [Outbound Order → Merge](order-outbound.md#merge-order-fusion)).
## Truck Loading (RFT Process)
@@ -378,7 +378,7 @@ Operators at the dock register each item loaded using the RFT:
- Auto-close: last item loaded triggers close process (seal registration, report collection)
- Partial close: configured to allow closing without all units loaded
## PS Groups (Automatic Warehouse — Outbound Conveyors)
## PS Groups (Automatic Warehouse - Outbound Conveyors)
PS (Pallet Shuttle or outbound conveyor) groups are logical groupings of outbound conveyors in automatic warehouses. Each group configures which PS stations belong to it and how they are filled (criteria for which PS station gets the next container).
@@ -451,25 +451,25 @@ Multiple shipping orders can be merged into the same client container if they me
| Interface | Path |
|---|---|
| Web — shipping orders | Menu "Shippings" → "Shipping orders" |
| Web — routes | Menu "Shippings" → "Routes" |
| Web — loads | Menu "Shippings" → "Loads" |
| Web — waves | Menu "Shippings" → "Waves" |
| Web — groups/fusions | Menu "Shippings" → "Groups" |
| Web — shipping templates | Menu "Configuration" → "Shipping templates" |
| Web — PS groups | Menu "Control" → "PS groups" |
| RFT — truck loading | Menu "Shipping" → "Load truck" |
| RFT — consolidation | Menu "Shipping orders" → "Packaging" |
| Web - shipping orders | Menu "Shippings" → "Shipping orders" |
| Web - routes | Menu "Shippings" → "Routes" |
| Web - loads | Menu "Shippings" → "Loads" |
| Web - waves | Menu "Shippings" → "Waves" |
| Web - groups/fusions | Menu "Shippings" → "Groups" |
| Web - shipping templates | Menu "Configuration" → "Shipping templates" |
| Web - PS groups | Menu "Control" → "PS groups" |
| RFT - truck loading | Menu "Shipping" → "Load truck" |
| RFT - consolidation | Menu "Shipping orders" → "Packaging" |
## Related
- [Picking](picking.md) — picking is the core preparation activity within the shipping process
- [Replenishment](replenishment.md) — picking dedicated locations are replenished when stock runs out during order preparation
- [Container (LPN)](container.md) — containers are the main unit tracked through shipping, loading, and delivery
- [Crossdocking](crossdocking.md) — some shipping orders can bypass storage through crossdocking
- [Reception](reception.md) — inbound stock feeds the inventory that shipping orders consume
- [Outbound Order](order-outbound.md) — shipping orders (SOR/SOF/SOC) drive the entire shipping process; order type determines destination and process
- [Task](task.md) — shipping generates Shipping and Loading tasks; task priority inherits from order priority
- [[cutting-stock]] — cutting stock has special shipping profile requirements (excess %, enter quantity mode = Manually)
- [[stations]] — Dock (type 34), Stage (type 33), PS (type 4), Consolidation (type 17) stations are central to shipping
- [Prepackaging](prepackaging.md) — dedicated page for prepackaging strategy configuration, ERP (SOR02) payload, and tested behaviors
- [Picking](picking.md) - picking is the core preparation activity within the shipping process
- [Replenishment](replenishment.md) - picking dedicated locations are replenished when stock runs out during order preparation
- [Container (LPN)](container.md) - containers are the main unit tracked through shipping, loading, and delivery
- [Crossdocking](crossdocking.md) - some shipping orders can bypass storage through crossdocking
- [Reception](reception.md) - inbound stock feeds the inventory that shipping orders consume
- [Outbound Order](order-outbound.md) - shipping orders (SOR/SOF/SOC) drive the entire shipping process; order type determines destination and process
- [Task](task.md) - shipping generates Shipping and Loading tasks; task priority inherits from order priority
- [[cutting-stock]] - cutting stock has special shipping profile requirements (excess %, enter quantity mode = Manually)
- [[stations]] - Dock (type 34), Stage (type 33), PS (type 4), Consolidation (type 17) stations are central to shipping
- [Prepackaging](prepackaging.md) - dedicated page for prepackaging strategy configuration, ERP (SOR02) payload, and tested behaviors