Skip to content
M3 Reference

MILOMA

Prefix: LMmaster

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

Module: Inventory & WarehouseCompany-partitioned (CONO)

Fields

5 fields · 3 key

KeyFieldAliasDescriptionTypeLengthFlags
KeyLMCONOCONOCompanynumeric
KeyLMITNOITNOItem numberalphanumeric
KeyLMBANOBANOLot (batch) number — unique per item, not globalalphanumeric
LMEXPIEXPIExpiration date of the lotnumeric
LMMFDTMFDTManufacturing date of the lotnumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MILOMAon 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
-- ============================================================
-- 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 Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified. 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;

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

Relationships

1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MILOMAMITMASforeign key · N:1
    ON MILOMA.LMITNO = MITMAS.MMITNO AND MILOMA.LMCONO = MITMAS.MMCONO
  • MITLOCMILOMAforeign key · N:1
    ON MITLOC.MLBANO = MILOMA.LMBANO AND MITLOC.MLCONO = MILOMA.LMCONO
  • MITALOMILOMAforeign key · N:1
    ON MITALO.MQBANO = MILOMA.LMBANO AND MITALO.MQCONO = MILOMA.LMCONO

Programs That Use This Table

No program mappings populated for this table yet.

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

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.