Skip to content
M3 Reference

MITALO

Prefix: MQtransaction

Allocations — one row per item, location, and lot allocated to a specific order line, connecting demand (the order reference) to the exact stock that will fill it; the bridge between order lines and MITLOC balances

Module: Inventory & WarehouseCompany-partitioned (CONO)
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).
In field listings, K marks a primary-key field.

Fields

9 fields · 5 key

9 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 9 fields.
KeyFieldAliasDescriptionTypeLengthFlags
KeyMQCONOCONOCompanynumeric
KeyMQWHLOWHLOWarehousealphanumeric
KeyMQITNOITNOItem numberalphanumeric
KeyMQWHSLWHSLStock location the allocation points atalphanumeric
KeyMQBANOBANOLot (batch) number allocatedalphanumeric
MQORCAORCAOrder category of the demand being served (customer order, manufacturing order…)alphanumeric
MQRIDNRIDNOrder number of the demand line the stock is allocated toalphanumeric
MQRIDLRIDLOrder line number of the demandnumeric
MQALQTALQTAllocated quantitynumeric

Field provenance: hand-curated.

Boilerplate SQL

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

7 parameters not filled: <catalog>, <schema>, <company>, <WHLO>, <ITNO>, <WHSL>, <BANO>

-- ============================================================
-- Table  : MITALO — Allocations — one row per item, location, and lot allocated to a specific order line, connecting demand (the order reference) to the exact stock that will fill it; the bridge between order lines and MITLOC balances
-- Purpose: Column-selected read of MITALO — auto-generated from field metadata
-- Grain  : Transaction-grain — finer than company (CONO) + MQWHLO + MQITNO + MQWHSL + MQBANO; the full row key is not yet cataloged (see the table description)
-- 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
  m.MQCONO AS "Company",
  m.MQWHLO AS "Warehouse",
  m.MQITNO AS "Item number",
  m.MQWHSL AS "Stock location the allocation points at",
  m.MQBANO AS "Lot (batch) number allocated",
  m.MQORCA AS "Order category of the demand being served (customer order, manufacturing order…)",
  m.MQRIDN AS "Order number of the demand line the stock is allocated to",
  m.MQRIDL AS "Order line number of the demand",
  m.MQALQT AS "Allocated quantity"
FROM <catalog>.<schema>.MITALO m
WHERE
  m.MQCONO = <company>
  -- AND m.MQWHLO = '<WHLO>'
  -- AND m.MQITNO = '<ITNO>'
  -- AND m.MQWHSL = '<WHSL>'
  -- AND m.MQBANO = '<BANO>'
ORDER BY m.MQWHLO;

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

  • MITALOMITMASforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITALO.MQITNO = MITMAS.MMITNO AND MITALO.MQCONO = MITMAS.MMCONO
  • MITALOMITWHLforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITALO.MQWHLO = MITWHL.MWWHLO AND MITALO.MQCONO = MITWHL.MWCONO
  • MITALOMILOMAforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITALO.MQBANO = MILOMA.LMBANO AND MITALO.MQITNO = MILOMA.LMITNO AND MITALO.MQCONO = MILOMA.LMCONO

Programs That Use This Table

More Inventory & Warehouse 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 Infor. Infor, Infor M3, and Infor CloudSuite are trademarks of Infor and/or its affiliates.