D365 Reference
InventTransOrigin
transactionThe 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/ValidToeffectivity 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.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | InventTransId | InventTransId | The transaction reference string that groups all movements for one source document line | string | 40 | |
| ReferenceCategory | What kind of document created the origin (sales, purchase, transfer, production…) — the discriminator for the polymorphic reference | enum | ||||
| ItemId | ItemId | Item the origin is for | string | 20 | ||
| RecId | RecId | The 64-bit surrogate key InventTrans.InventTransOrigin joins to | int64 | |||
| ReferenceId | Document number of the originating reference — the sales order, purchase order, or journal id, typed by ReferenceCategory | string | ||||
| Party | RecId | RecId of the counterparty's global-address-book party in DirPartyTable, where the origin has one | int64 | |||
| ItemInventDimId | InventDimId | Dimension combination carrying the origin's product dimensions (variant), before site/warehouse are decided | string | |||
| IsExcludedFromInventoryValue | Whether transactions from this origin are excluded from inventory value reporting | enum |
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
ON inventtrans.inventtransorigin = inventtransorigin.recidON reqtrans.inventtransorigin = inventtransorigin.recid
Data Entities That Expose This Table
No standard export entity — land the raw table.
More Inventory tables
- WMSLocationWarehouse location (bin) master — one row per storage location within a warehouse, with its aisle/rack/level coordinates, zone, profile, and capacity limits
- InventBatchBatch master — one row per item and batch number, carrying expiry and manufacturing dates plus vendor batch details; the record behind the inventBatchId dimension
- InventDimThe inventory dimension hub — one row per unique combination of site, warehouse, location, batch, and serial that every stock quantity hangs off by InventDimId
- InventItemPriceItem price records — activated cost, purchase, and sales prices per item, costing version, and dimension; the source for standard-cost analysis
- InventJournalTableInventory journal header — one row per movement, adjustment, transfer, BOM, or counting journal, with its type, posting status, and line count
- InventJournalTransInventory journal line — one row per item movement in a journal, with quantity, cost, counted figures, and the dimension combination it posts against