D365 Reference

PurchPurchaseOrderHeaderV2Entity

OData: PurchaseOrderHeadersV2

Purchase order headers — one record per order, the header-level export for procure-to-pay

Module: Procurement & Sourcing
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

V2 header entity; research-confirmed.

Rebuild-from-tables SQL

Databricks SQL

Starting 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
-- ============================================================
-- Entity : PurchPurchaseOrderHeaderV2Entity (OData: PurchaseOrderHeadersV2)
-- Purpose: Rebuild PurchPurchaseOrderHeaderV2Entity from landed F&O tables — auto-generated from table-entity-map
-- Grain  : One row per PurchTable record
-- Tables : PurchTable
-- 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
  po.purchid AS "The purchase order number — the natural key",
  po.purchname AS "Free-text order description",
  po.deliveryname AS "Name at the delivery address"
FROM <catalog>.<schema>.purchtable po
WHERE
  po.dataareaid = '<company>'
ORDER BY po.purchid;

3 parameters not filled: <catalog>, <schema>, <company>

Backing Tables