màj wiki avec retour MES lot-5 AD
This commit is contained in:
Arthur Ria
@@ -0,0 +1,977 @@
|
||||
---
|
||||
title: "Glossary — EasyWMS / Mecalux"
|
||||
type: glossary
|
||||
sources:
|
||||
- wiki/concepts/container.md
|
||||
- wiki/concepts/location.md
|
||||
- wiki/concepts/stock.md
|
||||
- wiki/concepts/task.md
|
||||
- wiki/concepts/reception.md
|
||||
- wiki/concepts/putaway.md
|
||||
- wiki/concepts/picking.md
|
||||
- wiki/concepts/shipping.md
|
||||
- wiki/concepts/replenishment.md
|
||||
- wiki/concepts/order-inbound.md
|
||||
- wiki/concepts/order-outbound.md
|
||||
- wiki/concepts/product-item.md
|
||||
- wiki/concepts/erp-interface.md
|
||||
- wiki/concepts/transactions.md
|
||||
- wiki/concepts/parameters.md
|
||||
- wiki/concepts/count.md
|
||||
- wiki/concepts/cutting-stock.md
|
||||
- wiki/concepts/labels.md
|
||||
- wiki/concepts/stations.md
|
||||
- wiki/architecture/application-dictionary.md
|
||||
- wiki/architecture/overview.md
|
||||
- wiki/modules/agv.md
|
||||
- wiki/modules/pallet-shuttle.md
|
||||
- wiki/modules/multi-carrier.md
|
||||
- wiki/modules/slotting.md
|
||||
- wiki/modules/labor-management.md
|
||||
- wiki/modules/dom.md
|
||||
- sources/archives/02_Strategie_assignation_vidage_bacs.md
|
||||
- sources/archives/04_Gestion_preemballage_precolisage.md
|
||||
- sources/archives/07_Gestion_gerbabilite.md
|
||||
- sources/archives/08_Ajouter_image_fiche_article_ITM01.md
|
||||
- sources/archives/12_Articles_alternatifs.md
|
||||
- sources/archives/13_Gestion_KIT.md
|
||||
- sources/archives/14_Processus_inventaire.md
|
||||
- sources/archives/15_Configuration_ABC.md
|
||||
- sources/archives/16_Tense_Flow.md
|
||||
- sources/archives/17_Fonctionnement_routes_tournees.md
|
||||
- sources/archives/18_ASN_DirectTransfer.md
|
||||
- sources/archives/19_ASN_Transfer.md
|
||||
- sources/archives/20_Strategies_reapprovisionnement.md
|
||||
- sources/archives/21_Validation_ajustements_stock.md
|
||||
- sources/archives/22_Chargement_camion.md
|
||||
- sources/archives/23_Declencheurs_impressions.md
|
||||
- sources/archives/24_Process_assignation_stock.md
|
||||
- sources/archives/25_Strategie_remplissage_canaux.md
|
||||
- sources/archives/26_Utilisation_chariots_emplacement.md
|
||||
- sources/archives/27_Modification_sequence_SSCC.md
|
||||
- sources/archives/28_Creation_attribut_logistique_sans_capture.md
|
||||
- sources/archives/29_Split_marchandise_reception.md
|
||||
- sources/archives/30_Reapprovisionnement_2_sous_entrepots_zone_intermediaire.md
|
||||
- sources/archives/31_Picking_Manuel.md
|
||||
- sources/archives/32_Fusion_commandes_Merge.md
|
||||
- sources/archives/33_Les_poids.md
|
||||
- sources/archives/menu_rf_easywms.md
|
||||
- sources/archives/Presentation_GALILEO.md
|
||||
- sources/archives/Communication_WMS_GALILEO.md
|
||||
- sources/archives/Communication_Easy_Galileo.md
|
||||
- sources/archives/Bases_fonctionnement_robotique_EasyWMS.md
|
||||
- sources/archives/Acronymes_elements_mecaniques.md
|
||||
- sources/archives/Codes_de_station.md
|
||||
- sources/archives/Catalogue_TK.md
|
||||
- sources/archives/Convoyeur_terminologie.md
|
||||
- sources/archives/Configuration_EasyS.md
|
||||
- sources/archives/Configuration_SmartUI.md
|
||||
- sources/archives/Tests_Miniload_Gateway.md
|
||||
- sources/archives/Comprendre_logs_Gateway.md
|
||||
- sources/archives/Erreurs_Defauts_GALILEO.md
|
||||
- sources/archives/Plan_tests_stations.md
|
||||
- sources/archives/Documents_utiles.md
|
||||
- sources/archives/Organisation_projet_Robotique.md
|
||||
- sources/archives/Planning_Installation_Miniload.md
|
||||
- sources/archives/DTR_configuration_reseau_materiel.md
|
||||
- sources/archives/Automation_Dashboard.md
|
||||
- sources/archives/Changer_adresse_WMS_dans_GALILEO.md
|
||||
related:
|
||||
- architecture/application-dictionary.md
|
||||
- architecture/galileo-integration.md
|
||||
- concepts/erp-interface.md
|
||||
- concepts/transactions.md
|
||||
- concepts/parameters.md
|
||||
- concepts/mechanical-elements.md
|
||||
last_compiled: "2026-04-17"
|
||||
---
|
||||
|
||||
# Glossary — EasyWMS / Mecalux
|
||||
|
||||
All terms specific to EasyWMS (by Mecalux), including product names, abbreviations, AD element names, ERP message codes, and field names. General WMS/logistics terms are included only when EasyWMS usage differs from industry standard.
|
||||
|
||||
---
|
||||
|
||||
## A
|
||||
|
||||
**ABC classification**
|
||||
Item classification by velocity/value. A = high rotation (near pick face), B = medium, C = low. Used by putaway strategies to assign storage zones and by cycle count schedules to set count frequency. See [Product / Item](concepts/product-item.md).
|
||||
|
||||
**ABC Inclusive / Exclusive**
|
||||
Two operating modes of the ABC analysis. **Inclusive** = all items appear in the result even if they have no movement (zero-rotation items classified C). **Exclusive** = only items that had at least one movement in the analysis window are classified; others keep their current class. See [Product / Item](concepts/product-item.md#abc-classification).
|
||||
|
||||
**AD (Application Dictionary)**
|
||||
The metadata layer that defines every executable element in EasyWMS: Commands, Queries, Entities, Views, Dialogs, Events, Workflows, Background Jobs, and Parameters. Approximately 38,765 elements. All UI screens and API calls are backed by AD elements. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**AGV (Automated Guided Vehicle)**
|
||||
Self-navigating forklift or carrier used in automatic warehouses. Communicates with EasyWMS via a 10-phase protocol (phases 00–255). Also transports Pallet Shuttle carts. See [AGV](modules/agv.md).
|
||||
|
||||
**AI (Application Identifier)**
|
||||
GS1 prefix code embedded in a barcode to identify the type of data that follows. Examples: AI(00) = SSCC, AI(02) = GTIN, AI(10) = lot, AI(17) = expiry date.
|
||||
|
||||
**ALM station (Almacén — Storage)**
|
||||
Station type used as a pure storage entry/exit point. Containers are deposited at ALM stations for AS/RS retrieval to racks. In the FR/EN translation matrix: ALM (ES) = MAG (FR) = AIS (EN). See [Mechanical Elements — Station codes](concepts/mechanical-elements.md#3-station-codes--fr--es--en-matrix).
|
||||
|
||||
**AP / APC / APR (Apilador de Paletas)**
|
||||
Pallet stacker machines. **AP** = Empty Pallet Stacker, **APC** = Chain Pallet Stacker, **APR** = Roller Pallet Stacker. See [Mechanical Elements](concepts/mechanical-elements.md#1-machine--equipment-acronyms-es--en).
|
||||
|
||||
**APS200**
|
||||
Automatic Pallet Shuttle variant using supercapacitors (SUPERCAP) instead of batteries. Faster charge cycles, shorter standalone runtime. See [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
**ATC (Abatible Transportador de Cadenas)**
|
||||
Lift-up gate Chain Conveyor — chain conveyor with a retractable gate for pedestrian passage. See [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
**Automatic Aisle**
|
||||
EasyS station element representing a stacker crane (TK) or Miniload. Linked to a rack; all locations inside the rack are reachable only through this aisle. See [Galileo Simulation — §3.4](operations/galileo-simulation.md#34-automatic-aisle-tk--miniload).
|
||||
|
||||
**APS (Automated Pallet Shuttle)**
|
||||
3D compact storage system managed by the APS3D module. Locations tagged as APS or APSFIFO. The Fleet Manager controller coordinates lifts, shuttles, and conveyors. See [APS3D](modules/aps3d.md).
|
||||
|
||||
**APSFIFO**
|
||||
APS location type with strict FIFO access mode. Containers enter and exit from the same end; oldest container is always at the front. Distinct from standard APS (LIFO/random access). See [Location](concepts/location.md).
|
||||
|
||||
**AS/RS (Automated Storage and Retrieval System)**
|
||||
Generic term for the automatic warehouse machinery (AGVs, conveyors, lifts, Pallet Shuttles) that moves containers without human operators. EasyWMS coordinates AS/RS movements via AGV tasks and the Fleet Manager.
|
||||
|
||||
**ASK (ASN Rejection Confirmation)**
|
||||
Outbound ERP message. Sent when a pre-notified ASN container is rejected at the WMS (container cancelled, CON.CNL.ASN transaction). Informs ERP that the ASN was not received. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**ASN (Advanced Shipping Notice)**
|
||||
Inbound ERP message (ASN). Pre-notifies the WMS that specific containers with known contents will arrive. Creates pre-notified containers in the ASN virtual location. Multiple variants (ASN01–ASN08) for different use cases. See [ERP Interface](concepts/erp-interface.md) and [Order Inbound](concepts/order-inbound.md).
|
||||
|
||||
**ALLOW_MERGE_DIFFERENT_ACCOUNT**
|
||||
Parameter of the Multi-Carrier / Deliveries module. When `true`, the `DlvShareDeliveries` merge message accepts outbound orders from **different accounts** in the same merge group. Default is `false`. See [Order Outbound](concepts/order-outbound.md#merge-order-fusion).
|
||||
|
||||
**ASO (ASN Open Confirmation)**
|
||||
Outbound ERP message. Confirms to ERP that an ASN container has been received and put away; includes final location. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Auto-direct picking**
|
||||
Automatic warehouse picking mode where the system generates picking tasks without operator intervention; containers move via conveyors and AGVs to the workstation. See [Picking](concepts/picking.md).
|
||||
|
||||
---
|
||||
|
||||
## B
|
||||
|
||||
**Background Job**
|
||||
A scheduled server-side process running in the Background Jobs IIS pool. Examples: `TryToReplenishProductLocations`, `Delete_StockStatusJob_PR`, `CycleCountJob`, `DefragmentationPlanner`, `SlottingJob`, `AGVService`, `PSService`, `MetricGatherer`. See [Application Dictionary](architecture/application-dictionary.md) and [System Architecture](architecture/overview.md).
|
||||
|
||||
**BOM (Bill of Materials)**
|
||||
List of components required to produce a finished good. Used by the Manufacturing module (RCP01 recipe type). See [Manufacturing](modules/manufacturing.md).
|
||||
|
||||
**Buffer station**
|
||||
Station with a buffer-type location used as a transit zone. Common role for ET (transit) stations and consolidation areas. See [Stations](concepts/stations.md).
|
||||
|
||||
---
|
||||
|
||||
## C
|
||||
|
||||
**Calculated Weight (Poids calculé)**
|
||||
Container weight field derived as *Theoretical Weight − adjustments* (picks, transfers, etc.). Updated on every stock movement. See [Weights](concepts/weights.md).
|
||||
|
||||
**Channel filling strategy**
|
||||
Putaway strategy variant applied **before** standard location strategies, used for APS, compact, Pallet Shuttle, dynamic, and push-back locations. Has no sequence (first eligible wins) and requires two mandatory criteria: source stations and candidate-container stations. See [Putaway](concepts/putaway.md#channel-filling-strategies).
|
||||
|
||||
**Client container (Client LPN)**
|
||||
A container whose stock is assigned to a specific shipping order. The `Is client LPN` flag is true. Client containers are created during picking and track the prepared stock from pick face to shipping dock. See [Container](concepts/container.md).
|
||||
|
||||
**Client stock**
|
||||
Stock that is inside a client container — i.e., stock that has been prepared for a specific outbound order. Cannot be adjusted without first un-preparing the shipment.
|
||||
|
||||
**CMC (Container Movement Confirmation)**
|
||||
Inbound ERP request message. Asks the WMS to move a container between locations. Generates a Manual Movement task. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**CME station (Control Miniload Entrée)**
|
||||
Control station at the entry of a Miniload/TK. If the downstream TE is full, CME recirculates the container to avoid collision. Must report a "route full" status (3) when saturated — see [Stations](concepts/stations.md#route-configuration-in-easys-robotics) and [Galileo Integration](architecture/galileo-integration.md).
|
||||
|
||||
**Conclure (replenishment)**
|
||||
French SmartUI label for the **Top-off / Particular Demand** replenishment strategy. Pre-brings stock based on reserved outbound orders on the picking locations. See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**Count Profile validation mode**
|
||||
Setting on the item's count profile that decides whether a count discrepancy needs manual validation. Three values: **Never** (discrepancy applied automatically), **Always** (every discrepancy requires SuperAdmin/Admin validation), **According to tolerance** (validation only if the quantity or value deviation exceeds a configured threshold). See [Stock Adjustment](concepts/stock-adjustment.md) and [Count](concepts/count.md).
|
||||
|
||||
**Cobot**
|
||||
Collaborative robot (robotic arm with suction cup) integrated with HPKS-R for picking tasks. Always paired with a manual operator station to handle exceptions. See [Cobot](modules/cobot.md).
|
||||
|
||||
**COF (Count Order Fulfilled)**
|
||||
Outbound ERP message. Sent when a count order is closed. Contains the final count results and any adjustments made. See [ERP Interface](concepts/erp-interface.md) and [Count](concepts/count.md).
|
||||
|
||||
**CommandExecute API**
|
||||
One of three EasyWMS API families. Used to invoke AD Command elements that change system state: `POST /api/commands/{commandName}`. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**CON.* transactions**
|
||||
Transaction prefix for container-level events. Key types: `CON.RECEP` (reception), `CON.PUT` (putaway), `CON.MOVE` (movement), `CON.SHIP` (shipping), `CON.VASDONE` (VAS completed), `CON.CNL.ASN` (ASN rejection). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**Container**
|
||||
See **LPN**.
|
||||
|
||||
**Container lock type**
|
||||
A named restriction applied to a container that blocks specific operations (picking, replenishment, movement, shipping). Multiple locks can be applied simultaneously unless one is **Exclusive**. Configured in `Masters > Lock Types > Container Lock Types`. See [Container](concepts/container.md) and [Quality Control](concepts/quality-control.md).
|
||||
|
||||
**COR (Count Order Request)**
|
||||
Inbound ERP message. Asks the WMS to create a count order for specified items, locations, or stock. Response: COF. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**COU.* transactions**
|
||||
Transaction prefix for count lifecycle events: `COU.CST` (count started), `COU.END` (count ended), `COU.CLS` (count closed), `COU.CNL` (count canceled). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**Crossdocking (XD)**
|
||||
Process of routing inbound stock directly to outbound orders without storage. Two types: **opportunity crossdocking** (direct to dock) and **crossdocking to warehouse** (dedicated XD locations). See [Crossdocking](concepts/crossdocking.md).
|
||||
|
||||
**CST.STK**
|
||||
Transaction code for a stock status change (quality lock applied or removed). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**Cutting stock**
|
||||
Items sold or stored by linear measure (length/stretch). Non-consolidating UoM. Requires a cutting profile and special handling throughout reception, picking, shipping, and counting. See [Cutting Stock](concepts/cutting-stock.md).
|
||||
|
||||
**CdP (Chef de Projet)**
|
||||
Project Manager (Mecalux France). Owns the `master` branch and the merges `develop`→`master` at MEP and post-Hypercare. Refuses TLM hand-off if `develop` still exists. See [Git Branch Lifecycle](operations/git-branch-lifecycle.md).
|
||||
|
||||
**CST_ (custom prefix)**
|
||||
Naming prefix mandatory on every custom AD element added or modified by a developer in a custom application. Exceptions: elements visible to the client (e.g. SmartUI parameters) and sub-elements of an already-prefixed top-level element (e.g. activities inside a `CST_` workflow). Verified during code review. See [Code Review Process](operations/code-review-process.md).
|
||||
|
||||
---
|
||||
|
||||
## D
|
||||
|
||||
**DBLink (Oracle Database Link)**
|
||||
A persistent connection object in Oracle that allows queries against tables in a remote database. In the AGV module context, a DBLink connects Oracle (WMS schema `db_read`) to PostgreSQL (AGV exchange tables) via the **dg4odbc** heterogeneous gateway and an ODBC System DSN. See [AGV Installation Guide](operations/agv-installation.md).
|
||||
|
||||
**dg4odbc (Database Gateway for ODBC)**
|
||||
Oracle component that enables connections from Oracle to non-Oracle databases through ODBC drivers. Used by the AGV module to bridge Oracle and PostgreSQL. Configured through `initPostgreSQL35W.ora`, `tnsnames.ora`, and `listener.ora`. The `(HS=OK)` flag in `tnsnames.ora` identifies it as a Heterogeneous Service. See [AGV Installation Guide](operations/agv-installation.md).
|
||||
|
||||
**Decision station (type 63)**
|
||||
Automatic conveyor element that routes containers to different destinations based on WMS logic (e.g., putaway vs. rejection, different staging zones). See [Stations](concepts/stations.md).
|
||||
|
||||
**Defragmentation**
|
||||
Process of moving containers between locations to optimize space and picking efficiency. Two strategies: **rotation** (by ABC class) and **shipping** (pre-position for orders). Automatic warehouse only. See [Defragmentation](concepts/defragmentation.md).
|
||||
|
||||
**Division (location cart)**
|
||||
A subdivision of a **Location cart** used for wave / group picking. Each division is identified and can be tied to a specific order or wave, so one cart holds several concurrent pickings without mixing stock. See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement).
|
||||
|
||||
**DirectTransfer**
|
||||
Value of the `<SorType>` field in the `SOR(01|02)` shipping order message, used for inter-warehouse transfers. Closing the expedition at origin automatically generates an `ASO01` on destination, pre-creating the incoming ASN container. Deleting the container from SmartUI triggers `ASK01`. Both messages carry **no reference to the source shipping order**. See [Order Outbound](concepts/order-outbound.md#asn--directtransfer-flow) and [Reception](concepts/reception.md#directtransfer--inter-warehouse-asn-flow).
|
||||
|
||||
**Delete_StockStatusJob_PR**
|
||||
Background job. Automatically removes time-expired stock quality locks. Runs every 15 minutes by default. See [Quality Control](concepts/quality-control.md).
|
||||
|
||||
**DlvShareDeliveries**
|
||||
Multi-Carrier XML message used to **merge** (fuse) several outbound orders into a single preparation group. The merged orders share stock assignment, client containers, and carrier call. Eligibility rules: same account, same site, same route/address, same carrier (the account rule is lifted by `ALLOW_MERGE_DIFFERENT_ACCOUNT`). See [Order Outbound](concepts/order-outbound.md#merge-order-fusion) and [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Delivery (Multi-Carrier)**
|
||||
Entity combining a carrier + consignee for a shipment. Holds tracking number, delivery note, and carrier label. Created when a shipping order is packaged at a Multi-Carrier station. See [Multi-Carrier](modules/multi-carrier.md).
|
||||
|
||||
**Dialog (AD)**
|
||||
An AD element type representing a multi-step operator flow — typically a wizard or guided process on the RF terminal or SmartUI. Examples: `ReceptionDialog`, `PickingDialog`, `CountDialog`. Each step is a form with specific validations. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**DOM (Distributed Order Management)**
|
||||
EasyWMS module for multi-node warehouse networks. Orchestrates sales orders across nodes using a 5-stage engine (region → carrier → stock → capacity → strategies). See [DOM](modules/dom.md).
|
||||
|
||||
**Double validation**
|
||||
Inventory control process where count discrepancies or adjustments require a second approval by a supervisor/manager before being committed to stock. Controlled via item count profile and `DOUBLE_VALIDATION_ACTIVE` parameter. See [Stock Adjustment](concepts/stock-adjustment.md) and [Count](concepts/count.md).
|
||||
|
||||
**DeleteEmptyContainers**
|
||||
Station/location parameter that decides what happens to empty supports. Robotics default for automated locations: **Not Delete**. Picking stations (PK) may use `Delete` or `Ask` when operators physically remove empty containers. See [Galileo Simulation — §3.1](operations/galileo-simulation.md#31-location--container-settings).
|
||||
|
||||
**DTR (Document Technique de Référence)**
|
||||
Reference document listing all technical elements for a robotics project (hardware, IPs, services, accounts) and the responsibility split between Mecalux and the client. Template on [Confluence](https://easywmsfrance.atlassian.net/wiki/spaces/EF/pages/3000562515980). See [Robotics Project Lifecycle — §2](operations/robotics-project-lifecycle.md#2-dtr--document-technique-de-référence).
|
||||
|
||||
---
|
||||
|
||||
## E
|
||||
|
||||
**Exiger (replenishment)**
|
||||
French SmartUI label for the **Dynamic / On-Demand** replenishment strategy — replenishment triggered when picking consumption empties a picking location, regardless of threshold. See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**Est renseigné (Count)**
|
||||
SmartUI flag on a Count Order Line (`CountOrderLineVList`) that controls whether the line is **informed** (expected quantity visible to operator) or **blind** (hidden). Historical ERP sends it via COR `IsInformed`; SmartUI can toggle it per line afterwards. See [Count](concepts/count.md#blind-vs-informed-mode).
|
||||
|
||||
**EAN (European Article Number)**
|
||||
Barcode standard for item identification. EAN-13 is the most common; used on item labels and for carton identification. Related to GS1/GTIN standards. See [Labels](concepts/labels.md).
|
||||
|
||||
**EasyS**
|
||||
Mecalux's layout configuration tool for EasyWMS, and **3D robotics simulator** that speaks the same protocol as GALILEO. Used to: (1) define physical warehouse topology — aisles, racks, locations, stations, equipment groups, routes; (2) run a full simulation with an EasyWMS Gateway for development and demos (port 3000, Start → Simulation 3D, PIE injection via PIE Info tab). Shared demo VM at Mecalux France: ALL on LYOITSW02 (`10.58.10.75`). See [Galileo Simulation](operations/galileo-simulation.md).
|
||||
|
||||
**EasyWMS Gateway**
|
||||
Windows service (`EasyWMSGateway2015`) that brokers all communication between EasyWMS and the automation layer (GALILEO in production, EasyS in simulation). Installed at `C:\Program Files\Mecalux\EasyWMS Gateway 2015`; config at `C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Config\MainObject.config` (tenantCode + TokenUser); logs at `C:\ProgramData\Mecalux\EasyWMS Gateway 2015\Logs\AllLog.log`; uses TCP port 3000. See [Galileo Integration](architecture/galileo-integration.md).
|
||||
|
||||
**End (GALILEO message)**
|
||||
GALILEO-to-WMS message that signals a movement has completed. Carries an `EndErrorCode` (0 = OK, 1 = deposit error, 2 = extraction error, 4 = inconsistent order — config mismatch, 7 = gauge error). Processed by `Galileo_EndCreatedEventHandler_PR`. See [Galileo Integration — End](architecture/galileo-integration.md#3-end-log--end0-end1-).
|
||||
|
||||
**EndErrorCode**
|
||||
Numeric code attached to a GALILEO End message. Value `4` is the most common diagnostic — indicates a configuration drift between EasyWMS and GALILEO (missing location, wrong allowed container type, X/Y out of range, impossible crossing). See [Galileo Troubleshooting — §3.1](operations/galileo-troubleshooting.md#31-enderrorcode--4-most-frequent).
|
||||
|
||||
**Empileur (EMP / APL)**
|
||||
Pallet stacker station (code 13). See [Stations](concepts/stations.md) and [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
**EMS (Sistema electrovía aérea)**
|
||||
Overhead Electric Monorail — suspended pallet transport system. See [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
**ECB (Empty Container Buffer)**
|
||||
Station type 55 — buffer specifically for empty containers waiting to be stacked or reused. See [Stations](concepts/stations.md).
|
||||
|
||||
**Event (GALILEO message)**
|
||||
GALILEO-to-WMS message declaring container presence at a checkpoint. Primary source is the PIE (barcode + gauge + weight). Content varies by station; flags `65536`=OK, `256`=barcode error, `512`=recovered, `1024`/`66560`=empty OK, `4`=overheight. Processed by `Galileo_PIEEventHandler_PR`. See [Galileo Integration — Event](architecture/galileo-integration.md#1-event-log--event).
|
||||
|
||||
**ETQ (Étiqueteuse)**
|
||||
Labeller station type 58 — an automatic labelling machine through which a container passes to receive a printed label. See [Stations](concepts/stations.md).
|
||||
|
||||
**eCommerce module**
|
||||
EasyWMS add-on module for e-commerce fulfillment. JIT reception flow: single-unit orders go to packing, multi-unit to ungrouping, no-order stock to storage. See [eCommerce](modules/ecommerce.md).
|
||||
|
||||
**Entity (AD)**
|
||||
An AD element type representing a core data object. Has CRUD operations via the API (`GET/POST/PUT/DELETE /api/entities/{entityName}`). Examples: Container, Location, Item, ShippingOrder, ReceiptOrder. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**Equipment**
|
||||
In EasyWMS, an equipment is a physical device (forklift, hand truck, conveyor segment, AGV, Pallet Shuttle cart) managed by the system. Equipment has a type, work zone permissions, container type compatibility, and optional PTL controller. See [Warehouse Designer](concepts/warehouse-designer.md).
|
||||
|
||||
**ERP Interface**
|
||||
The set of standardized messages exchanged between EasyWMS and the customer's ERP system (SAP, Oracle, etc.). Three-letter codes identify each message type (ROR, SOR, ASN, ROF, SOF, etc.). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**ET station (Estación de Tránsito — Transit)**
|
||||
Station type used as an intermediate buffer between two zones that cannot directly route to each other. A conveyor element in EasyS; appears in the "Automatic elements" group. Required for multi-zone replenishment flows. See [Stations](concepts/stations.md).
|
||||
|
||||
**Event (AD)**
|
||||
An AD element type representing a state-transition trigger. Fired when a transaction occurs; can trigger ERP messages (STV, ROF, SOF), SCEM notifications, or start Workflows. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**EnterAction / EscapeAction (ProcessContext)**
|
||||
Workflow variables used to detect a user pressing `Entrée` or `Échap` after a dialog. Code review enforces their use instead of hard-coded "Enter"/"Escape" string constants. See [Code Review Process](operations/code-review-process.md).
|
||||
|
||||
---
|
||||
|
||||
## F
|
||||
|
||||
**Flux tendu**
|
||||
See **Tense flow**. French term for the warehouse mode where inbound stock is immediately routed to active outbound orders. Configured in EasyS on the target zone; reception kicks off virtual picking on the tense-flow orders. See [Tense Flow](concepts/tense-flow.md).
|
||||
|
||||
**FEFO (First Expired, First Out)**
|
||||
Shipping logic where stock with the earliest expiry date is picked first. Configured as a location storage logic and/or shipping order requirement. See [Location](concepts/location.md).
|
||||
|
||||
**FIFO (First In, First Out)**
|
||||
Shipping/storage logic where the oldest stock (by receipt date) is consumed first. Used in location configuration and compact channel settings. See [Location](concepts/location.md).
|
||||
|
||||
**Fleet Manager**
|
||||
Controller software/hardware that coordinates APS3D shuttle movements, lifts, and conveyors. Communicates with EasyWMS via the Fleet Manager protocol. See [APS3D](modules/aps3d.md) and [Stations](concepts/stations.md).
|
||||
|
||||
**Fusion (order fusion) — synonym Merge**
|
||||
Grouping of two or more shipping orders into a single picking wave for joint preparation. Orders in a fusion share picking tasks. See [Shipping](concepts/shipping.md).
|
||||
|
||||
---
|
||||
|
||||
## G
|
||||
|
||||
**Gateway AGV**
|
||||
Windows service provided by Mecalux that bridges Easy WMS workflows and the PostgreSQL exchange tables used by the AGV module. Serializes AGV tasks into `agv_outputqueue` / `agv_eag`, reads fleet manager responses from `agv_inputqueue` / `agv_age` / `agv_ags`. Polls at configurable intervals (default 1 second). Creates all PostgreSQL tables and sequences on first startup. Config file: `C:\ProgramData\Mecalux\EasyWMS GatewayAGV 2015\`. See [AGV](modules/agv.md) and [AGV Installation Guide](operations/agv-installation.md).
|
||||
|
||||
**Galileo**
|
||||
Mecalux's production **Transport Management System (TMS)** — the automation layer that drives conveyors, stacker cranes (TK/Miniload), shuttles, AGVs and lifts. Has **no predictive vision**; only requests orders from EasyWMS and executes them. Also used inside EasyS as the label of the conveyor route type (opposed to Manual / Virtual) — a "Galileo" route is a physical hop that requires Gateway communication. See [Galileo Integration](architecture/galileo-integration.md) and [Stations](concepts/stations.md).
|
||||
|
||||
**Galileo_PIEEventHandler_PR / Galileo_SearchCreatedEventHandler_PR / Galileo_EndCreatedEventHandler_PR**
|
||||
The three core workflows consuming GALILEO messages: PIE events (inbound identification), Search requests (next-hop routing — can fire dozens per second, do not activate instance tracing carelessly), and End notifications (movement complete / error). See [Galileo Integration — AD entry points](architecture/galileo-integration.md#application-dictionary-entry-points).
|
||||
|
||||
**GalileoMovTrackingCreateCommand**
|
||||
Preferred AD command for pushing a movement order to GALILEO (over the deprecated `GalileoMovTrackingCreateChangingTargetCommand`). Transition: movement `Generated` → `In progress`, container placed on virtual location **Mov**. See [Galileo Integration](architecture/galileo-integration.md).
|
||||
|
||||
**Gerbabilité (Stackability)**
|
||||
Numeric attribute (0–10) on an item's logistic profile expressing how many containers of that item can be stacked on top of each other. Transmitted via `ITM01` field `<Stack>`. `0` = not stackable; `10` = maximum stacking. Checked by putaway strategies and channel storage logic. See [Product / Item](concepts/product-item.md).
|
||||
|
||||
**GNAImportError (Notification_GNAImportError)**
|
||||
SCEM notification event triggered when an ERP message fails to import (parse error or missing data). Critical event to subscribe to for all deployments. See [Supply Chain Event Management](modules/supply-chain-event.md).
|
||||
|
||||
**GS1-128**
|
||||
Barcode format based on Code 128, augmented with Application Identifiers (AI). Standard format for EasyWMS LPN labels (SSCC) and item labels. See [Labels](concepts/labels.md).
|
||||
|
||||
**GTIN (Global Trade Item Number)**
|
||||
GS1 identifier for a product at a specific packaging level (item, case, pallet). Encoded in AI(02) in GS1-128 barcodes. See [Labels](concepts/labels.md).
|
||||
|
||||
---
|
||||
|
||||
## H
|
||||
|
||||
**HPKS-R**
|
||||
Mecalux cobot integration protocol. The Cobot module connects robotic picking arms to EasyWMS via the HPKS-R interface. See [Cobot](modules/cobot.md).
|
||||
|
||||
**Hypercare**
|
||||
Period immediately after MEP (go-live) during which the dev team handles bug fixes on the `develop` branch. Ends when the project is transferred to the Support team (TLM). See [Git Branch Lifecycle](operations/git-branch-lifecycle.md).
|
||||
|
||||
**IdentError / IdentErrorType**
|
||||
Enum of rejection reason codes (PIE barcode unreadable, overheight, overhang, overweight, no ASN match…). Different IdentErrors can route containers to different reject destinations using **reject routes** (displayed in red in EasyS). Reference: [IdentErrorType doc](https://msscc.mecalux.com/documentation/Development/master/ES/apis/easywms/Domain/IdentErrorType.md). See [Galileo Simulation — §3.11](operations/galileo-simulation.md#311-reject-configuration).
|
||||
|
||||
**IMS (Sistema electrovía invertida)**
|
||||
Inverted Electric Monorail — floor-based inverted monorail variant of EMS. See [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
---
|
||||
|
||||
## I
|
||||
|
||||
**IIS (Internet Information Services)**
|
||||
Microsoft web server hosting EasyWMS. Requires three application pools: Main (web UI + API), Background Jobs (scheduled tasks), Integration (ERP message processing). See [System Architecture](architecture/overview.md).
|
||||
|
||||
**INO.* transactions**
|
||||
Transaction prefix for receipt order lifecycle: `INO.CREATE` (order created), `INO.OPEN` (order opened), `INO.CLS` (order closed). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**IS crossdocking (Is crossdocking strategy)**
|
||||
A putaway strategy variant. When this flag is active, the strategy routes stock to dedicated crossdocking locations rather than standard storage. See [Crossdocking](concepts/crossdocking.md).
|
||||
|
||||
**ITM (Item Master)**
|
||||
Inbound ERP message. Creates or updates item master data in EasyWMS. Also `ITC` for item catalog. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
---
|
||||
|
||||
## K
|
||||
|
||||
**KIT / Kit assembly**
|
||||
Process of assembling finished kits from component items. Managed via the Kits module. ERP message `KIT` sends kit structure. Task type: Kit assembly. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**KPI (Key Performance Indicator)**
|
||||
Performance metrics tracked in the Data Analytics module or displayed on the 3PL Client Portal. Examples: lines picked per hour, receiving accuracy, order cycle time. See [Data Analytics](modules/data-analytics.md) and [3PL Portal](modules/3pl-portal.md).
|
||||
|
||||
---
|
||||
|
||||
## L
|
||||
|
||||
**Location cart (chariot à emplacement)**
|
||||
Mobile cart divided into numbered **divisions**, used at the RFT for wave and group picking so a single operator prepares multiple orders in one pass without mixing stock. Requires specific SmartUI configuration (cart type, division count, assignment to work area). See [Picking](concepts/picking.md#location-carts-chariots-à-emplacement).
|
||||
|
||||
**LogisticAttributeCreateLogisticCaptureCommand**
|
||||
Run Command that adds a **capture mode** to an existing logistic attribute. Used with `CaptureMode = 2` and `CaptureProcess = 2` to create an attribute with **no capture mode** — that is, one auto-generated by custom code rather than prompted on the RFT/SmartUI. See [Product / Item](concepts/product-item.md#creating-a-logistic-attribute-without-a-capture-mode).
|
||||
|
||||
**LneTrmAlternative**
|
||||
Sub-field of `<LneTerms>` in `SOR(01|02)`. Boolean flag enabling the **substitute item** feature at line level. When `true`, the WMS may ship the configured substitute items (see shipping profile mode: Partiel / Substitution / Tout ou rien) if the primary item has insufficient stock. Returned in `SOF` alongside `LneDIsAlternative` to flag the actual substitute used. See [Product / Item](concepts/product-item.md#alternative--substitute-items) and [Order Outbound](concepts/order-outbound.md#alternative-items-sor-flag--sof-feedback).
|
||||
|
||||
**LneDIsAlternative**
|
||||
Field in the `SOF` shipping-order feedback, at line level. `true` if the shipped stock is a substitute of the originally-requested item. Paired with the substitute item code. See [Product / Item](concepts/product-item.md#alternative--substitute-items).
|
||||
|
||||
**L&F (Lost & Found)**
|
||||
Virtual location used to park containers with unknown or unresolvable physical location. Stock in L&F is visible but excluded from normal operations until reconciled. Transaction: `CON.SEND.L&F`. See [Container](concepts/container.md).
|
||||
|
||||
**Labor Management (LMS)**
|
||||
EasyWMS module that measures operator productivity by comparing actual task times to calculated target times (based on layout dimensions and equipment speed). See [Labor Management](modules/labor-management.md).
|
||||
|
||||
**LIFO (Last In, First Out)**
|
||||
Storage access mode for compact channels (Pallet Shuttle, mobile racking). The most recently inserted container is extracted first. See [Pallet Shuttle](modules/pallet-shuttle.md) and [Location](concepts/location.md).
|
||||
|
||||
**LMS**
|
||||
See **Labor Management**.
|
||||
|
||||
**Load (truck load)**
|
||||
A grouping of containers/routes assigned to a specific truck or vehicle. Created from one or more routes. Truck loading task sequence is determined by route stop numbers (reverse delivery order). See [Shipping](concepts/shipping.md).
|
||||
|
||||
**Location lock type**
|
||||
A named restriction applied to a location that blocks specific operations (putaway, picking, replenishment, count, movement). Configured in `Masters > Lock Types > Location Lock Types`. See [Location](concepts/location.md) and [Security](architecture/security.md).
|
||||
|
||||
**LOF (Load Order Fulfilled)**
|
||||
Outbound ERP message. Sent when a truck load is closed (all containers loaded). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**LPN (License Plate Number)**
|
||||
The fundamental unit of physical storage in EasyWMS. A box, pallet, or any container that holds stock. Identified by a unique code (usually SSCC). Synonymous with "container" in the WMS. The AD entity name is `Container`. See [Container](concepts/container.md).
|
||||
|
||||
---
|
||||
|
||||
## M
|
||||
|
||||
**Manual Picking (`ManualPicking_ByItem_UI`)**
|
||||
RFT flow where the operator creates the outbound order on the spot by scanning items, then picks them without a pre-existing SOR. Incompatible with 3PL billing (orders without accounts not billed) and with carrier modules (orders without carrier metadata not shippable as parcels). Menu path: *Ordres d'expédition → Picking manuel*. See [Picking](concepts/picking.md).
|
||||
|
||||
**Manual movement**
|
||||
A stock or container relocation performed without generating a task. Eight move types: location↔location, location↔container, container↔container, container+divisions, division↔division, move container, cutting stock, and partitions. See [Manual Movements](concepts/manual-movements.md).
|
||||
|
||||
**ME station (Multi-Exit)**
|
||||
Automatic warehouse station where containers exit the system onto multiple possible conveyor lanes. See [Stations](concepts/stations.md).
|
||||
|
||||
**ME / TE (Aisle Inbound Conveyor / Table d'entrée)**
|
||||
Station type 9 — the conveyor at the entry of a TK/Miniload. Can hold multiple containers (layout uses Positions + Stack); configure `Logical X = 991` except for tables embedded in the rack. FR: TE, ES: ME, EN: Input Conveyor (IC). See [Stations](concepts/stations.md) and [Galileo Simulation — §3.8](operations/galileo-simulation.md#38-entry--outbound-tables-te--ts-on-the-tk).
|
||||
|
||||
**MS / TS (Outbound Conveyor / Table de sortie)**
|
||||
Station type 10 — the outbound conveyor of a TK/Miniload. Shares the Positions + Stack configuration pattern with ME/TE. FR: TS, ES: MS, EN: Output Conveyor (OC). See [Stations](concepts/stations.md).
|
||||
|
||||
**MP / TP (Preparation Zone / Table de préparation)**
|
||||
Station type 16. Preparation tables linked to a picking station (PK) where operators deposit picked stock. Routes: **Manual** PK → MP, **Galileo** MP → outbound table, **Virtual** MP → consolidation. Assignment mode (Automatic / Manual) set via **Menu → Control → Workstations**. In manual mode, tasks do not generate until the outbound order is assigned to a table. See [Picking — PK/MP setup](concepts/picking.md#pk--mp-setup-and-assignment-mode).
|
||||
|
||||
**Miniload (ML / STL / TK)**
|
||||
Light-load automated stacker crane used for bins/cases (typically ≤ 50–100 kg per load). Nomenclature: `ML` = Miniload, `B` (post-ML) = Bicolumn, `EPSF` = pelle simple fond (1 charge), `EPDF` = pelle double fond (1 charge, double-depth rack), `ECDF` = courroie double fond (2 charges). Each model drives the TE/TS table configuration in EasyS. See [Mechanical Elements — §4](concepts/mechanical-elements.md#4-miniload-nomenclature-tk--ml).
|
||||
|
||||
**Mov (virtual location)**
|
||||
System virtual location that temporarily holds a container while it is physically travelling between two stations. Set on movement transition `Generated` → `In progress`; cleared on End with `EndErrorCode=0`. See [Galileo Integration — Task lifecycle](architecture/galileo-integration.md#tasks-vs-movements).
|
||||
|
||||
**Manual Action (EasyS)**
|
||||
Test-mode checkbox on a picking station in EasyS. When ticked, the container **does not leave automatically** after picking confirmation — the operator must click **Liberate** to release it. Essential for stepping through flows during simulation. See [Galileo Simulation — §7](operations/galileo-simulation.md#7-extract-a-container-from-the-miniload).
|
||||
|
||||
**MT / MTB (Transelevador de paletas)**
|
||||
Monocolumn (MT) and Bicolumn (MTB) pallet stacker cranes. Heavy-duty variants of the miniload used for Euro-pallets. See [Mechanical Elements](concepts/mechanical-elements.md).
|
||||
|
||||
**MECALUX**
|
||||
Spanish manufacturer and developer of EasyWMS and EasyS. Headquarters in Barcelona. Also manufactures automated warehouse equipment (racks, Pallet Shuttle carts, moviracks).
|
||||
|
||||
**MEP (Mise En Production)**
|
||||
Go-live event for a project. Pivot moment of [Git Branch Lifecycle](operations/git-branch-lifecycle.md): before MEP the CdP merges `develop`→`master` and deletes `develop`; Hypercare follows on a freshly-recreated `develop`.
|
||||
|
||||
**MSSCODE**
|
||||
Internal Mecalux Gitea instance hosting all project repositories. Authentication via SSH key (ed25519) — see [SSH Keys Setup](operations/ssh-keys-setup.md). Cloning via SSH (not HTTPS) is mandatory once the SSH key is configured in Sourcetree.
|
||||
|
||||
**MOR01 (Manufacturing Order)**
|
||||
Inbound ERP message for manufacturing production orders. Triggers stock consumption of components and creation of finished goods. See [Manufacturing](modules/manufacturing.md).
|
||||
|
||||
**Montage sur demande**
|
||||
Kit configuration flag (French: "on-demand assembly"). When `YES`, the WMS auto-creates an assembly work order at the integration of an outbound order containing a kit shortage. When `NO`, kit fabrication is only triggered by a manual or ERP-originated WOR — the WMS emits no automatic alert. See [Kits](concepts/kits.md#kit-shortage-handling).
|
||||
|
||||
**Movirack**
|
||||
Mecalux mobile racking system where rack bays slide laterally to open aisles on demand. Five work modes: Manual, Auto, Timing, Autoparking, Autopicking. See [Movirack](modules/movirack.md).
|
||||
|
||||
**MP station**
|
||||
Container or equipment used in grouped/automatic picking. Has extra locations (slots) where individual stock units are accumulated before being directed to their destination. See [Stations](concepts/stations.md) and [Picking](concepts/picking.md).
|
||||
|
||||
**MS station (Multi-Stock)**
|
||||
Automatic warehouse station type for multi-reference stock movements. See [Stations](concepts/stations.md).
|
||||
|
||||
**MU station (Multi-Unit)**
|
||||
Automatic warehouse station type handling multiple simultaneous container flows. See [Stations](concepts/stations.md).
|
||||
|
||||
**Multi-Carrier Shipping module**
|
||||
EasyWMS add-on for carrier integration. Manages deliveries (carrier + consignee), packing at packaging stations, tracking numbers, carrier labels, and carrier selection rules. See [Multi-Carrier](modules/multi-carrier.md).
|
||||
|
||||
---
|
||||
|
||||
## N
|
||||
|
||||
**NEUT / ROUJE pattern (Split reception)**
|
||||
Mecalux France reception split convention. Incoming stock is split between two complementary buffers at reception to enforce picking-vs-reserve separation : `NEUT` (neutral / picking-ready) and `ROUJE` (customs-held / reserve). Combines with four putaway strategies (direct-to-picking, picking + reserve, reserve only, customs-hold). See [Reception](concepts/reception.md#reception-split-strategy).
|
||||
|
||||
**Negative picking**
|
||||
Automatic warehouse picking mode where an empty container is sent to a storage channel; the AS/RS picks the desired stock from the channel into the empty container. Used in LIFO channels. See [Picking](concepts/picking.md).
|
||||
|
||||
**NegativeStock user status**
|
||||
Special stock status used in the Manufacturing module to represent component stock consumed in production before the finished good is confirmed. See [Manufacturing](modules/manufacturing.md).
|
||||
|
||||
**Notification event**
|
||||
A named event in the SCEM module that users can subscribe to. Associated with a severity (Info/Warning/Error) and a notification group. Examples: AGV errors (group: AGV), stock failure (group: WMS), ERP import error (group: GNA). See [Transactions](concepts/transactions.md) and [Supply Chain Event Management](modules/supply-chain-event.md).
|
||||
|
||||
**NAT (Network Address Translation)**
|
||||
Routing layer set up between the Hyper-V host PC and the dev VM (commutateur InternoNAT). Maps external host ports (8080, 4430, 33890, 15210, 4450) to internal VM ports (80, 443, 3389, 1521, 445) so applicative ports remain free on the host. See [VM Network Routing](operations/vm-network-routing.md).
|
||||
|
||||
---
|
||||
|
||||
## O
|
||||
|
||||
**Order orchestration (DOM)**
|
||||
The 5-stage engine in the DOM module that assigns sales orders to the optimal fulfillment node: (1) Geographic region, (2) Carrier availability, (3) Stock availability, (4) Node capacity, (5) Business strategies. See [DOM](modules/dom.md).
|
||||
|
||||
**OUT.* transactions**
|
||||
Transaction prefix for shipping order lifecycle: `OUT.CREATE` (order created), `OUT.OPEN` (order released), `OUT.PICK` (picking started), `OUT.PREP` (preparation completed), `OUT.SHIP` (shipped). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**Owner**
|
||||
In 3PL contexts, an entity that owns the inventory stored in the warehouse (a client of the 3PL). Owner extensions enforce data isolation across all master data and orders. See [Account / Owner](concepts/account-owner.md) and [Owner Extensions](modules/owner-extensions.md).
|
||||
|
||||
**OutboundLines vs OutboundOrderLines**
|
||||
Two distinct properties on writing-side queries against shipping orders. Use `OutboundLines` to avoid the "Le nombre de ligne d'ordre d'expédition ne peut pas être négatif" error when a line is cancelled. With kits without assembly: `OutboundLines` returns only the kit; `OutboundOrderOutboundOrderLineDetails` returns all components. See [Code Review Process](operations/code-review-process.md).
|
||||
|
||||
---
|
||||
|
||||
## P
|
||||
|
||||
**Prepackaging (Préemballage / Précolisage)**
|
||||
Configuration that drives **how** pickers group picked stock into client containers during shipping preparation. The strategy is set at the shipping order type level; the ERP can also supply the package count and type via `SOR02` `<PrpPackagingConfiguration>`. Distinguishes from VAS (which acts after picking). See [Prepackaging](concepts/prepackaging.md).
|
||||
|
||||
**Parameter**
|
||||
A named configuration value that controls a specific WMS behavior. Stored in the AD. Organized at organization level (global) or warehouse level (per-facility). See [Parameters](concepts/parameters.md).
|
||||
|
||||
**Partition (PDL partition)**
|
||||
A sub-division of a picking dedicated location assigned to a specific item and logistic attributes. Used for fine-grained allocation of shared shelf space (drawers, boxes). See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**Partition (count)**
|
||||
A sub-division of a location for the purpose of counting. Items are assigned to specific physical positions within a location. See [Count](concepts/count.md).
|
||||
|
||||
**PDL (Picking Dedicated Location)**
|
||||
A warehouse location (or partition of a location) permanently assigned to a specific item (and optionally logistic attributes) for first-level picking. PDLs have min/max stock levels and trigger replenishment automatically. See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**Pick and Pack**
|
||||
Picking mode where the operator picks directly into the final shipping box, eliminating a separate packing step. See [Picking](concepts/picking.md).
|
||||
|
||||
**Pick and Pass**
|
||||
Picking mode where multiple operators each pick one zone; the client container passes from operator to operator along a conveyor or route until all lines are complete. See [Picking](concepts/picking.md).
|
||||
|
||||
**PIE station (Punto de Introducción de Entrada — Automatic Inbound Point)**
|
||||
The entry point of an automated warehouse. Validates dimensions, weight, and identity of incoming containers. Routes valid containers inward; rejects non-conforming containers to a rejection station. On the GALILEO side, the PIE is seen as a standalone station whose events trigger the `Galileo_PIEEventHandler_PR` workflow on EasyWMS. See [Stations](concepts/stations.md), [GALILEO Integration](architecture/galileo-integration.md) and [Reception](concepts/reception.md).
|
||||
|
||||
**PK conveyor / PK station (Picking conveyor)**
|
||||
A picking workstation on the conveyor system. Operators work at a PC; containers arrive on the conveyor and are processed (picked, received, consolidated, counted) before continuing on the conveyor. PK station capacity is given per-route (unlike miniload TKs which give capacity per-station). See [Stations](concepts/stations.md) and [GALILEO Integration](architecture/galileo-integration.md).
|
||||
|
||||
**PKE station (Punto de Extracción de Salida — Picking Extraction Point)**
|
||||
Extraction point *from* a picking workstation, used on a "full" PK→PKE route for robotics simulation tests. Pairs with an ME (Manual Entry) target. See [Galileo Simulation](operations/galileo-simulation.md) and [Robotics Project Lifecycle](operations/robotics-project-lifecycle.md).
|
||||
|
||||
**PLC (Programmable Logic Controller)**
|
||||
Hardware controller for automated warehouse machinery (conveyors, lifts, sorters). EasyWMS communicates with PLCs for AS/RS coordination.
|
||||
|
||||
**PLC Container Type / PLC Height Type**
|
||||
Two fields configured in EasyS under **PLC Types** that translate WMS container codes and heights into the numeric identifiers the PLC/controller expects. On miniload installations the two types are usually **tied** (container type implies height). Required before GALILEO can route containers. See [Galileo Simulation](operations/galileo-simulation.md).
|
||||
|
||||
**Port 3000**
|
||||
TCP port used by the **EasyWMS Gateway** to listen for GALILEO / EasyS connections. Must be opened in the Windows firewall (e.g. `New-NetFirewallRule -DisplayName "EasyWMS Gateway 3000" -LocalPort 3000 -Protocol TCP -Action Allow`). See [Galileo Simulation](operations/galileo-simulation.md).
|
||||
|
||||
**Post-processing (ERP message)**
|
||||
The mechanism by which EasyWMS transactions trigger outbound ERP messages. A transaction (e.g., `REC.CLS`) is marked as "post-processed" when the associated ERP message (e.g., `ROF`) has been queued for sending. See [ERP Interface](concepts/erp-interface.md) and [Transactions](concepts/transactions.md).
|
||||
|
||||
**POS (Point of Sale)**
|
||||
Terminal at a retail store. In the Store Fulfillment module, POS systems at remote stores send outbound orders to the central warehouse. See [Store Fulfillment](modules/store-fulfillment.md).
|
||||
|
||||
**PS (Pallet Shuttle)**
|
||||
A motorized cart that operates inside compact rack channels (deep-lane), depositing and extracting pallets autonomously. Controlled by the PSService background job via WIFI. See [Pallet Shuttle](modules/pallet-shuttle.md).
|
||||
|
||||
**PSService**
|
||||
Background job that centralizes communication between EasyWMS and all Pallet Shuttle carts via WIFI/tablet. Manages deposit/extraction/compaction commands and battery status. See [Pallet Shuttle](modules/pallet-shuttle.md).
|
||||
|
||||
**PTL (Pick To Light / Put To Light)**
|
||||
Illuminated display devices mounted at picking locations. Guide operators during batch picking: devices light up in assigned colors showing quantity to pick (Pick To Light) or quantity to drop at equipment slot (Put To Light). Requires PTL Service and PTL controller per device group. See [Picking](concepts/picking.md) and [Configuration Guide](operations/configuration-guide.md).
|
||||
|
||||
**Put To Light**
|
||||
See **PTL**. Variant of PTL picking where devices are mounted on both shelves and equipment. See [Configuration Guide](operations/configuration-guide.md).
|
||||
|
||||
**ProductConversion (OutboundLine)**
|
||||
Optional attribute of a shipping order line — can be `null` when the order specifies a container code but no item (e.g. a request for a specific support without product). Code review enforces a null-check. See [Code Review Process](operations/code-review-process.md).
|
||||
|
||||
---
|
||||
|
||||
## Q
|
||||
|
||||
**Poids balance / Poids calculé / Poids réel / Poids théorique (article) / Poids théorique (balance)**
|
||||
The five container-level weight fields tracked by the WMS. *"Poids théorique"* is ambiguous in French — always disambiguate between **article** (from item master) and **balance** (from scale minus adjustments). See [Weights](concepts/weights.md).
|
||||
|
||||
**Quality lock**
|
||||
A stock status applied to specific stock to block one or more operations (picking, replenishment, shipping, counting). Two subtypes: **receiving status** (applied at reception) and **user status** (applied manually or via ERP). See [Quality Control](concepts/quality-control.md).
|
||||
|
||||
**QueryExecute API**
|
||||
One of three EasyWMS API families. Executes LINQ-based queries against Views or Entities: `POST /api/queries/execute`. Supports filtering, sorting, and pagination. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
---
|
||||
|
||||
## R
|
||||
|
||||
**RCP01 / RCP02 (Recipe types)**
|
||||
Manufacturing module recipe types: `RCP01` = standard manufacturing recipe (components → finished good); `RCP02` = quartering recipe (split one item into portions). See [Manufacturing](modules/manufacturing.md).
|
||||
|
||||
**REAC station (Reactivation)**
|
||||
Pallet Shuttle charging station variant — reactivates/charges a PS cart. See [Stations](concepts/stations.md).
|
||||
|
||||
**Receipt**
|
||||
A WMS document that records the physical receipt of stock (containers and/or loose stock) within a reception session. Multiple receipts can be created against the same receipt order. Receipt is distinct from receipt order. See [Reception](concepts/reception.md).
|
||||
|
||||
**Receipt order**
|
||||
See **Inbound Order**.
|
||||
|
||||
**RECH station (Recharge)**
|
||||
Pallet Shuttle charging station. PS carts are deposited here to charge their battery. See [Stations](concepts/stations.md).
|
||||
|
||||
**Reject route / MP-reject**
|
||||
A physical route configured in EasyS that ends on a **Manual Exit (TM / MT)** serving as the warehouse's "reject bin" for PIE-level refusals. Used to extract unknown / unmeasured / weight-rejected containers. See [Galileo Simulation](operations/galileo-simulation.md).
|
||||
|
||||
**Responsable de projet (Robotics)**
|
||||
Senior project manager at Mecalux who arbitrates scope and priorities across the chef de chantier, chef de projet IT and responsable électricité during a robotics installation. See [Robotics Project Lifecycle](operations/robotics-project-lifecycle.md).
|
||||
|
||||
**Route (GALILEO)**
|
||||
A physical path between two stations in the TMS (GALILEO / EasyS). Distinct from a WMS logical route: on EasyWMS side, a station is linked to a route via `StationRoutes`. The station + route pair drives capacity semantics: PK/PS routes carry capacity; miniload TK stations carry capacity. See [Stations](concepts/stations.md), [GALILEO Integration](architecture/galileo-integration.md) and [Galileo Simulation](operations/galileo-simulation.md).
|
||||
|
||||
**REF (Receipt Error Feedback)**
|
||||
Outbound ERP message. Sent when a reception error occurs (e.g., ASN quantity mismatch, unknown container). Informs ERP of the discrepancy. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Relocation percentage**
|
||||
A putaway strategy configuration value. When an aisle's occupancy exceeds this percentage, the putaway engine stops assigning new containers to that aisle (for that strategy). See [Putaway](concepts/putaway.md).
|
||||
|
||||
**Reten (Manuel de retention)**
|
||||
Project handover/retention manual maintained as Markdown in the project Git repository (`docs/`). Documents every custom modification: process changes go in process chapters (Entries, Exits, Picking…), other custom elements go in end-of-reten tables, custom attributes go in section "1.2 General custom elements". Mandatory deliverable, validated by documentation review. See [Code Review Process](operations/code-review-process.md) and [Development Methodology](operations/development-methodology.md).
|
||||
|
||||
**RFT (Radio Frequency Terminal)**
|
||||
Handheld or vehicle-mounted barcode scanning terminal used by warehouse operators for guided tasks (receiving, picking, putaway, counting). Runs EasyWMS RF application via WIFI.
|
||||
|
||||
**ROC (Receipt Order Confirmation)**
|
||||
Outbound ERP message. Sent when a receipt order changes status (opened, partially received, closed). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Real Weight (Poids réel)**
|
||||
Container weight field computed as `max(Calculated Weight, Theoretical Scale Weight)`. Acts as the "best known" weight — theoretical when no PIE pass has occurred, scale-derived once it has. Reported on shipping documents. See [Weights](concepts/weights.md).
|
||||
|
||||
**ROF (Receipt Order Fulfilled)**
|
||||
Outbound ERP message. Sent when a receipt order is fully fulfilled (all lines received). Two variants: `ROF01` (standard) and `ROF02` (extended line-level detail — used when the inbound order was generated from a `Transfer` shipping order in the two-warehouse flow, and for returns). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Routine (replenishment)**
|
||||
French SmartUI label for the **Stockout / threshold-based** replenishment strategy — triggers when the picking location drops below its configured minimum. See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**ROR (Receipt Order Request)**
|
||||
Inbound ERP message. Creates a receipt order in EasyWMS. Multiple variants for supplier receipts, ASN pre-notifications, returns, and transfers. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**ROU.* / LOAD.* transactions**
|
||||
Transaction prefix for route and load lifecycle events: `ROU.CREATE`, `ROU.CLS`, `LOAD.CREATE`, `LOAD.CLS`. See [Transactions](concepts/transactions.md).
|
||||
|
||||
**RUT (Route Update)**
|
||||
Inbound ERP message. Creates or updates a shipping route in EasyWMS. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
---
|
||||
|
||||
## S
|
||||
|
||||
**SAC (Stock Analysis Classification)**
|
||||
Outbound ERP message (`SAC01`) sent manually from SmartUI after running the ABC rotation analysis. Carries item code + suggested ABC class. The ERP uses it to update item classification. Not automatic — the WMS operator must explicitly trigger it. See [ERP Interface](concepts/erp-interface.md#module-specific-erp-messages).
|
||||
|
||||
**SaaS (Software as a Service)**
|
||||
Cloud-hosted deployment of EasyWMS on Amazon infrastructure. Includes VPN requirements, SaaS-specific API endpoints, and Amazon SaaS certification for mobile apps (Android 10 requirement for Marketplaces). See [System Architecture](architecture/overview.md).
|
||||
|
||||
**SCADA (Supervisory Control And Data Acquisition)**
|
||||
Supervision UI layer of the automation installation. In Mecalux robotics, SCADA is distinct from both GALILEO (TMS logic) and EasyWMS (business logic) — it shows the physical machine state to operators and maintenance teams. See [GALILEO Integration](architecture/galileo-integration.md).
|
||||
|
||||
**SCEM (Supply Chain Event Management)**
|
||||
EasyWMS module for real-time event notification. Users subscribe to notification events and receive alerts via web, email, or SMS. See [Supply Chain Event Management](modules/supply-chain-event.md).
|
||||
|
||||
**Search (GALILEO message)**
|
||||
One of the three GALILEO-initiated message types (the others: **Event** and **End**). A **Search** asks EasyWMS where a specific container should go next (routing decision). Handled by `Galileo_SearchCreatedEventHandler_PR`. The response carries a target station and, optionally, a container update. See [GALILEO Integration](architecture/galileo-integration.md).
|
||||
|
||||
**SCR (Stock Contrast Request)**
|
||||
Inbound ERP message. Requests a stock comparison between ERP and WMS for specified items/locations. WMS responds with `WSC`. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Shipping order**
|
||||
See **Outbound Order**.
|
||||
|
||||
**SKU (Stock Keeping Unit)**
|
||||
A unique identifier for an item at a specific packaging level. In EasyWMS, the item code is the primary SKU; aliases can provide additional codes for scanning and ERP integration.
|
||||
|
||||
**Slotting module**
|
||||
EasyWMS add-on that analyzes item rotation data and recommends optimal picking location assignments. Uses a profit formula to calculate the value of moving each item. See [Slotting](modules/slotting.md).
|
||||
|
||||
**SGA (Sistema de Gestión de Almacenes)**
|
||||
Spanish acronym for WMS. Used interchangeably with WMS in Mecalux Spain-originated documentation.
|
||||
|
||||
**SmartUI**
|
||||
EasyWMS's web-based user interface (browser). Used by supervisors and managers for administration, monitoring, and configuration. Distinct from RFT (handheld terminal) screens. See [System Architecture](architecture/overview.md).
|
||||
|
||||
**Station update / Route update (GALILEO)**
|
||||
Two status streams GALILEO pushes to EasyWMS roughly every 1–3 seconds. They carry real-time physical state (station busy/free, route status, movement progress) and are written in the Gateway log. Not `Event` messages — they do not trigger workflows, only update state. See [GALILEO Integration](architecture/galileo-integration.md) and [Galileo Troubleshooting](operations/galileo-troubleshooting.md).
|
||||
|
||||
**SOC (Shipping Order Confirmation)**
|
||||
Outbound ERP message. Sent when a shipping order changes status (released, prepared, in progress, completed). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**SOF (Shipping Order Fulfilled)**
|
||||
Outbound ERP message. Sent when a shipping order is fully shipped. Two variants: `SOF01` (fully fulfilled) and `SOF02` (partially fulfilled / backorder). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**SOR (Shipping Order Request)**
|
||||
Inbound ERP message. Creates a shipping order in EasyWMS. Two variants: `SOR01` (standard) and `SOR02` (with VAS instructions). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**SRK / SRN / SRO (Supplier Return messages)**
|
||||
ERP message family for supplier return flows: `SRN` (return notification inbound), `SRO` (return order confirmation outbound), `SRK` (return fulfilled outbound). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Scale Weight (Poids balance)**
|
||||
Raw gross weight of a container measured at the **PIE** (Punto de Introducción de Entrada). Updated on PIE pass only. Feeds Theoretical Scale Weight and Real Weight. See [Weights](concepts/weights.md).
|
||||
|
||||
**SSCC (Serial Shipping Container Code)**
|
||||
GS1-standard 18-digit numeric identifier for a logistics unit (LPN). The default LPN code format in EasyWMS. Encoded in GS1-128 barcode as AI(00). See [Labels](concepts/labels.md) and [Container](concepts/container.md).
|
||||
|
||||
**STK.* transactions**
|
||||
Transaction prefix for stock-level events. Key types: `STK.RECEP` (received), `STK.MOVE` (moved), `STK.ADJ` (adjusted), `STK.PICK` (picked), `STK.SHIP` (shipped), `STK.REP` (replenished), `STK.MAN.PRODUCTION` (manufacturing). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**SSCC prefix (change)**
|
||||
Changing the SSCC prefix sequence is done in **EasyS** (the configurator). Open the warehouse, **double-click the warehouse name** to expose the SSCC/numbering panel, adjust the prefix and/or sequence number, save. Has no effect on already-created containers. See [Container](concepts/container.md#changing-the-sscc-sequence-prefix).
|
||||
|
||||
**Stock assignment**
|
||||
The allocation engine that decides which concrete stock lines fulfil each outbound order line detail, and which task type (picking, shipping, replenishment, virtual picking) will be created. Built around the `StockAssignProcess_*` workflows. See [Stock Assignment](concepts/stock-assignment.md).
|
||||
|
||||
**StockAssignProcess_\* workflows**
|
||||
Family of workflows making up the stock assignment engine: `AssignOutboundLine_PR`, `AssignOutboundOrderLineDetails_PR`, `GetLockAndUpdateDetail_PR`, `GetAvailableStockForOutboundOrderLineDetails_PR`, `CalculateByAssignmentManufacturingAndKits_PR`, `CalculateEfficiencyMode_PR`, `ValidateStockList_PR`, `CreateAssignments_PR`, `GetStockToAssignForStrategy_PR`. The standard extension hooks (query filters, custom strategies) live here. See [Stock Assignment](concepts/stock-assignment.md).
|
||||
|
||||
**STC (Stock Change)**
|
||||
Outbound ERP message. Sent when a stock quality status changes (lock applied or removed). Transaction: `CST.STK`. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**STR (Stock Status Request)**
|
||||
Inbound ERP message. ERP requests the WMS to apply or remove a quality lock on stock. Response: STC (at reception close) or immediate STC (for closed receptions). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**STV (Stock Variation)**
|
||||
Outbound ERP message. Sent when stock quantity changes (adjustment, replenishment, picking, shipping). The primary stock synchronization message. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Substitute item**
|
||||
Alternative item that may replace the primary item on an outbound order line when stock is insufficient. Configured on the primary item's master ("Articles de remplacement" table). Enabled per line via `<LneTerms><LneTrmAlternative>true</LneTrmAlternative>`. The shipping profile defines the behaviour (Partiel / Substitution / Tout ou rien). SOF feedback uses `LneDIsAlternative`. See [Product / Item](concepts/product-item.md#alternative--substitute-items).
|
||||
|
||||
**Sub-warehouse**
|
||||
A logical partition of a warehouse with independent stock management rules. Items can have a "sub-warehouse classification" that controls which sub-warehouse they are stored in. Replenishment between sub-warehouses is a distinct strategy type. See [Product / Item](concepts/product-item.md) and [Replenishment](concepts/replenishment.md).
|
||||
|
||||
---
|
||||
|
||||
## T
|
||||
|
||||
**Theoretical Scale Weight (Poids théorique balance)**
|
||||
Container weight field computed as *Scale Weight − adjustments*. Initialised after the first PIE pass, then adjusted by subsequent stock moves. Input to Real Weight. See [Weights](concepts/weights.md).
|
||||
|
||||
**Theoretical Weight (Poids théorique article)**
|
||||
Container weight field computed as *item-master unit weight × quantity + container tare*. Set at creation and on every adjustment. Note : the container tare is **frozen at creation** — changing the pallet-type weight in EasyS does not propagate. See [Weights](concepts/weights.md).
|
||||
|
||||
**Transit buffer (intermediate buffer)**
|
||||
EasyS element of type **Transport** whose sub-location is a **Buffer** (not Automatic) used to bridge two sub-warehouses served by different equipment groups. Pattern: reserve-equipment drops on the buffer, picking-equipment picks up. Critical detail: the sub-location is created as `Automatic` by default and must be manually changed to `Buffer`. See [Location](concepts/location.md#transit-buffer-between-sub-warehouses) and [Replenishment](concepts/replenishment.md#inter-sub-warehouse-replenishment-via-intermediate-buffer).
|
||||
|
||||
**Transfer (SorType)**
|
||||
Shipping order type for inter-warehouse transfers with a **reciprocal inbound order** at the destination. Unlike `DirectTransfer` (which only raises an ASN via ASO), `Transfer` creates a full ROR at destination carrying the source SOR reference ; the destination ROF02 (on close) reconciles the source. See [Order Outbound](concepts/order-outbound.md#transfer-two-warehouse-flow) and [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Task**
|
||||
The atomic unit of work in EasyWMS. A task represents a single movement (container or stock from location A to location B). Tasks belong to a process (putaway, picking, replenishment, count, etc.) and follow a lifecycle: Pending → Generated → In Process → Finished/Canceled. See [Task](concepts/task.md).
|
||||
|
||||
**Tense flow (Flux tendu)**
|
||||
A warehouse configuration where all received stock is immediately directed to active outbound orders via virtual picking, without intermediate storage. Configured on the target zone in EasyS; reception triggers picking on the tense-flow orders. Distinct from opportunity crossdocking: tense flow is zone-driven, not container-driven. See [Tense Flow](concepts/tense-flow.md).
|
||||
|
||||
**Tournée (Route / RUT)**
|
||||
French term for a carrier route. Integrated from a TMS via the `RUT` inbound ERP message (route code, carrier, dock, departure time, stops). Shipping orders reference the route to consolidate truck loading. See [Shipping](concepts/shipping.md#rut-file-tms-driven-routes) and [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**TK (Transstockeur / Stacker crane)**
|
||||
Spanish/French term for a stacker crane serving a single miniload aisle. In GALILEO stations, a TK is seen as one station per miniload (capacity = number of container slots held on its forks). Opposite: a TKB is a bicolumn (double) miniload. See [Mechanical Elements](concepts/mechanical-elements.md) and [Stations](concepts/stations.md).
|
||||
|
||||
**TMS (Transport Management System — two meanings)**
|
||||
Two distinct usages in EasyWMS docs: (1) **Robotics TMS**: GALILEO (production) or EasyS (simulator), which physically drives conveyors, stacker cranes and shuttles — see [GALILEO Integration](architecture/galileo-integration.md). (2) **Carrier TMS**: external carrier-booking software, integrates via Yard Management and Multi-Carrier.
|
||||
|
||||
**Tracking (GALILEO)**
|
||||
On the GALILEO side, a "tracking" is the live movement object (container + target station + progress). EasyWMS creates a tracking via the `GalileoMovTrackingCreateCommand` when it decides where a container should go; the tracking closes when GALILEO sends back an **End** message. Distinct from a WMS **task**, which may span multiple trackings. See [GALILEO Integration](architecture/galileo-integration.md).
|
||||
|
||||
**Transaction**
|
||||
An immutable record of a state change in EasyWMS. Every WMS operation generates one or more transaction records. Transactions drive ERP messages (via post-processing). Transaction codes follow a `PREFIX.ACTION` pattern. See [Transactions](concepts/transactions.md).
|
||||
|
||||
**TSK.* transactions**
|
||||
Transaction prefix for task lifecycle: `TSK.CREATE` (task created), `TSK.ASS` (assigned), `TSK.INI` (started), `TSK.FIN` (finished), `TSK.CNL` (canceled), `TSK.COU` (count task), `TSK.ERR.EXTR` / `TSK.ERR.PUT` (automatic warehouse errors). See [Transactions](concepts/transactions.md).
|
||||
|
||||
**TryToReplenishProductLocations**
|
||||
Background job that automatically triggers replenishment for PDLs below their minimum stock level. Recommended schedule: every 5–15 minutes. See [Replenishment](concepts/replenishment.md).
|
||||
|
||||
**TLM (Tierce Maintenance)**
|
||||
Project life-cycle phase after Hypercare: ownership of the project transfers from the dev team to the **Support team**. Support refuses TLM hand-off if the Git repository still contains a `develop` branch. Support handles urgent fixes via `hotfix` branches off `master`. See [Git Branch Lifecycle](operations/git-branch-lifecycle.md).
|
||||
|
||||
**TMA (Tierce Maintenance Applicative)**
|
||||
Continuous maintenance team that delivers complementary "offers" via `release` branches (one per offer). Must merge `master` → `release` whenever Support delivers a `hotfix`, and merge `release` → `master` after delivering an offer. See [Git Branch Lifecycle](operations/git-branch-lifecycle.md).
|
||||
|
||||
**Trigramme projet**
|
||||
3-letter project prefix used in Jira issue keys (`<TRIGRAMME>-NNN`) and in deployment Git tags (`<TRIGRAMME>-V<N>`, e.g. `LMD-V1`, `SPEN-V3`). See [Deploy Test Application](operations/deploy-test-application.md) and [Deploy Specific Commit](operations/deployment-specific-commit.md).
|
||||
|
||||
---
|
||||
|
||||
## U
|
||||
|
||||
**UoM (Unit of Measure)**
|
||||
|
||||
The measurement unit for an item (piece, kilogram, liter, meter, etc.). EasyWMS supports multiple UoMs per item with conversion factors. The base UoM is used for all internal calculations; presentation UoMs are used at reception and picking. See [Product / Item](concepts/product-item.md).
|
||||
|
||||
**UserImagesURI**
|
||||
Setting in the WMS `appsettings.json` that specifies the filesystem folder resolved for item pictures transmitted via `ITM01 <ItmPicture>filename.jpg</ItmPicture>`. Typical value: `C:/MLX/Data/Pictures/`. The WMS service account must have read access. See [ERP Interface](concepts/erp-interface.md#itm--image-fields).
|
||||
|
||||
**uGNA / uGNAConsole**
|
||||
Mecalux command-line utility (`C:\Program Files (x86)\Mecalux\uGNA\uGNAConsole.exe`) used to export the WMS configuration / master data / parameters to XML files (option `-Z:<entities>`). Output is committed to the project Git in `..\test`. Distinct from the GNA service (interfacing layer). See [uGNA Data Export](operations/ugna-data-export.md) and [GNA, Services & License](operations/gna-services-license.md).
|
||||
|
||||
---
|
||||
|
||||
## V
|
||||
|
||||
**Variable weight (Poids variable)**
|
||||
Option on the logistic profile of an item. When enabled, the stock weight must be provided at creation (manual or from ROR via the "Poids moyen" option). `StockAdjust` can modify line weights only for variable-weight items. See [Weights](concepts/weights.md) and [Product / Item](concepts/product-item.md).
|
||||
|
||||
**Vidage de bacs (Bin Emptying)**
|
||||
Picking efficiency mode ("empty first") that, when the last unit of an item is picked, marks the source location as empty so replenishment can start immediately rather than waiting for the next pick cycle. Driven by workflows `StockAssignProcess_CalculateEfficiencyModeToEmpty_PR` and variants. See [Picking](concepts/picking.md#vidage-de-bacs-efficiency-mode).
|
||||
|
||||
**VAS (Value Added Services)**
|
||||
Module for performing additional operations on stock (screen printing, container wrapping, labeling, kitting) within the warehouse. VAS activities are organized in templates with steps. See [VAS](modules/vas.md).
|
||||
|
||||
**View (AD)**
|
||||
An AD element type representing a read-only data projection. Used for all list screens in SmartUI and RF terminal displays. Often joins multiple entities. Examples: `ViewContainers`, `ViewStocks`, `ViewTasksOpen`, `ViewDockStage`. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**Voice picking**
|
||||
Picking mode guided by voice prompts through a headset. Controlled by `VOICE_ENABLED` parameter and requires voice middleware configuration. See [Picking](concepts/picking.md).
|
||||
|
||||
**VPN Mecalux (Europe / Europe 4)**
|
||||
Two SSL VPN gateways used by European delegations (except Gijón) to access the Mecalux network: `vpn-europa@mecalux.com:4443` (Europe) and `vpn-europa4@mecalux.com:443` (Europe 4). See [VM Network Routing](operations/vm-network-routing.md).
|
||||
|
||||
---
|
||||
|
||||
## W
|
||||
|
||||
**Wave**
|
||||
A batch of shipping orders grouped together for joint picking. All orders in a wave are released simultaneously; operators pick for multiple orders in a single pass through the warehouse. See [Shipping](concepts/shipping.md) and [Picking](concepts/picking.md).
|
||||
|
||||
**WMS (Warehouse Management System)**
|
||||
EasyWMS is Mecalux's WMS product.
|
||||
|
||||
**WOF (Work Order Fulfilled)**
|
||||
Outbound ERP message. Sent when a manufacturing work order is completed (finished good produced). See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**Workflow (AD)**
|
||||
An AD element type representing an orchestrated sequence of Commands, Queries, and sub-Workflows. Examples: `PutawayWorkflow`, `StockAssignmentWorkflow`, `ReplenishmentWorkflow`, `DefragmentationWorkflow`, `CountCloseWorkflow`. See [Application Dictionary](architecture/application-dictionary.md).
|
||||
|
||||
**WOR (Work Order Request)**
|
||||
Inbound ERP message for manufacturing work orders. Triggers the production process in EasyWMS. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
**WSC (Warehouse Stock Confirmation)**
|
||||
Outbound ERP message. Response to SCR (Stock Contrast Request); sends current WMS stock quantities to ERP for reconciliation. See [ERP Interface](concepts/erp-interface.md).
|
||||
|
||||
---
|
||||
|
||||
## X
|
||||
|
||||
**XD**
|
||||
Abbreviation for crossdocking. Used in strategy names and configuration fields (e.g., "Is XD location", "XD strategy"). See [Crossdocking](concepts/crossdocking.md).
|
||||
|
||||
---
|
||||
|
||||
## Y
|
||||
|
||||
**Yard Management module**
|
||||
EasyWMS add-on for managing vehicle arrivals and departures. Manages appointments, checkpoints, parking lots, dock assignments, and vehicle check-in/check-out. See [Yard Management](modules/yard-management.md).
|
||||
|
||||
---
|
||||
|
||||
## Z
|
||||
|
||||
**Zone**
|
||||
A logical grouping of aisles within a warehouse. Two types: **storage zones** (group storage aisles by product type or environment) and **working zones** (group work areas by equipment permissions and process types). See [Location](concepts/location.md) and [Warehouse Designer](concepts/warehouse-designer.md).
|
||||
|
||||
**ZAPP / Zscaler APP**
|
||||
Security agent that conflicts with Hyper-V NAT and breaks VPN connectivity to the Mecalux network. If installed on the developer's physical machine, it must be uninstalled and the machine rebooted; otherwise open a ticket `No Hyper-V NAT connectivity` to `it@mecalux.com`. See [VM Network Routing](operations/vm-network-routing.md).
|
||||
|
||||
---
|
||||
|
||||
## ERP Message Quick Reference
|
||||
|
||||
| Code | Direction | Description |
|
||||
|------|-----------|-------------|
|
||||
| ITM / ITC | ERP→WMS | Item / item catalog master |
|
||||
| OWN | ERP→WMS | Owner master |
|
||||
| CAR | ERP→WMS | Carrier master |
|
||||
| ACC | ERP→WMS | Account master |
|
||||
| SUP | ERP→WMS | Supplier master |
|
||||
| KIT | ERP→WMS | Kit structure |
|
||||
| LCK | ERP→WMS | Lock master |
|
||||
| ROR | ERP→WMS | Receipt order request |
|
||||
| ASN | ERP→WMS | ASN pre-notification |
|
||||
| SRN | ERP→WMS | Supplier return notification |
|
||||
| SOR | ERP→WMS | Shipping order request |
|
||||
| RUT | ERP→WMS | Route definition |
|
||||
| WOR | ERP→WMS | Work order (manufacturing) |
|
||||
| COR | ERP→WMS | Count order request |
|
||||
| STR | ERP→WMS | Stock status request (quality lock) |
|
||||
| SCR | ERP→WMS | Stock contrast request |
|
||||
| CMC | ERP→WMS | Container movement command |
|
||||
| ROC | WMS→ERP | Receipt order confirmation |
|
||||
| ROF | WMS→ERP | Receipt order fulfilled |
|
||||
| ASO / ASK | WMS→ERP | ASN confirmation / ASN rejection |
|
||||
| SRO / SRK | WMS→ERP | Return confirmation / fulfilled |
|
||||
| REF | WMS→ERP | Receipt error feedback |
|
||||
| SOC | WMS→ERP | Shipping order confirmation |
|
||||
| SOF | WMS→ERP | Shipping order fulfilled |
|
||||
| LOF | WMS→ERP | Load (truck) fulfilled |
|
||||
| WOF | WMS→ERP | Work order fulfilled |
|
||||
| COF | WMS→ERP | Count order fulfilled |
|
||||
| STV | WMS→ERP | Stock variation (quantity change) |
|
||||
| STC | WMS→ERP | Stock change (quality status) |
|
||||
| WSC | WMS→ERP | Warehouse stock confirmation |
|
||||
|
||||
---
|
||||
|
||||
## Transaction Code Quick Reference
|
||||
|
||||
| Prefix | Entity | Examples |
|
||||
|--------|--------|---------|
|
||||
| CON.* | Container | RECEP, PUT, MOVE, SHIP, VASDONE, CNL.ASN, SEND.L&F |
|
||||
| STK.* | Stock | RECEP, MOVE, ADJ, PICK, SHIP, REP, MAN.PRODUCTION |
|
||||
| CST.STK | Stock status | Quality lock change |
|
||||
| INO.* | Receipt order | CREATE, OPEN, CLS |
|
||||
| REC.* | Receipt document | CREATE, OPEN, CLS |
|
||||
| OUT.* | Shipping order | CREATE, OPEN, PICK, PREP, SHIP |
|
||||
| ROU.* / LOAD.* | Route / Load | CREATE, CLS |
|
||||
| TSK.* | Task | CREATE, ASS, INI, FIN, CNL, COU, ERR.EXTR, ERR.PUT |
|
||||
| COU.* | Count | CST, END, CLS, CNL |
|
||||
| WOR.* / KOU.* | Work order / Kit | CREATE, FIN, CLS |
|
||||
|
||||
Full reference: [Transactions](concepts/transactions.md).
|
||||
Reference in New Issue
Block a user