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/operations/troubleshooting.md
+29 -29
View File
@@ -49,11 +49,11 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Cause:** Order code unknown to WMS or ROR message not yet received from ERP.
- **Solution:** Enable `ALLOW_CREATE_RECEPTION` to allow blind receipt creation; or have ERP resend the ROR message first.
### ASN container rejected at PIE — order doesn't exist
### ASN container rejected at PIE - order doesn't exist
- **Cause:** The receipt order referenced in the ASN message has not yet arrived in WMS.
- **Solution:** If `USE_EXCLUSIVE_RESERVE_STRICT_MODE` is inactive, container can still be received and the reserve is formalized later. If active, resolve the absent receipt order first before retrying PIE entry.
### Quantity discrepancy at PIE — container sent to reconditioning
### Quantity discrepancy at PIE - container sent to reconditioning
- **Cause:** ASN pre-notified quantity doesn't match the received quantity, and the receipt order does not allow excess.
- **Solution:** Correct the discrepancy at the reconditioning station, then retry induction into the PIE.
@@ -79,7 +79,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
### Transfer receipt order has no ASN
- **Cause:** The source warehouse did not close the corresponding Transfer-type shipping order.
- **Solution:** Verify the source warehouse has closed the transfer shipping order — ASN is auto-generated at that point.
- **Solution:** Verify the source warehouse has closed the transfer shipping order - ASN is auto-generated at that point.
### Order stuck in "Receiving" status
- **Cause:** Associated receipts are still open (not yet closed).
@@ -97,11 +97,11 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
## 2. Putaway
### No valid location found — manual warehouse
### No valid location found - manual warehouse
- **Cause:** All strategies exhausted; no location meets the combination of criteria + restrictions + rules. Common causes: all eligible zones full, location type mismatch, strategy sequence incomplete.
- **Solution:** Operator must manually select a destination. Review: strategy sequence coverage, restrictions not overly restrictive, no locations marked full or locked.
### No valid location found — automatic warehouse (rejection task generated)
### No valid location found - automatic warehouse (rejection task generated)
- **Cause:** All aisles at the relocation percentage limit, no route from current station to any candidate, or weight limit exceeded everywhere.
- **Solution:** Container is diverted to rejection station. Review aisle relocation configuration, available routes, and weight constraints.
@@ -144,7 +144,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Solution:** Check lock type configuration. If the reason for the lock is resolved, unlock the LPN and re-process using alternative stock.
### Cannot modify LPN type or division type
- **Cause:** LPN is not empty — still contains stock.
- **Cause:** LPN is not empty - still contains stock.
- **Solution:** Pick out or move all stock from the LPN, then change the type.
### ASN LPN cannot be deleted
@@ -175,7 +175,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Cause:** Stock is prepared for a shipping order inside a client container.
- **Solution:** Un-prepare the stock via Shipping management, then adjust.
### Adjustment fails — reason required
### Adjustment fails - reason required
- **Cause:** No adjustment reason selected; none configured for the Adjustment capture process.
- **Solution:** Create reasons in `Masters > Adjustment reasons`; select one before submitting the adjustment.
@@ -195,7 +195,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
## 5. Picking / Order Preparation
### Order line stays incomplete — no stock assigned
### Order line stays incomplete - no stock assigned
- **Cause:** All stock assignment strategies exhausted without finding eligible stock. Typical causes: stock status blocks picking, count task active on the picking location, no PDL configured for item, extraction errors at candidate locations.
- **Solution:** Check stock statuses, cancel any active count tasks on the location, verify PDL configuration, resolve extraction errors.
@@ -267,7 +267,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Cause:** WMS-ERP integration issue, or order was closed without an active ERP connection.
- **Solution:** Check integration configuration; retry via forced resend if the functionality is available.
### Cannot cancel order — stock already prepared
### Cannot cancel order - stock already prepared
- **Cause:** Picking tasks have been completed; stock is in a client container.
- **Solution:** Undo preparation (un-prepare from the consolidation or truck loading view) before canceling.
@@ -312,14 +312,14 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
## 8. Count / Stock Adjustment
### Count order stuck in "Releasing"
- **Cause:** Automatic warehouse — containers are still moving at release time.
- **Cause:** Automatic warehouse - containers are still moving at release time.
- **Solution:** Wait until all containers have reached a static location, then release the count order.
### Count line shows conflict icon — no stock
### Count line shows conflict icon - no stock
- **Cause:** Item count line requested for an item with zero stock in the warehouse.
- **Solution:** Use "Force Close" to finalize the line; review item master to understand the discrepancy.
### Count line shows conflict icon — location not configured for count
### Count line shows conflict icon - location not configured for count
- **Cause:** Location does not have the "Allow count" flag enabled in EasyS.
- **Solution:** Fix the location configuration in EasyS, or delete the problematic line.
@@ -332,7 +332,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Expected behavior:** Task distribution adjusts dynamically. Fine-tune schedule parameters if distribution is too uneven.
### Cannot re-release a cycle count after cancel
- **Cause:** By design — cycle count orders are non-re-releasable.
- **Cause:** By design - cycle count orders are non-re-releasable.
- **Solution:** Create a new manual count for the affected locations.
### No adjustment reasons visible on RFT
@@ -384,14 +384,14 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
- **Solution:** Assign different equipment; check equipment-container type compatibility configuration.
### Task cannot be manually completed
- **Cause:** Task type is picking, counting, stock replenishment, kit assembly, or consolidation — these must be completed through their respective process screens.
- **Cause:** Task type is picking, counting, stock replenishment, kit assembly, or consolidation - these must be completed through their respective process screens.
- **Solution:** Complete via the appropriate screen (picking station, count screen, etc.).
### Movement stuck "In Execution"
- **Cause:** Automatic warehouse malfunction or communication failure.
- **Solution:** Use "Movement Release" to reset the movement back to Pending; investigate the automation incident.
### Task canceled — container not found at location
### Task canceled - container not found at location
- **Cause:** Operator reported the wrong location at cancellation, or the container was moved without a system record.
- **Solution:** Run a count on the expected location; use Lost & Found if needed.
@@ -403,7 +403,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
## 11. AGV & Pallet Shuttle
### AGV notification events — full error code table
### AGV notification events - full error code table
| Code | Error |
|------|-------|
@@ -419,10 +419,10 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
| 2003 | Extraction error at non-storage location |
| 2004 | Putaway error at non-storage location |
| 2005 | Manual cancellation from AGV interface |
| 2500 | Communication error — sending order |
| 2501 | Communication error — priority update |
| 2502 | Communication error — cancellation |
| 2503 | Communication error — destination change |
| 2500 | Communication error - sending order |
| 2501 | Communication error - priority update |
| 2502 | Communication error - cancellation |
| 2503 | Communication error - destination change |
### AGV extraction error
- **Behavior:** No container found at pickup location.
@@ -448,7 +448,7 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
### Pallet Shuttle low battery
- **Behavior:** PS completes current tasks → returns to pickup position → disconnects → awaits AGV dispatch to charging station. If no charging station is available: user is notified.
### PS task in process — cannot be canceled
### PS task in process - cannot be canceled
- **Cause:** AGV system is already involved in the movement.
- **Note:** Only tasks in "Pending" state (waiting/pending shipping with CREATE action) can be canceled. Tasks in any other state must complete.
@@ -556,11 +556,11 @@ Organized by **symptom category**. Each entry: symptom → cause → solution. F
## Related
- [Parameters](../concepts/parameters.md) — Full parameter reference; values controlling most behaviors above
- [ERP Interface](../concepts/erp-interface.md) — All ERP message types, fields, and error codes
- [Transactions](../concepts/transactions.md) — Transaction codes for audit trail investigation
- [Security](../architecture/security.md) — Role and permission configuration
- [System Architecture](../architecture/overview.md) — IIS pools, background jobs, infrastructure
- [Quality Control](../concepts/quality-control.md) — Stock status lock/unlock system
- [AGV](../modules/agv.md) — Full AGV error code reference
- [Pallet Shuttle](../modules/pallet-shuttle.md) — PS diagnostics and error handling
- [Parameters](../concepts/parameters.md) - Full parameter reference; values controlling most behaviors above
- [ERP Interface](../concepts/erp-interface.md) - All ERP message types, fields, and error codes
- [Transactions](../concepts/transactions.md) - Transaction codes for audit trail investigation
- [Security](../architecture/security.md) - Role and permission configuration
- [System Architecture](../architecture/overview.md) - IIS pools, background jobs, infrastructure
- [Quality Control](../concepts/quality-control.md) - Stock status lock/unlock system
- [AGV](../modules/agv.md) - Full AGV error code reference
- [Pallet Shuttle](../modules/pallet-shuttle.md) - PS diagnostics and error handling