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/reception.md
+27 -27
View File
@@ -34,7 +34,7 @@ last_compiled: "2026-04-17"
Reception is the process by which stock physically arrives at the warehouse and is formally registered in EasyWMS. Until a receipt is completed and closed, the arrived stock does not exist for any other WMS process (picking, replenishment, shipping). Reception is therefore the entry gate between the physical world and the logical warehouse state.
EasyWMS supports five distinct reception entry points — each suited to a different physical configuration and information context: **Dock** (manual, RFT-driven), **ASN** (pre-notified containers), **PIE** (automated sensor gate), **PK** (picking conveyor), and **Returns** (customer returns). All share the same fundamental structure: a **Receipt** groups received stock lines, and optionally links to a **Receipt Order** (planned) or generates one ad hoc (blind).
EasyWMS supports five distinct reception entry points - each suited to a different physical configuration and information context: **Dock** (manual, RFT-driven), **ASN** (pre-notified containers), **PIE** (automated sensor gate), **PK** (picking conveyor), and **Returns** (customer returns). All share the same fundamental structure: a **Receipt** groups received stock lines, and optionally links to a **Receipt Order** (planned) or generates one ad hoc (blind).
The reception output is always a REF message to the ERP confirming what was received, and an ASO message (for pre-notified containers) or similar notification per entry point.
@@ -121,7 +121,7 @@ Supports **exclusive reserve** at receipt time: stock received can be pre-reserv
Unplanned stock with no prior notification or entry order.
- A receipt is automatically created (and closed at end) — transparent to the user.
- A receipt is automatically created (and closed at end) - transparent to the user.
- The receipt cannot be created or edited from the WMS UI.
- Supports: multi-reference LPN, single-SKU LPN (labeled/unlabeled/identical), loose stock, cutting stock.
- Communicates to ERP via `REF` after blind receipt close.
@@ -133,8 +133,8 @@ Unplanned stock with no prior notification or entry order.
Customer-returned stock coming back to the warehouse.
- Can be linked to a receipt order (if created from the web) or not (if created from RFT).
- If created from RFT: no lines initially — lines are added as stock is received.
- Date logistic attributes (expiry, shelf life) are captured but **not validated** — expired stock may be returned and must be managed after receipt.
- If created from RFT: no lines initially - lines are added as stock is received.
- Date logistic attributes (expiry, shelf life) are captured but **not validated** - expired stock may be returned and must be managed after receipt.
- Supports: containers, loose stock, cutting stock, exclusive reserves.
- Custom code prefix configurable: `RETURN_RECEPTION_PREFIX`
@@ -180,14 +180,14 @@ Used when the ERP has pre-notified containers via `ASN` message before they phys
- Web: `Warehouse > ASN LPN`, `Receiving > Receipt orders`
- RFT: `Receipts > Notices`
#### DirectTransfer — inter-warehouse ASN flow
#### DirectTransfer - inter-warehouse ASN flow
When the source order is a `<DirectTransfer>` shipment (cf. [concepts/order-outbound.md](../concepts/order-outbound.md#asn--directtransfer-flow)), closing the expedition at origin triggers an automatic `ASO01` message on the destination warehouse, pre-creating the incoming ASN container(s). The operator then receives them via RFT menu **Réception → Préavis** just like any other ASN container.
When the source order is a `<DirectTransfer>` shipment (cf. [concepts/order-outbound.md](../concepts/order-outbound.md#asn---directtransfer-flow)), closing the expedition at origin triggers an automatic `ASO01` message on the destination warehouse, pre-creating the incoming ASN container(s). The operator then receives them via RFT menu **Réception → Préavis** just like any other ASN container.
- Container deletion from SmartUI (`Entrepôt → Conteneurs ASN → Supprimer`) triggers an `ASK01` back to the ERP.
- ⚠️ The ASO/ASK messages carry **no reference to the originating shipping order or DirectTransfer header** — only the container and its stock.
- ⚠️ The ASO/ASK messages carry **no reference to the originating shipping order or DirectTransfer header** - only the container and its stock.
#### Transfer — two-warehouse ASN flow (with receipt)
#### Transfer - two-warehouse ASN flow (with receipt)
Unlike `<DirectTransfer>` (which bypasses reception at destination), a `<Transfer>`-type shipping order (`SorType = Transfer` in SOR02) **automatically creates an inbound order at destination** when expedition is confirmed at source. The destination ASN containers live on an `Asn` location in the destination warehouse.
@@ -200,7 +200,7 @@ Operator flow: RFT menu **Réception → Préavis** (of the destination warehous
**ERP messages generated:**
- `ASO01` at each container reception
- `ROF02` at inbound order closure (contains **all** received containers — the authoritative record for Transfer receptions)
- `ROF02` at inbound order closure (contains **all** received containers - the authoritative record for Transfer receptions)
- `ASK01` when closing a partially-received inbound order (to drop non-arrived containers)
> ⚠️ Neither `ASO01` nor `ASK01` carries the transfer header info. For `<Transfer>` flows the ERP **must** consume `ROF02`.
@@ -269,7 +269,7 @@ Receipts can be closed **manually** or **automatically**.
### Manual Closing
- Done from web interface or RFT at any time — full quantity not required.
- Done from web interface or RFT at any time - full quantity not required.
- If linked to receipt orders and all ordered stock received → receipt order = _Completed_; else = _Partially received_.
- Stock allocation across identical order lines follows: least expected qty first → oldest creation date → excess to first line allowing it.
- Process: `Reception_Close_PR_V2`
@@ -317,7 +317,7 @@ Receipts can be closed **manually** or **automatically**.
| `ASN` | ERP → WMS | Pre-notifies containers and their stock |
| `ASO` | WMS → ERP | Confirms receipt of a pre-notified container |
| `ASK` | WMS → ERP | Confirms rejection of a pre-notified container |
| `REF` | WMS → ERP | Receipt close confirmation — lists all received stock |
| `REF` | WMS → ERP | Receipt close confirmation - lists all received stock |
| `ROF` | WMS → ERP | Receipt order close confirmation |
| `STV` | WMS → ERP | Stock adjustment in pre-notified container during review |
@@ -342,7 +342,7 @@ See [concepts/labels.md](../concepts/labels.md) for complete label reference.
- Cause: Order code unknown or not yet created.
- Solution: Enable `ALLOW_CREATE_RECEPTION` to create a new receipt; or have the ERP send the `ROR` message first.
**ASN container rejected at PIE — order doesn't exist:**
**ASN container rejected at PIE - order doesn't exist:**
- Cause: Receipt order referenced in ASN message not yet in WMS.
- Solution: If `USE_EXCLUSIVE_RESERVE_STRICT_MODE` is inactive, container can still be received; reserve is formalized later. If active, resolve order absence first.
@@ -350,7 +350,7 @@ See [concepts/labels.md](../concepts/labels.md) for complete label reference.
- Cause: Receipt still has uncommitted lines or allows excess reception.
- Solution: Close manually, or verify `AutoCloseReception` is active and no line allows over-receipt.
**Quantity discrepancy at PIE — container sent to reconditioning:**
**Quantity discrepancy at PIE - container sent to reconditioning:**
- Cause: ASN pre-notified stock quantity doesn't match received stock and receipt order doesn't allow excess.
- Solution: Correct the discrepancy at the reconditioning station and retry.
@@ -360,13 +360,13 @@ See [concepts/labels.md](../concepts/labels.md) for complete label reference.
**Return receipt rejected for expired stock:**
- Cause: `RECEPTION_NUM_DAYS_PRODUCTION_DATE_MARGIN` check triggered.
- Note: Date logistic attributes are captured but expiry is **not blocked** during returns — check parameter configuration.
- Note: Date logistic attributes are captured but expiry is **not blocked** during returns - check parameter configuration.
---
## Reception Split Strategy (Mecalux France pattern)
Deployed at **ROUJE** and **NEUT** — documented from NEUT (blind reception, supplier + customer return, loose stock on equipment). When the item has a picking dedicated location (PDL), incoming stock is split at reception between two buffers so PDLs are filled to capacity directly and the overflow lands in reserve.
Deployed at **ROUJE** and **NEUT** - documented from NEUT (blind reception, supplier + customer return, loose stock on equipment). When the item has a picking dedicated location (PDL), incoming stock is split at reception between two buffers so PDLs are filled to capacity directly and the overflow lands in reserve.
**Flow:**
@@ -396,7 +396,7 @@ Deployed at **ROUJE** and **NEUT** — documented from NEUT (blind reception, su
| 3 | PICKING buffer | Dedicated picking locations | Item assigned, destination zone = PICKING |
| 4 | RESERVE buffer | Pallet rack locations | Destination zone = PALETTE |
**Split logic (custom workflow) — rules applied after stock reception:**
**Split logic (custom workflow) - rules applied after stock reception:**
| Situation | Action |
|---|---|
@@ -408,8 +408,8 @@ Deployed at **ROUJE** and **NEUT** — documented from NEUT (blind reception, su
> ⚠️ Stock dropped on the RESERVE buffer **must** be on a container (existing LPN or a newly generated code).
**Customs required:**
- `Equipment_Unload_ProductUnloadOnContainer_UI` — hide the free-drop button when `location.code == "RESERVE"`
- `Equipment_Unload_ProductUnloadAllStockOnContainer_UI` — idem
- `Equipment_Unload_ProductUnloadOnContainer_UI` - hide the free-drop button when `location.code == "RESERVE"`
- `Equipment_Unload_ProductUnloadAllStockOnContainer_UI` - idem
- Custom workflow after reception that computes the split and generates two drop tasks
Reference implementation: [NEUT-58](https://easywmsfrance.atlassian.net/browse/NEUT-58).
@@ -435,12 +435,12 @@ Reference implementation: [NEUT-58](https://easywmsfrance.atlassian.net/browse/N
## Related
- [concepts/container.md](../concepts/container.md) — LPN structure, statuses, ASN pre-notification
- [concepts/order-inbound.md](../concepts/order-inbound.md) — Receipt orders (ROR message), inbound lifecycle
- [concepts/putaway.md](../concepts/putaway.md) — What happens after stock is received
- [concepts/stock.md](../concepts/stock.md) — Stock records created during reception
- [concepts/product-item.md](../concepts/product-item.md) — Item reception profiles, logistic attributes captured at receipt
- [concepts/quality-control.md](../concepts/quality-control.md) — Incoming stock quality locks
- [concepts/labels.md](../concepts/labels.md) — LPN and item labels at reception
- [concepts/erp-interface.md](../concepts/erp-interface.md) — ROR, ASN, ASO, ASK, REF, ROF message definitions
- [concepts/transactions.md](../concepts/transactions.md) — CON.RECEP, STK.RECEP, CON.ASN.001, REC.CLS
- [concepts/container.md](../concepts/container.md) - LPN structure, statuses, ASN pre-notification
- [concepts/order-inbound.md](../concepts/order-inbound.md) - Receipt orders (ROR message), inbound lifecycle
- [concepts/putaway.md](../concepts/putaway.md) - What happens after stock is received
- [concepts/stock.md](../concepts/stock.md) - Stock records created during reception
- [concepts/product-item.md](../concepts/product-item.md) - Item reception profiles, logistic attributes captured at receipt
- [concepts/quality-control.md](../concepts/quality-control.md) - Incoming stock quality locks
- [concepts/labels.md](../concepts/labels.md) - LPN and item labels at reception
- [concepts/erp-interface.md](../concepts/erp-interface.md) - ROR, ASN, ASO, ASK, REF, ROF message definitions
- [concepts/transactions.md](../concepts/transactions.md) - CON.RECEP, STK.RECEP, CON.ASN.001, REC.CLS