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/stock.md
+19 -19
View File
@@ -39,11 +39,11 @@ last_compiled: "2026-04-17"
## Overview
A **stock record** (stock line) is the physical instance of an item in the warehouse at a specific moment — a quantity of a particular item, owned by a specific owner, in a specific location or container, with specific logistic attributes and status. It is distinct from the item master: the item defines what the product is; the stock defines how much of it exists, where, and in what state.
A **stock record** (stock line) is the physical instance of an item in the warehouse at a specific moment - a quantity of a particular item, owned by a specific owner, in a specific location or container, with specific logistic attributes and status. It is distinct from the item master: the item defines what the product is; the stock defines how much of it exists, where, and in what state.
Stock is created when goods are received, consumed when goods are shipped, and transformed (split, merged, adjusted) throughout warehouse operations. The WMS maintains an exact, real-time view of all stock across every location and container in the warehouse. All WMS processes (putaway strategies, stock assignment for outbound orders, replenishment, counting) operate against stock records.
A single item in the warehouse can have many stock lines — one per unique combination of container, logistic attributes, and status. For example, the same SKU in three different lot numbers stored in two locations will produce at least 6 separate stock lines.
A single item in the warehouse can have many stock lines - one per unique combination of container, logistic attributes, and status. For example, the same SKU in three different lot numbers stored in two locations will produce at least 6 separate stock lines.
## Types
@@ -53,7 +53,7 @@ Stock is classified by its storage context and status:
- **Containerized stock**: stock inside a container (LPN). The container holds the stock and can be moved as a unit. The stock line references both the container and the location of the container.
- **Loose stock**: stock directly in a location, not in a container. Common in conventional manual locations with picking dedicated partitions.
- **Client stock**: stock that has been prepared (picked) for a specific outbound order, now in a client (outbound) container. Special rules apply — quantity, UoM, and logistic attributes cannot be adjusted like regular stock.
- **Client stock**: stock that has been prepared (picked) for a specific outbound order, now in a client (outbound) container. Special rules apply - quantity, UoM, and logistic attributes cannot be adjusted like regular stock.
- **ASN stock**: stock pre-notified by the ERP but not yet physically received. Located in the virtual ASN location. Cannot be adjusted.
### By status
@@ -62,7 +62,7 @@ Stock carries up to three parallel status dimensions:
| Status type | Description | Set by |
|---|---|---|
| **System status** | Internal WMS status (e.g., normal, reserved, assigned) | Automatic — driven by stock assignment and task creation |
| **System status** | Internal WMS status (e.g., normal, reserved, assigned) | Automatic - driven by stock assignment and task creation |
| **User status** | Quality or business-driven lock (e.g., "Quarantine", "Hold") | Manually by user, or via ERP STR message. Has optional end date. |
| **Receiving status** | Quality control status set during reception | At reception, automatically based on receipt order configuration |
@@ -192,7 +192,7 @@ Stock adjustments allow operators to correct discrepancies between the WMS recor
> **WSC / SCR**: To get the complete stock image, the ERP sends an **SCR** request and EasyWMS responds with a **WSC** file. This can be:
> - Grouped by item (one line per item/owner/status)
> - Detailed (with location and container)
> - The WSC does NOT discriminate "available to sell" — use stock status filtering for that.
> - The WSC does NOT discriminate "available to sell" - use stock status filtering for that.
> - Stock at 0 can optionally be included (configurable).
> - Can be sent on-demand or on a scheduled basis (once/day or at intervals).
@@ -211,7 +211,7 @@ EasyWMS supports a **double validation** mechanism for stock adjustments. When a
Configuration (per item, in **inventory profile**):
| Setting | Behavior |
|---------|---------|
| **Never** | No double validation — adjustments applied immediately |
| **Never** | No double validation - adjustments applied immediately |
| **Always** | All adjustments require manager validation |
| **By tolerance** | Requires validation only if delta exceeds a configured threshold (absolute value or %) |
@@ -271,7 +271,7 @@ The grouped stock reports provide aggregate views of stock without the per-line
|---|---|---|
| Cannot adjust ASN stock | Stock is in pre-notified container not yet received | Receive the container first via the reception process |
| Cannot adjust client stock | Stock is prepared for a shipping order in a client container | Un-prepare the stock via shipping management, then adjust |
| Adjustment fails — reason required | No adjustment reason selected | Create reasons in Masters; select one before adjusting |
| Adjustment fails - reason required | No adjustment reason selected | Create reasons in Masters; select one before adjusting |
| Stock not visible in view | Stock in virtual location (ASN, Lost_Found) or filtered out | Remove filters; check virtual locations explicitly |
| Stock in lock not assignable | User or receiving status prevents shipping | Release the lock (manually or via STR from ERP); or add required status to SOR line |
| Quantity jumps after decrease | Other stock from the same item was consolidated | Separate stock lines if needed; use "From multiple receptions" selection |
@@ -279,15 +279,15 @@ The grouped stock reports provide aggregate views of stock without the per-line
## Related
- [[container]] — stock is either containerized (in an LPN) or loose; container locks and type affect stock eligibility
- [[location]] — every stock record has a location; location logics (allow shipping, allow replenishment) determine eligibility
- [[product-item]] — item defines the static attributes; stock is the physical quantity with runtime attributes
- [[reception]] — stock is created during the reception process; receiving status can be set at receipt
- [[picking]] — stock is assigned and picked for outbound orders; picking consumes stock quantity
- [[shipping]] — shipping closes orders and removes stock from the warehouse
- [[count]] — counts verify the accuracy of stock records; discrepancies trigger adjustments
- [[stock-adjustment]] — detailed adjustment procedures (quantity, UoM, logistic attributes)
- [[stock-assignment]] — the allocation engine that binds stock lines to outbound order line details (`StockAssignProcess_*` workflows, assignment types, customisation points)
- [[order-outbound]] — stock assignment links specific stock lines to SOR lines; reserves and assignments
- [[task]] — tasks move stock between locations; running tasks block certain stock adjustments
- [[erp-interface]] — STV message reports stock changes; SCR/WSC for stock contrasts; STR for status locks
- [[container]] - stock is either containerized (in an LPN) or loose; container locks and type affect stock eligibility
- [[location]] - every stock record has a location; location logics (allow shipping, allow replenishment) determine eligibility
- [[product-item]] - item defines the static attributes; stock is the physical quantity with runtime attributes
- [[reception]] - stock is created during the reception process; receiving status can be set at receipt
- [[picking]] - stock is assigned and picked for outbound orders; picking consumes stock quantity
- [[shipping]] - shipping closes orders and removes stock from the warehouse
- [[count]] - counts verify the accuracy of stock records; discrepancies trigger adjustments
- [[stock-adjustment]] - detailed adjustment procedures (quantity, UoM, logistic attributes)
- [[stock-assignment]] - the allocation engine that binds stock lines to outbound order line details (`StockAssignProcess_*` workflows, assignment types, customisation points)
- [[order-outbound]] - stock assignment links specific stock lines to SOR lines; reserves and assignments
- [[task]] - tasks move stock between locations; running tasks block certain stock adjustments
- [[erp-interface]] - STV message reports stock changes; SCR/WSC for stock contrasts; STR for status locks