MITMAS
Prefix: MMmasterThe item master — one row per item per company, carrying the item's identity, status, grouping codes, basic unit of measure, and physical attributes; every balance, order line, and stock movement joins back to it on ITNO
Fields
14 fields · 2 key
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | MMCONO | CONO | Company | numeric | ||
| Key | MMITNO | ITNO | Item number — the natural key every balance, order line, and movement joins on | alphanumeric | ||
| MMSTAT | STAT | Item status — a two-char ladder from preliminary through active to deactivated | alphanumeric | |||
| MMITDS | ITDS | Item name (short description) | alphanumeric | |||
| MMFUDS | FUDS | Item description (full) | alphanumeric | |||
| MMITTY | ITTY | Item type — the code that controls how the item behaves across modules | alphanumeric | |||
| MMITGR | ITGR | Item group — the primary reporting and posting bucket for the item | alphanumeric | |||
| MMITCL | ITCL | Product group — a second classification slice alongside the item group | alphanumeric | |||
| MMBUAR | BUAR | Business area — the broadest reporting classification on the item | alphanumeric | |||
| MMUNMS | UNMS | Basic unit of measure — the unit balances and movements are stored in | alphanumeric | |||
| MMNEWE | NEWE | Net weight of one basic unit | numeric | |||
| MMGRWE | GRWE | Gross weight of one basic unit | numeric | |||
| MMVOL3 | VOL3 | Volume of one basic unit — with weight, the basis for load and freight math | numeric | |||
| MMRESP | RESP | Responsible — the user accountable for the item's master data | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MITMASon 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.
-- ============================================================
-- Table : MITMAS — The item master — one row per item per company, carrying the item's identity, status, grouping codes, basic unit of measure, and physical attributes; every balance, order line, and stock movement joins back to it on ITNO
-- Purpose: Column-selected read of MITMAS — auto-generated from field metadata
-- Grain : One row per company (CONO) + MMITNO
-- 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
im.MMCONO AS "Company",
im.MMITNO AS "Item number — the natural key every balance, order line, and movement joins on",
im.MMSTAT AS "Item status — a two-char ladder from preliminary through active to deactivated", -- status: decode im.MMSTAT against your configuration — see quirks guide #statuses
im.MMITDS AS "Item name (short description)",
im.MMFUDS AS "Item description (full)",
im.MMITTY AS "Item type — the code that controls how the item behaves across modules",
im.MMITGR AS "Item group — the primary reporting and posting bucket for the item",
im.MMITCL AS "Product group — a second classification slice alongside the item group",
im.MMBUAR AS "Business area — the broadest reporting classification on the item",
im.MMUNMS AS "Basic unit of measure — the unit balances and movements are stored in",
im.MMNEWE AS "Net weight of one basic unit",
im.MMGRWE AS "Gross weight of one basic unit",
im.MMVOL3 AS "Volume of one basic unit — with weight, the basis for load and freight math",
im.MMRESP AS "Responsible — the user accountable for the item's master data"
FROM <catalog>.<schema>.MITMAS im
WHERE
im.MMCONO = <company>
-- AND im.MMITNO = '<ITNO>'
ORDER BY im.MMITNO;4 parameters not filled: <catalog>, <schema>, <company>, <ITNO>
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
ON MITBAL.MBITNO = MITMAS.MMITNO AND MITBAL.MBCONO = MITMAS.MMCONOON MITLOC.MLITNO = MITMAS.MMITNO AND MITLOC.MLCONO = MITMAS.MMCONOON MITTRA.MTITNO = MITMAS.MMITNO AND MITTRA.MTCONO = MITMAS.MMCONOON OOLINE.OBITNO = MITMAS.MMITNO AND OOLINE.OBCONO = MITMAS.MMCONOON MPLINE.IBITNO = MITMAS.MMITNO AND MPLINE.IBCONO = MITMAS.MMCONOON MITFAC.M9ITNO = MITMAS.MMITNO AND MITFAC.M9CONO = MITMAS.MMCONOON MITAUN.MUITNO = MITMAS.MMITNO AND MITAUN.MUCONO = MITMAS.MMCONOON MITPOP.MPITNO = MITMAS.MMITNO AND MITPOP.MPCONO = MITMAS.MMCONOON MILOMA.LMITNO = MITMAS.MMITNO AND MILOMA.LMCONO = MITMAS.MMCONOON MITALO.MQITNO = MITMAS.MMITNO AND MITALO.MQCONO = MITMAS.MMCONOON ODLINE.UBITNO = MITMAS.MMITNO AND ODLINE.UBCONO = MITMAS.MMCONOON MITPLO.MOITNO = MITMAS.MMITNO AND MITPLO.MOCONO = MITMAS.MMCONO
Programs That Use This Table
- MMS001Item master maintenance — where items are created and their MITMAS attributes managedPrimary sourceInteractive
- MMS002Item/warehouse maintenance — connects items to warehouses and manages the MITBAL planning parametersInteractive
- MMS200MIItem API — reads and maintains items and their warehouse connections programmaticallyPrimary sourceAPI