Route
mainRoute operation sequence — one row per operation number on a route, ordering the operations and linking each to the next; operation times live on the related RouteOpr table
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).
Header & line
Route lines join back to their header RouteTable — and the DataAreaId — so a line never fans out across companies.
Fields
8 fields · 2 key
8 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | RouteId | RouteId | The route this operation row belongs to | string | 20 | |
| Key | OprNum | Operation number — orders the operations within the route | int | |||
| OprPriority | Priority of the row when several rows share an operation number (primary / secondary) | enum | ||||
| OprId | Operation identifier — the reusable operation definition this step runs; times live on the related RouteOpr rows | string | ||||
| OprNumNext | Operation number of the next step; 0 marks the last operation | int | ||||
| LinkType | Whether the next operation is hard-linked (no queue between) or free | enum | ||||
| Level | Network level of the operation within the route. Reserved word — lands as level_ in Synapse Link / Fabric Link exports | int | ||||
| ErrorPct | Expected error (scrap) percentage of the operation | real |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading Route 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.
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Table : Route Route operation sequence — one row per operation number on a route, ordering the operations and linking each to the next; operation times live on the related RouteOpr table
-- Purpose: Column-selected read of Route — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + RouteId + OprNum
-- 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 this operation row belongs to",
r.oprnum AS "Operation number — orders the operations within the route",
r.oprpriority AS "Priority of the row when several rows share an operation number (primary / secondary)", -- enum: decode r.oprpriority via GlobalOptionsetMetadata join — see quirks guide #enums
r.oprid AS "Operation identifier — the reusable operation definition this step runs; times live on the related RouteOpr rows",
r.oprnumnext AS "Operation number of the next step; 0 marks the last operation",
r.linktype AS "Whether the next operation is hard-linked (no queue between) or free", -- enum: decode r.linktype via GlobalOptionsetMetadata join — see quirks guide #enums
r.level_ AS "Network level of the operation within the route",
r.errorpct AS "Expected error (scrap) percentage of the operation"
FROM <catalog>.<schema>.route 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.dataareaid
Data Entities That Expose This Table
More Production Control tables
- RouteTableRoute 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
- 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