lint(standard): corrections completes mode standard
- 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:
@@ -36,7 +36,7 @@ last_compiled: "2026-04-10"
|
||||
|
||||
A **receipt order** (also called inbound order) is the WMS document that tracks expected incoming stock. It represents a list of items or containers expected to arrive at the warehouse, serving as the basis for the reception process. Receipt orders allow the warehouse to plan dock resources, validate quantities, and close the loop with the ERP upon receipt.
|
||||
|
||||
Most receipt orders originate in the ERP (purchase orders to suppliers, customer return orders, transfer orders from other warehouses) and arrive via messaging. Easy WMS also allows manual creation of receipt orders directly in the UI. Receipt orders are optional — stock can be received without one (blind reception) — but they enable quantity control, automatic label printing, and ERP reconciliation.
|
||||
Most receipt orders originate in the ERP (purchase orders to suppliers, customer return orders, transfer orders from other warehouses) and arrive via messaging. Easy WMS also allows manual creation of receipt orders directly in the UI. Receipt orders are optional - stock can be received without one (blind reception) - but they enable quantity control, automatic label printing, and ERP reconciliation.
|
||||
|
||||
The receipt order is distinct from the **receipt** (the actual WMS event of receiving stock physically). One receipt order can be fulfilled by one or more receipts; one receipt can be associated with one or more receipt orders.
|
||||
|
||||
@@ -47,7 +47,7 @@ Receipt orders (and their associated receipts) are categorized by type, which co
|
||||
| Type | Description | Typical origin |
|
||||
|---|---|---|
|
||||
| **Supplier** | Stock arriving from a vendor. Lines specify items, expected quantities, and UoM. Stock may arrive in any presentation (pack, box, etc.) regardless of the line's UoM. Logistic attributes and quality status can optionally be pre-set by the ERP. | ERP purchase order (PO) |
|
||||
| **Return** | Customer returns — damaged or surplus stock. Similar line structure to Supplier type. | ERP return authorization |
|
||||
| **Return** | Customer returns - damaged or surplus stock. Similar line structure to Supplier type. | ERP return authorization |
|
||||
| **Transfer** | Stock transferred from another warehouse in the same organization. Stock always arrives in containers, which are pre-notified as ASN containers at the destination. Lines specify containers, items, and quantities. | ERP transfer order; automatic when source shipping order closes (Transfer type) |
|
||||
|
||||
Receipt orders also have a **class** for additional personalization of the reception process (custom flow variants, label types, etc.). Classes do not change the type logic but allow further differentiation.
|
||||
@@ -81,7 +81,7 @@ Each line identifies the expected item/container and quantity:
|
||||
| **Line number** | Unique line identifier within the order |
|
||||
| **Status** | Line status (mirrors order status progression) |
|
||||
| **Container** | Expected or received container code (Transfer type or ASN) |
|
||||
| **Item** | Item code expected; alternatively, a presentation alias (GTIN/EAN) can be used — in this case, only stock of that EAN presentation is received against this line |
|
||||
| **Item** | Item code expected; alternatively, a presentation alias (GTIN/EAN) can be used - in this case, only stock of that EAN presentation is received against this line |
|
||||
| **Owner** | Owner of the expected stock |
|
||||
| **Quantity** | Expected quantity |
|
||||
| **UoM** | Unit of measure (usually base UoM; can be a presentation if packaging is known) |
|
||||
@@ -130,7 +130,7 @@ Each line identifies the expected item/container and quantity:
|
||||
|
||||
### Messages: ERP → WMS
|
||||
|
||||
#### ROR — Receipt Order Request
|
||||
#### ROR - Receipt Order Request
|
||||
|
||||
Creates, modifies, or cancels receipt orders.
|
||||
|
||||
@@ -155,7 +155,7 @@ Key ROR fields:
|
||||
- Line `LneStockStatus`: forced receiving status for stock on this line
|
||||
- Line reserves (`LneStkRsvSORCode` / `LneStkRsvAccCode`): pre-allocate received stock to a specific outbound order or account
|
||||
|
||||
#### ASN — Advanced Shipping Notice
|
||||
#### ASN - Advanced Shipping Notice
|
||||
|
||||
Pre-notifies containers expected at the warehouse. Containers are created in the virtual ASN location.
|
||||
|
||||
@@ -176,11 +176,11 @@ ASN key fields: `ContainerCode`, `ContainerType`, `ReceiptOrderCode`, `NumExpect
|
||||
|
||||
### Messages: WMS → ERP
|
||||
|
||||
#### ROC — Receipt Order status Change
|
||||
#### ROC - Receipt Order status Change
|
||||
|
||||
Sent by WMS when an order changes status. Fields: `RorCode`, `Status` (Waiting / ReceptionPending / Receiving / PartiallyReceived / Complete / Expired / Canceled), `UpdateDate` (UTC timestamp).
|
||||
|
||||
#### ROF — Receipt Order Finalization
|
||||
#### ROF - Receipt Order Finalization
|
||||
|
||||
Sent when an order is closed or canceled. Two versions:
|
||||
- **ROF01**: includes receipt data + order data + stock received. Sent on order close/cancel AND on receipt close (even if receipt has no order).
|
||||
@@ -188,11 +188,11 @@ Sent when an order is closed or canceled. Two versions:
|
||||
|
||||
ROF01/ROF02 key fields per line: `LneItemCode`, `LneOwnerCode`, `LneQtyExpected`, `LneQtyReceived`, `LneQtyFree`, `LneQtyUoMCode`.
|
||||
|
||||
#### ASO — ASN receipt confirmation (WMS → ERP)
|
||||
#### ASO - ASN receipt confirmation (WMS → ERP)
|
||||
|
||||
Sent when an ASN pre-notified container is physically received. Confirms item, owner, quantity, and optionally the receiving status (`LneStaStatus`). Variants mirror ASN variants (stacked, matched on dummy, with divisions).
|
||||
|
||||
#### STR — Stock lock/unlock request (ERP → WMS)
|
||||
#### STR - Stock lock/unlock request (ERP → WMS)
|
||||
|
||||
Although STR is a request (not a receipt order message), it is closely related to inbound quality control. The ERP requests Easy WMS to apply or remove a user status on stock (e.g., lock a lot for quality reasons):
|
||||
- `Operation S`: add user status (lock) with optional quarantine end date
|
||||
@@ -241,11 +241,11 @@ WMS responds with one or more **STC** messages confirming the modified stock.
|
||||
|
||||
## Related
|
||||
|
||||
- [[reception]] — the physical reception process that fulfills receipt orders; dock/PIE/ASN reception modes all reference receipt orders
|
||||
- [[container]] — ASN pre-notifies containers; Transfer-type receipt orders always involve containers
|
||||
- [[product-item]] — receipt order lines reference items by code or alias; reception profile governs behavior
|
||||
- [[stock]] — receipt creates stock; receiving status from ROR line is applied to created stock
|
||||
- [[putaway]] — after reception, putaway tasks move stock from dock to storage; receipt order type affects putaway strategy eligibility
|
||||
- [[order-outbound]] — receipt orders can include reserves for outbound orders (cross-dock scenario); transfer orders create an outbound order at source
|
||||
- [[crossdocking]] — ASN containers with exclusive reserves enable direct crossdocking on receipt
|
||||
- [[erp-interface]] — ROR (in), ASN (in), ROC (out), ROF (out), ASO (out), STR (in), STC (out) messages
|
||||
- [[reception]] - the physical reception process that fulfills receipt orders; dock/PIE/ASN reception modes all reference receipt orders
|
||||
- [[container]] - ASN pre-notifies containers; Transfer-type receipt orders always involve containers
|
||||
- [[product-item]] - receipt order lines reference items by code or alias; reception profile governs behavior
|
||||
- [[stock]] - receipt creates stock; receiving status from ROR line is applied to created stock
|
||||
- [[putaway]] - after reception, putaway tasks move stock from dock to storage; receipt order type affects putaway strategy eligibility
|
||||
- [[order-outbound]] - receipt orders can include reserves for outbound orders (cross-dock scenario); transfer orders create an outbound order at source
|
||||
- [[crossdocking]] - ASN containers with exclusive reserves enable direct crossdocking on receipt
|
||||
- [[erp-interface]] - ROR (in), ASN (in), ROC (out), ROF (out), ASO (out), STR (in), STC (out) messages
|
||||
|
||||
Reference in New Issue
Block a user