arthur
9ce6ae37be
- 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)
88 lines
4.2 KiB
Markdown
88 lines
4.2 KiB
Markdown
---
|
|
title: "Owner Extensions"
|
|
type: module
|
|
sources:
|
|
- areas/ownerextensions/index.md
|
|
related:
|
|
- modules/billing-3pl.md
|
|
- modules/3pl-portal.md
|
|
- modules/directives.md
|
|
- concepts/order-inbound.md
|
|
- concepts/order-outbound.md
|
|
last_compiled: "2026-04-10"
|
|
---
|
|
|
|
# Owner Extensions
|
|
|
|
## Overview
|
|
|
|
Owner Extensions is a prerequisite intermediate module that must be installed before using the **3PL Portal** and **Billing** modules. It enforces owner-level isolation across orders and master data, making it possible to manage multiple 3PL clients in the same warehouse with complete data separation.
|
|
|
|
The module adds a mandatory **owner field** to receipt orders and shipping orders, and enforces that all lines within an order belong to the same owner as the order header. It also adds owner scoping to key master data entities so that the same item, account, or supplier can exist independently per owner.
|
|
|
|
## Key capabilities
|
|
|
|
- Mandatory owner on receipt orders (inbound)
|
|
- Mandatory owner on shipping orders (outbound)
|
|
- Owner-isolated master data for 8 entity types
|
|
- Code uniqueness per owner (concatenated code = owner + element code)
|
|
- Foundation for 3PL Portal visibility filtering
|
|
- Foundation for Billing contract assignment
|
|
|
|
## Architecture
|
|
|
|
### Owner enforcement on orders
|
|
|
|
| Order type | Effect |
|
|
|------------|--------|
|
|
| Receipt orders | Owner field becomes mandatory at creation; all lines must belong to the same owner |
|
|
| Shipping orders | Owner field becomes mandatory at creation; all lines must belong to the same owner |
|
|
|
|
The owner requirement enables:
|
|
- **3PL Portal**: filters all WMS views by the logged-in client's owner, so each 3PL client sees only their own stock, orders, and reports
|
|
- **Billing**: uniquely identifies which 3PL contract each order and order line belongs to for economic valuation
|
|
|
|
### Owner-isolated master data
|
|
|
|
The following master data entities gain an owner field, making each record unique per owner:
|
|
|
|
| Entity | Notes |
|
|
|--------|-------|
|
|
| Companies | Owner-scoped company records |
|
|
| Account types | Account type classifications per owner |
|
|
| Accounts | End-customer accounts per owner |
|
|
| Supplier types | Supplier type classifications per owner |
|
|
| Suppliers | Supplier records per owner |
|
|
| Item types | Item type classifications per owner |
|
|
| Item families | Item family groupings per owner |
|
|
|
|
The element code is **concatenated with the owner** to ensure uniqueness. This prevents conflicts when the same item code, account, or supplier exists for multiple 3PL clients.
|
|
|
|
ERP integrations that send master data via communications must include the owner in the message so that records are correctly identified and no ambiguity exists when the same element exists across multiple owners.
|
|
|
|
### Exceptions (no owner required)
|
|
|
|
Two order types are exempt from the mandatory owner constraint:
|
|
|
|
| Exception | Reason |
|
|
|-----------|--------|
|
|
| Groups and fusions | A group may consolidate orders from multiple owners; requiring a single owner would prevent this use case |
|
|
| Replenishments between warehouses | Internal warehouse replenishments may cross owner boundaries and do not follow single-owner shipping order logic |
|
|
|
|
For these exceptions, if the order code would normally be concatenated with the owner, the concatenation is skipped when the order involves multiple owners.
|
|
|
|
## Configuration
|
|
|
|
Owner Extensions is installed as an intermediate module during WMS deployment (not configured from the WMS interface). Once installed:
|
|
1. Existing receipt and shipping order creation flows require owner selection
|
|
2. Master data forms for the 8 entity types require owner selection
|
|
3. 3PL Portal and Billing modules become installable
|
|
|
|
## Related
|
|
|
|
- [[billing-3pl]] - Requires Owner Extensions; uses the owner field on orders to assign lines to the correct billing contract
|
|
- [[3pl-portal]] - Requires Owner Extensions; uses the owner field to filter all portal views to the logged-in client's owner
|
|
- [[directives]] - Owner directives apply per-owner customization to shipping processes; Owner Extensions provides the owner field that enables this filtering
|
|
- [[order-inbound]] - Receipt orders gain mandatory owner field with Owner Extensions installed
|
|
- [[order-outbound]] - Shipping orders gain mandatory owner field with Owner Extensions installed
|