Skip to content
D365 Reference

Route

main

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

Module: Production ControlCompany-partitioned (DataAreaId)Header: RouteTable
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/ValidTo effectivity 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

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.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 8 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyRouteIdRouteIdThe route this operation row belongs tostring20
KeyOprNumOperation number — orders the operations within the routeint
OprPriorityPriority of the row when several rows share an operation number (primary / secondary)enum
OprIdOperation identifier — the reusable operation definition this step runs; times live on the related RouteOpr rowsstring
OprNumNextOperation number of the next step; 0 marks the last operationint
LinkTypeWhether the next operation is hard-linked (no queue between) or freeenum
LevelNetwork level of the operation within the route. Reserved word — lands as level_ in Synapse Link / Fabric Link exportsint
ErrorPctExpected error (scrap) percentage of the operationreal

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.

Query parameters

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

  • RouteTableRouteheader line · 1:N
    ON routetable.routeid = route.routeid AND routetable.dataareaid = route.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.

Browse more production tables

More Production Control tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Microsoft. Microsoft, Dynamics 365, and Microsoft Fabric are trademarks of the Microsoft group of companies.