Skip to content
M3 Reference

MMS002

Interactive

Item/warehouse maintenance — connects items to warehouses and manages the MITBAL planning parameters

Tables vs APIs

This program works over the tables below. For analytics at scale, land the raw tables — the SQL further down reads them directly, joined on their keys and CONO. When to land tables vs call MI APIs →

Boilerplate SQL

Databricks SQL

Starting point for reading the tables behind MMS002 from landed data — the backing tables joined on their keys and CONO. Set your Unity Catalog location, company, and filter values below.

Query parameters
-- ============================================================
-- Program: MMS002 — Item/warehouse maintenance — connects items to warehouses and manages the MITBAL planning parameters
-- Purpose: Read the tables behind program MMS002 — auto-generated from program-table-map
-- Grain  : MITBAL × MITMAS, MITWHL — 1:N joins yield one row per line
-- Tables : MITBAL, MITMAS, MITWHL
-- 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; company-partitioned tables are joined on CONO to prevent cross-company fan-out. 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.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",
  im.MMITDS AS "Item name (short description)",
  im.MMFUDS AS "Item description (full)",
  w.MWWHNM AS "Warehouse name"
FROM <catalog>.<schema>.MITBAL ib
LEFT JOIN <catalog>.<schema>.MITMAS im
  ON im.MMITNO = ib.MBITNO
 AND im.MMCONO = ib.MBCONO
LEFT JOIN <catalog>.<schema>.MITWHL w
  ON w.MWWHLO = ib.MBWHLO
 AND w.MWCONO = ib.MBCONO
WHERE
  ib.MBCONO = <company>
ORDER BY ib.MBWHLO;

3 parameters not filled: <catalog>, <schema>, <company>

Backing Tables

How these tables connect. Nodes are clickable.

Join details

  • MITBALMITMASforeign key · N:1
    ON MITBAL.MBITNO = MITMAS.MMITNO AND MITBAL.MBCONO = MITMAS.MMCONO
  • MITBALMITWHLforeign key · N:1
    ON MITBAL.MBWHLO = MITWHL.MWWHLO AND MITBAL.MBCONO = MITWHL.MWCONO

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.