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
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
| 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 | int | ||||
| ErrorPct | Expected error (scrap) percentage of the operation | real |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading Routeon 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.
-- ============================================================
-- 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;3 parameters not filled: <catalog>, <schema>, <company>
Relationships
1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON routetable.routeid = route.routeid