Infor M3 Reference Database
A searchable reference for Infor M3 tables, programs, fields, and relationships. Built for supply chain and analytics practitioners landing M3 data into Databricks from the Infor Data Lake — with a quirks guide for the column prefixes, CONO partitioning, numeric YYYYMMDD dates, two-char status ladders, and CSYTAB code decodes that trip up every first M3 extract.
How this is scoped
- Scope: the supply-chain core — items, inventory, customer orders, and purchasing — plus the generic code-table foundation every module points back to. The catalog spans 32 tables and 14 programs today and is still growing; it leads with the objects an analyst reaches for most, not a full metadata dump.
- Two program kinds: M3 exposes the same data through interactive programs (how functional users name features — MMS001, OIS100) and MI API programs (how integrators reach it — MMS200MI). This reference documents both on one axis, cross-linked, alongside the tables they read and write.
- Verification: field names, keys, and structural facts are curated against Infor documentation; status-ladder values ship only when verified, and every description is original wording. Last verified July 2026.
- Built for analytics: relationships focus on the joins you'll actually write — header/line pairs, shared-alias foreign keys, the CONO equality every cross-table join needs, and the CSYTAB decode hop that trips up every first code lookup.
Frequently Referenced Tables
The workhorses of M3 supply-chain analytics — the item master, warehouse and location balances, the stock ledger, and the customer- and purchase-order pairs.
- MITMASThe 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
- 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
- OOLINEThe customer order line — one row per ordered item with quantities across the ordered/delivered/invoiced flow, price, warehouse, and planned delivery date; the core sell-side transaction, joined to its header by ORNO
- OOHEADThe customer order header — one row per order, carrying the customer, order type, dates, and currency, plus the pair of status fields (lowest and highest line status) that summarize where the order's lines stand
- 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
- MPLINEThe purchase order line — one row per ordered item with quantity, price, planned delivery date, and status; the core buy-side transaction, joined to its header by PUNO
- OCUSMAThe customer master — one row per customer per company, with name and address, country, currency, and the default payment, delivery, and sales-rep terms new orders inherit
- 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
- MPHEADThe purchase order header — one row per order, carrying the supplier, order date, currency, receiving warehouse, and the lowest/highest line status pair mirroring the customer-order pattern
- CIDMASThe supplier master — one row per supplier per company with identity, status, and name; purchasing and supplier-ledger records join back to it on SUNO
Frequently Used Programs
The screens functional users name — and the MI API programs integrators call — behind the order-to-cash and procure-to-pay data.
- OIS100Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pair
- MMS001Item master maintenance — where items are created and their MITMAS attributes managed
- OIS300Customer order overview — the order-book view planners and customer service work from
- PPS200Purchase order maintenance — creates and maintains purchase orders, writing the MPHEAD/MPLINE pair
- MMS200MIItem API — reads and maintains items and their warehouse connections programmatically
- OIS100MICustomer order API — creates, reads, and maintains customer orders programmatically
The M3 quirks guide
The encoding and modeling traps that make a first M3 extract wrong in ways that look right. Each links to a worked Databricks SQL pattern.
Every column is a 2-char table prefix plus a 4-char alias — MMITNO, MBITNO, OBITNO are all ITNO. Join by alias.
The numeric company key on essentially every table — the WHERE anchor, and why you must join on it too.
Company → division → facility → warehouse, and which grain (MITBAL vs MITLOC) answers your on-hand question.
Dates are numbers, 0 means 'no date' — NULL-wrap before MIN/AVG. Entry/change dates sit in server time.
'10'…'99' ladders that vary by order type; order headers carry both the lowest and highest line status.
Hundreds of logical code tables in one physical table, discriminated by STCO — M3's UDC. The decode join.
RGDT / RGTM / LMDT / CHNO / CHID under every prefix — change detection with LMDT + CHNO.
Balances live in the item's basic unit; ordered quantities may not — normalize before comparing.
The universal item key, plus the lot and receipt splits that appear at the MITLOC grain.
Raw landed objects carry every variation plus delete/archive indicators — dedup before analytics.
Getting M3 into your lakehouse
Multi-tenant CloudSuite M3 has no direct database access. The extraction guide covers the supported path — the Infor Data Lake and its Compass SQL platform — the variation metadata landed objects carry, incremental MERGE patterns, and when to land raw tables vs call MI APIs.
Read the extraction guide →Browse by Module
Organized by functional area. Click a module to see its tables and programs.
- Items & Product DataThe item master and the product data every balance, order, and movement points back to4 tables · 2 programsSupply chain
- Inventory & WarehouseWarehouse and location balances, lot records, stock transactions, and the warehouse master6 tables · 1 programsSupply chain
- Customer OrdersCustomer orders from header through line, plus the customer master on the sell side of order-to-cash3 tables · 5 programsSupply chain
- DeliveriesDelivery documents and shipment records between order lines and the customer4 tables · 1 programsSupply chain
- PurchasingPurchase orders and the supplier master across the procure-to-pay cycle3 tables · 3 programsSupply chain
- ManufacturingManufacturing orders, product structures, and routings that define how items are made5 tables · 1 programsSupply chain
- PlanningOrder proposals and planning records that translate demand into planned supply1 tables · 1 programsSupply chain
- FinanceGeneral ledger and subledger records the supply-chain tables post into3 tables · 0 programs
- FoundationThe company/division/facility structure and the generic code tables (CSYTAB) shared by every module3 tables · 0 programs
Sources & further reading
Table structure, program names, and extraction behavior are authoritative only at source. Use these references to verify before building on any claim in this reference.
- Infor Documentation — M3 — the primary documentation portal for Infor M3 and Infor CloudSuite (the source this catalog is verified against).
- Infor Data Fabric — the Data Lake platform M3 publishes its table-shaped data objects to, and the supported extraction path in the cloud.
- Infor Data Fabric User Guide — variation handling — how record variations, delete indicators, and archive indicators behave in landed Data Lake objects.
- Infor Data Fabric User Guide — infor.include table function — the Compass table function for history, deleted, and archived records; the exact signature and record-state semantics the extraction guide quotes.
- Infor Data Fabric — Stream Pipelines (Snowflake destination) — Infor's first-party streaming path out of Data Fabric, with Snowflake as a supported destination; the connector landscape the extraction guide describes.