Skip to content
D365 Reference

InventTransOrigin

transaction

The origin record every inventory transaction points to — resolves an InventTrans row back to the sales line, purchase line, or journal that created it

Module: InventoryCompany-partitioned (DataAreaId)
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.

Fields

8 fields · 1 key

8 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 8 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyInventTransIdInventTransIdThe transaction reference string that groups all movements for one source document linestring40
ReferenceCategoryWhat kind of document created the origin (sales, purchase, transfer, production…) — the discriminator for the polymorphic referenceenum
ItemIdItemIdItem the origin is forstring20
RecIdRecIdThe 64-bit surrogate key InventTrans.InventTransOrigin joins toint64
ReferenceIdDocument number of the originating reference — the sales order, purchase order, or journal id, typed by ReferenceCategorystring
PartyRecIdRecId of the counterparty's global-address-book party in DirPartyTable, where the origin has oneint64
ItemInventDimIdInventDimIdDimension combination carrying the origin's product dimensions (variant), before site/warehouse are decidedstring
IsExcludedFromInventoryValueWhether transactions from this origin are excluded from inventory value reportingenum

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading InventTransOrigin 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  : InventTransOrigin The origin record every inventory transaction points to — resolves an InventTrans row back to the sales line, purchase line, or journal that created it
-- Purpose: Column-selected read of InventTransOrigin — auto-generated from field metadata
-- Grain  : One row per company (dataareaid) + InventTransId
-- 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
  ito.inventtransid AS "The transaction reference string that groups all movements for one source document line",
  ito.referencecategory AS "What kind of document created the origin (sales, purchase, transfer, production…) — the discriminator for the polymorphic reference",  -- enum: decode ito.referencecategory via GlobalOptionsetMetadata join — see quirks guide #enums
  ito.itemid AS "Item the origin is for",
  ito.recid AS "The 64-bit surrogate key InventTrans.InventTransOrigin joins to",
  ito.referenceid AS "Document number of the originating reference — the sales order, purchase order, or journal id, typed by ReferenceCategory",
  ito.party AS "RecId of the counterparty's global-address-book party in DirPartyTable, where the origin has one",
  ito.iteminventdimid AS "Dimension combination carrying the origin's product dimensions (variant), before site/warehouse are decided",
  ito.isexcludedfrominventoryvalue AS "Whether transactions from this origin are excluded from inventory value reporting"  -- enum: decode ito.isexcludedfrominventoryvalue via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.inventtransorigin ito
WHERE
  ito.dataareaid = '<company>'
ORDER BY ito.inventtransid;

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

  • InventTransInventTransOriginRecId ref · N:1
    ON inventtrans.inventtransorigin = inventtransorigin.recid
  • ReqTransInventTransOriginRecId ref · N:1
    ON reqtrans.inventtransorigin = inventtransorigin.recid

Data Entities That Expose This Table

No standard export entity — land the raw table.

Browse more inventory tables

More Inventory 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.