M3 Reference

MITBAL

Prefix: MBbalance

The item/warehouse record — one row per item and warehouse, pairing planning policy (safety stock, reorder point, lead time, main supplier) with the warehouse-level on-hand and allocated balances

Module: Inventory & WarehouseCompany-partitioned (CONO)Parent: MITMAS

What the badges mean

Prefix: MM: Prefix: the table’s 2-character physical-column prefix (e.g. MM on MITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide).
master: Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
Shared across companies: The table carries no CONO — rows aren’t partitioned per company (see the quirks guide).
Division-level: The table carries DIVI — rows are scoped below company to a division, one layer more granular than CONO alone (see the quirks guide).

Used in the library

KPI definitions

K-05Inventory Turns

K-06Days of Supply (DOS / DIO)

K-10Excess & Obsolete (E&O)

K-11Cash-to-Cash Cycle Time

Dashboard patterns

D-01Inventory Health

D-03S&OP / Demand Review

Cross-ERP guides

GuideERP Deletes & Change Tracking

GuideSource History & Ingestion Path

GuideMedallion Layer Contracts for ERP Data

GuideInventory Snapshot Patterns

GuideERP Data Quality Checklist

Parent & satellites

MITBAL is a satellite of MITMAS — many rows here per MITMAS row; join on ITNO plus the CONO (exact ON clause under Join details below).

MITBAL is the parent master for MITLOC — each carries many rows per MITBAL row at its own grain.

Fields

10 fields · 3 key

10 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 10 fields.
Key	Field	Alias	Description	Type	Flags
Key	MBCONO	CONO	Company	numeric
Key	MBWHLO	WHLO	Warehouse	alphanumeric
Key	MBITNO	ITNO	Item number	alphanumeric
	MBSTAT	STAT	Item/warehouse status — whether the item is active in this warehouse	alphanumeric	Status
	MBSTQT	STQT	On-hand balance in the warehouse, in the basic unit	numeric
	MBALQT	ALQT	Allocated quantity — stock reserved against demand but not yet issued	numeric
	MBSSQT	SSQT	Safety stock quantity for the item in this warehouse	numeric
	MBREOP	REOP	Reorder point that triggers replenishment for the item in this warehouse	numeric
	MBLEAT	LEAT	Lead time in days used by planning for this item/warehouse	numeric
	MBSUNO	SUNO	Main supplier for replenishing the item in this warehouse — the default sourcing join to CIDMAS	alphanumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MITBAL on Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO 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

CatalogSchemaCompany (CONO)Warehouse (WHLO)Item number (ITNO)

Include optional filters (2)

5 parameters not filled: <catalog>, <schema>, <company>, <WHLO>, <ITNO>

-- ============================================================
-- Table  : MITBAL — The item/warehouse record — one row per item and warehouse, pairing planning policy (safety stock, reorder point, lead time, main supplier) with the warehouse-level on-hand and allocated balances
-- Purpose: Column-selected read of MITBAL — auto-generated from field metadata
-- Grain  : One row per company (CONO) + MBWHLO + MBITNO
-- Notes  : Auto-generated skeleton for a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
  ib.MBCONO AS "Company",
  ib.MBWHLO AS "Warehouse",
  ib.MBITNO AS "Item number",
  ib.MBSTAT AS "Item/warehouse status — whether the item is active in this warehouse",  -- status: decode ib.MBSTAT against your configuration — see quirks guide #statuses
  ib.MBSTQT AS "On-hand balance in the warehouse, in the basic unit",
  ib.MBALQT AS "Allocated quantity — stock reserved against demand but not yet issued",
  ib.MBSSQT AS "Safety stock quantity for the item in this warehouse",
  ib.MBREOP AS "Reorder point that triggers replenishment for the item in this warehouse",
  ib.MBLEAT AS "Lead time in days used by planning for this item/warehouse",
  ib.MBSUNO AS "Main supplier for replenishing the item in this warehouse — the default sourcing join to CIDMAS"
FROM <catalog>.<schema>.MITBAL ib
WHERE
  ib.MBCONO = <company>
  -- AND ib.MBWHLO = '<WHLO>'
  -- AND ib.MBITNO = '<ITNO>'
ORDER BY ib.MBWHLO;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

MITBALMITMASforeign key · N:1
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITBAL.MBITNO = MITMAS.MMITNO AND MITBAL.MBCONO = MITMAS.MMCONO
MITBALMITWHLforeign key · N:1
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITBAL.MBWHLO = MITWHL.MWWHLO AND MITBAL.MBCONO = MITWHL.MWCONO
MITBALCIDMASforeign key · N:1
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITBAL.MBSUNO = CIDMAS.IDSUNO AND MITBAL.MBCONO = CIDMAS.IDCONO
MITLOCMITBALforeign key · N:1
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITLOC.MLWHLO = MITBAL.MBWHLO AND MITLOC.MLITNO = MITBAL.MBITNO AND MITLOC.MLCONO = MITBAL.MBCONO