M3 Reference
MILOMA
Prefix: LMmasterThe lot master — one row per item and lot (batch) number, carrying the lot's identity and life-cycle dates; location balances and allocations reference it by BANO
Module: Inventory & WarehouseCompany-partitioned (CONO)
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — 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 thanCONOalone (see the quirks guide).
In field listings, K marks a primary-key field.
Fields
5 fields · 3 key
5 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | LMCONO | CONO | Company | numeric | ||
| Key | LMITNO | ITNO | Item number | alphanumeric | ||
| Key | LMBANO | BANO | Lot (batch) number — unique per item, not global | alphanumeric | ||
| LMEXPI | EXPI | Expiration date of the lot | numeric | |||
| LMMFDT | MFDT | Manufacturing date of the lot | numeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MILOMA 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
5 parameters not filled: <catalog>, <schema>, <company>, <ITNO>, <BANO>
-- ============================================================
-- Table : MILOMA — The lot master — one row per item and lot (batch) number, carrying the lot's identity and life-cycle dates; location balances and allocations reference it by BANO
-- Purpose: Column-selected read of MILOMA — auto-generated from field metadata
-- Grain : One row per company (CONO) + LMITNO + LMBANO
-- 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.LMCONO AS "Company",
m.LMITNO AS "Item number",
m.LMBANO AS "Lot (batch) number — unique per item, not global",
CASE WHEN m.LMEXPI = 0 THEN NULL ELSE TO_DATE(CAST(CAST(m.LMEXPI AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Expiration date of the lot", -- YYYYMMDD, 0 → NULL
CASE WHEN m.LMMFDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(m.LMMFDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Manufacturing date of the lot" -- YYYYMMDD, 0 → NULL
FROM <catalog>.<schema>.MILOMA m
WHERE
m.LMCONO = <company>
-- AND m.LMITNO = '<ITNO>'
-- AND m.LMBANO = '<BANO>'
ORDER BY m.LMITNO;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
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MILOMA.LMITNO = MITMAS.MMITNO AND MILOMA.LMCONO = MITMAS.MMCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MITLOC.MLBANO = MILOMA.LMBANO AND MITLOC.MLITNO = MILOMA.LMITNO AND MITLOC.MLCONO = MILOMA.LMCONO-- 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
- MITALOAllocations — 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
- MITBALThe 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
- MITLOCThe location-level balance — one row per item, warehouse, location, lot, and receipt, holding the physical on-hand at the finest grain M3 tracks stock; warehouse-level figures in MITBAL are the roll-up of these rows
- MITTRAThe stock transaction ledger — one row per inventory movement (receipt, issue, transfer, adjustment) with its transaction type, quantity, date, and the order reference that caused it
- MITWHLThe warehouse master — one row per warehouse with its name, facility, and warehouse type; the WHLO every balance and movement carries resolves here