D365 Reference
ProdProductionOrderHeaderEntity
OData: ProductionOrderHeadersProduction orders — one record per production order header, the standard export for order status, quantities, and schedule dates
Tables vs entities
This entity is an export-shaped view over the tables below. When you land raw F&O tables instead of the entity, the SQL further down rebuilds it — joining the backing tables on their keys and DataAreaId. When to land tables vs entities
Notes
No V2 variant. Name confirmed via the CDM entity page; ProductionOrderHeaders collection corroborated by practitioner OData usage.
Rebuild-from-tables SQL
Databricks SQLStarting point for reconstructing this entity from landed tables — the backing tables joined on their keys and DataAreaId. Set your Unity Catalog location, company, and filter values below.
Query parameters
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Entity : ProdProductionOrderHeaderEntity (OData: ProductionOrderHeaders)
-- Purpose: Rebuild ProdProductionOrderHeaderEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per ProdTable record
-- Tables : ProdTable
-- 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. Company-partitioned tables are joined on DataAreaId to prevent cross-company fan-out. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
pr.prodid AS "The production order number — the natural key BOM lines and postings join back on",
pr.name AS "Order description, defaulted from the item name"
FROM <catalog>.<schema>.prodtable pr
WHERE
pr.dataareaid = '<company>'
ORDER BY pr.prodid;