Skip to content
D365 Reference

InventLocation

group

Warehouse master — one row per warehouse (inventory location) with its site and type

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.
Used in the library
Dashboard patterns

Fields

15 fields · 1 key

15 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 15 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyInventLocationIdInventLocationIdThe warehouse codestring10
InventSiteIdInventSiteIdSite the warehouse belongs tostring10
NameWarehouse namestring60
InventLocationTypeWhether the warehouse is a default, quarantine, or transit locationenum
WHSEnabledWhether advanced warehouse management (WHS) processes run in this warehouseenum
DefaultStatusIdDefault inventory status applied to receipts in this warehousestring
InventLocationIdQuarantineInventLocationIdQuarantine warehouse paired with this onestring
InventLocationIdTransitInventLocationIdTransit warehouse used for transfer orders shipping from this onestring
InventLocationIdReqMainInventLocationIdMain warehouse this one is refilled from in master planningstring
ReqRefillWhether master planning refills this warehouse from its main warehouseenum
ManualWhether items in this warehouse are planned manually rather than by master planningenum
ReqCalendarIdWorking-time calendar master planning uses for this warehousestring
InventLocationLevelLevel of the warehouse in a multi-level refill hierarchyint
VendAccountVendAccountVendor account, for externally located (vendor-managed) warehousesstring
BranchNumberBranch number used by localizations that report warehouses as branchesstring

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading InventLocation 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

4 parameters not filled: <catalog>, <schema>, <company>, <InventLocationId>

-- ============================================================
-- Table  : InventLocation Warehouse master — one row per warehouse (inventory location) with its site and type
-- Purpose: Column-selected read of InventLocation — auto-generated from field metadata
-- Grain  : One row per company (dataareaid) + InventLocationId
-- 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
  loc.inventlocationid AS "The warehouse code",
  loc.inventsiteid AS "Site the warehouse belongs to",
  loc.name AS "Warehouse name",
  loc.inventlocationtype AS "Whether the warehouse is a default, quarantine, or transit location",  -- enum: decode loc.inventlocationtype via GlobalOptionsetMetadata join — see quirks guide #enums
  loc.whsenabled AS "Whether advanced warehouse management (WHS) processes run in this warehouse",  -- enum: decode loc.whsenabled via GlobalOptionsetMetadata join — see quirks guide #enums
  loc.defaultstatusid AS "Default inventory status applied to receipts in this warehouse",
  loc.inventlocationidquarantine AS "Quarantine warehouse paired with this one",
  loc.inventlocationidtransit AS "Transit warehouse used for transfer orders shipping from this one",
  loc.inventlocationidreqmain AS "Main warehouse this one is refilled from in master planning",
  loc.reqrefill AS "Whether master planning refills this warehouse from its main warehouse",  -- enum: decode loc.reqrefill via GlobalOptionsetMetadata join — see quirks guide #enums
  loc.manual AS "Whether items in this warehouse are planned manually rather than by master planning",  -- enum: decode loc.manual via GlobalOptionsetMetadata join — see quirks guide #enums
  loc.reqcalendarid AS "Working-time calendar master planning uses for this warehouse",
  loc.inventlocationlevel AS "Level of the warehouse in a multi-level refill hierarchy",
  loc.vendaccount AS "Vendor account, for externally located (vendor-managed) warehouses",
  loc.branchnumber AS "Branch number used by localizations that report warehouses as branches"
FROM <catalog>.<schema>.inventlocation loc
WHERE
  loc.dataareaid = '<company>'
  -- AND loc.inventlocationid = '<InventLocationId>'
ORDER BY loc.inventlocationid;

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

  • WMSLocationInventLocationforeign key · N:1
    ON wmslocation.inventlocationid = inventlocation.inventlocationid AND wmslocation.dataareaid = inventlocation.dataareaid
  • InventLocationInventSiteforeign key · N:1
    ON inventlocation.inventsiteid = inventsite.siteid AND inventlocation.dataareaid = inventsite.dataareaid

Data Entities That Expose This Table

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.