D365 Reference
RouteTable
mainRoute header — one row per route identifier with its name and approval state; route versions assign it to items, and Route rows hold its operation sequence
Module: Production ControlCompany-partitioned (DataAreaId)
What the badges mean
- main
- Table group: how F&O categorizes the table's role — main entity, group/header, transaction, worksheet header, worksheet line, reference, parameter, or framework.
- Shared across companies
- The table carries no
DataAreaId— rows aren’t partitioned per company, so a query never needs (and can’t use) a company filter here (see the quirks guide). - Date-effective
- The table carries a
ValidFrom/ValidToeffectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
In field listings, K marks a key field.
Header & line
RouteTable is the header for its lines in Route.
Fields
6 fields · 1 key
6 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | RouteId | RouteId | The route identifier — the natural key operations and versions join on | string | 20 | |
| Name | Route name | string | 60 | |||
| ItemGroupId | Item group used to filter and organize routes | string | ||||
| Approved | Whether the route header is approved for use | enum | ||||
| Approver | RecId | RecId of the worker who approved the route | int64 | |||
| CheckRoute | Whether route network validation is enforced | enum |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading RouteTable on Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
Query parameters
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Table : RouteTable Route header — one row per route identifier with its name and approval state; route versions assign it to items, and Route rows hold its operation sequence
-- Purpose: Column-selected read of RouteTable — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + RouteId
-- Notes : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
r.routeid AS "The route identifier — the natural key operations and versions join on",
r.name AS "Route name",
r.itemgroupid AS "Item group used to filter and organize routes",
r.approved AS "Whether the route header is approved for use", -- enum: decode r.approved via GlobalOptionsetMetadata join — see quirks guide #enums
r.approver AS "RecId of the worker who approved the route",
r.checkroute AS "Whether route network validation is enforced" -- enum: decode r.checkroute via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.routetable r
WHERE
r.dataareaid = '<company>'
ORDER BY r.routeid;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON routetable.routeid = route.routeid AND routetable.dataareaid = route.dataareaidON prodtable.routeid = routetable.routeid AND prodtable.dataareaid = routetable.dataareaidON routeversion.routeid = routetable.routeid AND routeversion.dataareaid = routetable.dataareaid
Data Entities That Expose This Table
Route export entities exist in Data management, but their programmatic names could not be primary-source verified — land the raw tables.
More Production Control tables
- RouteVersionRoute version — the link that assigns a route to a finished item for a validity period, quantity range, and site, mirroring how BOMVersion assigns a BOM
- BOMBill of materials line — one component per row under a BOM header, with quantity per unit, validity dates, scrap factors, and the operation it is consumed at
- BOMTableBill of materials header — one row per BOM identifier, with its name, approval state, and production site; versions in BOMVersion decide which items use it and when
- BOMVersionBOM version — the link that assigns a BOM header to a finished item for a validity period, quantity range, and site; the Active flag decides which version planning and orders pick
- ProdBOMProduction order BOM line — the materials a specific production order plans to consume, copied from the item's active BOM at order creation and then adjusted per order
- ProdTableProduction order header — one row per order carrying the item being built, order status and type, scheduled and actual dates, and the BOM and route it was created from