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/crossdocking.md
+23 -23
View File
@@ -4,7 +4,7 @@ type: concept
sources:
- areas/crossdocking/crossdocking_manual/index.md
- areas/crossdocking/crossdocking_manual/crossdocking_warehouse.md
- areas/crossdocking/crossdocking_manual/crossdocking_opportunity.md (404 — sourced from index.md description)
- areas/crossdocking/crossdocking_manual/crossdocking_opportunity.md (404 - sourced from index.md description)
- areas/putaway/putaway_admin/index.md (Group by SO/Route strategy type)
- sources/archives/06_Gestion_cross_docking.md
related:
@@ -38,8 +38,8 @@ Both types apply to containers, stacked containers, carts, and loose stock recei
When an operator is about to putaway received stock/containers, EasyWMS checks if any unreleased or in-preparation shipping order needs that stock. If yes, instead of going to bulk storage, the stock is directed straight to the dock, stage, or buffer associated with the shipping order.
The process triggers at two moments:
1. **After receipt into equipment** — operator is ready to putaway what was received
2. **When preparing to putaway from a reception stage** — stock received in a staging area is evaluated for direct transfer
1. **After receipt into equipment** - operator is ready to putaway what was received
2. **When preparing to putaway from a reception stage** - stock received in a staging area is evaluated for direct transfer
### Conditions and Eligibility
@@ -73,7 +73,7 @@ For **cutting stock items** in non-consolidating conversions:
### Concept (Warehouse)
If opportunity crossdocking is not possible (no shipping order needing immediate routing, or the stock quantity exceeds a single order's need), EasyWMS evaluates **crossdocking to warehouse**: the stock is placed in dedicated **crossdocking locations** near the shipping area. When the shipping order is eventually released, these crossdocking locations are consulted first during stock assignment — ensuring minimum travel distance for shipping.
If opportunity crossdocking is not possible (no shipping order needing immediate routing, or the stock quantity exceeds a single order's need), EasyWMS evaluates **crossdocking to warehouse**: the stock is placed in dedicated **crossdocking locations** near the shipping area. When the shipping order is eventually released, these crossdocking locations are consulted first during stock assignment - ensuring minimum travel distance for shipping.
The stock is not yet assigned to any shipping order during the crossdocking-to-warehouse placement. The link to the order happens at release time.
@@ -94,7 +94,7 @@ For crossdocking to warehouse to execute:
### Process Flow (Warehouse)
1. Operator is about to putaway received container/stock
2. EasyWMS first tries opportunity crossdocking (direct to dock) — if not possible:
2. EasyWMS first tries opportunity crossdocking (direct to dock) - if not possible:
3. EasyWMS evaluates crossdocking to warehouse:
a. Identifies candidate shipping orders meeting criteria
b. Checks if existing crossdocking locations already have sufficient stock
@@ -189,7 +189,7 @@ No special location or strategy configuration required. The system automatically
3. **Putaway strategies**: create and enable at least one strategy with "Is crossdocking" = true, including destination rules targeting the crossdocking locations
4. **Stock assignment**: ensure the stock assignment strategy consults crossdocking locations first when the shipping order is released (these locations are consulted preferentially automatically)
### Mecalux France — EasyS / SmartUI Setup Notes
### Mecalux France - EasyS / SmartUI Setup Notes
Additional setup steps consolidated from Mecalux France practice (in addition to the items above) :
@@ -203,16 +203,16 @@ Additional setup steps consolidated from Mecalux France practice (in addition to
1. On eligible items, enable **Cross-docking** in the advanced data tab.
2. Create the crossdocking putaway strategy **in sequence position 1** so it runs before the other putaway strategies.
**Criteria tab** : enable crossdocking. ⚠️ Without any additional criterion, **all items** will be treated as crossdocking at reception — always add conditions on the state of the pending outbound orders (e.g. status "En attente") to avoid this.
**Criteria tab** : enable crossdocking. ⚠️ Without any additional criterion, **all items** will be treated as crossdocking at reception - always add conditions on the state of the pending outbound orders (e.g. status "En attente") to avoid this.
**Rules tab** : set `Zone` to the crossdocking zone created in EasyS.
### Mecalux France — Known Behavior Notes
### Mecalux France - Known Behavior Notes
- **Reception must be done on the RFT** : the reception buffer does not trigger crossdocking evaluation. If reception is performed on the buffer, crossdocking is bypassed silently.
- **Buffer over dock for direct XD** : when the outbound order has an assigned buffer, direct (opportunity) crossdocking routes stock to the *buffer* rather than the dock — useful for a subsequent packing step.
- **Buffer over dock for direct XD** : when the outbound order has an assigned buffer, direct (opportunity) crossdocking routes stock to the *buffer* rather than the dock - useful for a subsequent packing step.
- **Crossdocking overrides reserve** : if a crossdocking location exists, the WMS redirects to it even if reserve stock is already available.
- **No label is printed** in standard direct (opportunity) crossdocking, even for a full pallet — plan for a custom label flow if the customer requires one.
- **No label is printed** in standard direct (opportunity) crossdocking, even for a full pallet - plan for a custom label flow if the customer requires one.
## Common Errors
@@ -222,7 +222,7 @@ Additional setup steps consolidated from Mecalux France practice (in addition to
**Stock placed in crossdocking location but not prioritized at release:** Stock assignment strategy doesn't prioritize crossdocking locations over normal storage. Check the stock assignment strategy configuration to ensure crossdocking location preferences are applied.
**Crossdocking location fills up, remainder goes to standard storage:** This is normal behavior — the crossdocking process places only what fits. The remainder follows standard putaway. No error; just an expected split.
**Crossdocking location fills up, remainder goes to standard storage:** This is normal behavior - the crossdocking process places only what fits. The remainder follows standard putaway. No error; just an expected split.
**Shipping order candidate filtered out unexpectedly:** The crossdocking strategy has filters on order status, priority, or days until release/load that exclude the order. Review the "Is crossdocking" strategy's filter settings.
@@ -232,18 +232,18 @@ Additional setup steps consolidated from Mecalux France practice (in addition to
| Interface | Path |
|---|---|
| Web — crossdocking putaway strategies | "Configuration" → "Putaway strategies" (filter by "Is crossdocking") |
| Web — item "Allow crossdocking" | "Inventory" → "Items" → item → settings |
| Web — location storage logic | "Warehouse" → "Locations" → location → "Change storage location logic" |
| RFT — putaway flow (opportunity XD) | Normal putaway flow; system routes to dock/stage automatically |
| RFT — putaway flow (XD to warehouse) | Normal putaway flow; system routes to XD location automatically |
| Web - crossdocking putaway strategies | "Configuration" → "Putaway strategies" (filter by "Is crossdocking") |
| Web - item "Allow crossdocking" | "Inventory" → "Items" → item → settings |
| Web - location storage logic | "Warehouse" → "Locations" → location → "Change storage location logic" |
| RFT - putaway flow (opportunity XD) | Normal putaway flow; system routes to dock/stage automatically |
| RFT - putaway flow (XD to warehouse) | Normal putaway flow; system routes to XD location automatically |
## Related
- [Reception](reception.md) — crossdocking is triggered during the putaway phase following reception
- [Putaway](putaway.md) — crossdocking uses the putaway strategy engine; "Is crossdocking" strategies are a subtype of putaway strategies
- [Shipping](shipping.md) — crossdocking locations feed stock assignment at order release; opportunity crossdocking routes directly to shipping docks
- [Container (LPN)](container.md) — containers are the primary unit being crossdocked; stacked containers and multi-reference containers have specific rules
- [Stock](stock.md) — stock status and logistic attributes affect crossdocking eligibility
- [Inbound Order](order-inbound.md) — ASN containers can carry exclusive reserves for specific outbound orders, enabling crossdocking on receipt
- [Outbound Order](order-outbound.md) — SOR lines with crossdocking-eligible items become crossdocking candidates; order priority drives XD selection
- [Reception](reception.md) - crossdocking is triggered during the putaway phase following reception
- [Putaway](putaway.md) - crossdocking uses the putaway strategy engine; "Is crossdocking" strategies are a subtype of putaway strategies
- [Shipping](shipping.md) - crossdocking locations feed stock assignment at order release; opportunity crossdocking routes directly to shipping docks
- [Container (LPN)](container.md) - containers are the primary unit being crossdocked; stacked containers and multi-reference containers have specific rules
- [Stock](stock.md) - stock status and logistic attributes affect crossdocking eligibility
- [Inbound Order](order-inbound.md) - ASN containers can carry exclusive reserves for specific outbound orders, enabling crossdocking on receipt
- [Outbound Order](order-outbound.md) - SOR lines with crossdocking-eligible items become crossdocking candidates; order priority drives XD selection