M3 Reference
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 what a first extract gets wrong.
Free & ungated · Last verified September 2026
33
Tables
36
Programs
9
Modules
11
Quirks
How this is scoped
- Scope: the supply-chain core through to the finance ledgers it posts into — items, inventory, customer orders, deliveries, purchasing, manufacturing, planning, and finance — plus the generic code-table foundation every module points back to. The catalog spans 33 tables and 36 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 September 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 the lowest/highest line-status pair; 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.
Read all 11 quirksGetting 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 guideBrowse 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 · 3 programsSupply chain
- Inventory & WarehouseWarehouse and location balances, lot records, stock transactions, and the warehouse master6 tables · 5 programsSupply chain
- Customer OrdersCustomer orders from header through line, plus the customer master on the sell side of order-to-cash3 tables · 7 programsSupply chain
- DeliveriesDelivery documents and shipment records between order lines and the customer4 tables · 3 programsSupply chain
- PurchasingPurchase orders and the supplier master across the procure-to-pay cycle4 tables · 7 programsSupply chain
- ManufacturingManufacturing orders, product structures, and routings that define how items are made5 tables · 4 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 · 3 programs
- FoundationThe company/division/facility structure and the generic code tables (CSYTAB) shared by every module3 tables · 3 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.
Show all 26 sources, graded by group
Infor official
- Infor Documentation — M3 (opens in new tab) — the primary documentation portal for Infor M3 and Infor CloudSuite (the source this catalog is verified against).
- Infor Data Fabric (opens in new tab) — 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 (opens in new tab) — how record variations, delete indicators, and archive indicators behave in landed Data Lake objects.
- Infor Data Fabric User Guide — infor.include table function (opens in new tab) — 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, supported destinations (opens in new tab) — the canonical destination list for Infor's first-party streaming path (an add-on license to Data Fabric): Snowflake, PostgreSQL and SQL Server engines, not Databricks; the connector landscape the extraction guide describes.
- Infor Data Fabric — Stream Pipelines, PostgreSQL destination (opens in new tab) — the destination page documenting PostgreSQL as a first-party Stream Pipelines target; why the extraction guide no longer describes the streaming path as Snowflake-only.
- Infor Data Fabric — Compass query processing (opens in new tab) — the overview of Compass's two query processing modes (transactional and analytical), which decide whether record-level deduplication happens during conversion.
- Infor Data Fabric — Compass transactional mode (opens in new tab) — the mode page stating that no record-level deduplication is applied and duplicate versions are returned directly in query results; the source behind the mode qualification in the extraction and quirks guides.
- Infor Data Fabric — Compass analytical mode (opens in new tab) — the mode page documenting the deduplicating conversion that yields Compass's consolidated current-state view.
- Infor Data Fabric — Configuring Compass query processing modes (opens in new tab) — the per-object Mode Configuration panel, and the decisive detail: when the switch is off, transactional (non-deduplicating) mode is used.
- M3 — Data Lake Publisher administration tasks (opens in new tab) — the M3-side half of the extraction story: per-table publishing subscriptions, the initial-load step for pre-subscription history, and the admin role that manages them.
- M3 BE — Status: Customer Order Line (opens in new tab) — the customer order line status ladder: the two-numeral encoding, the digit meanings, and the combination table. The source behind the line-status decode and the two-numeral rule in the quirks guide.
- M3 BE — Status: Customer Order (header) (opens in new tab) — the customer order header status ladder: the header-only rungs (00/20/90) and the lowest/highest pair reflecting the order's lines; the provenance behind the header-pair decode.
- M3 BE — Item Status (opens in new tab) — the ten-value item lifecycle ladder on MITMAS.MMSTAT, including the discontinued-but-still-transactable distinction between 80 and 90.
- M3 BE — Purchase Order (opens in new tab) — the purchase-order structure: the entry rungs (12/15/20) of the line-status (PUST) decode, and the source for the highest/lowest status pair carried by both the order header and each order line.
- M3 BE — Goods Receiving Flow for Purchase Orders (opens in new tab) — the receipt, inspection, and put-away rungs (50–75) of the purchase-order line-status (PUST) decode.
- M3 BE — Create, Release, and Display Purchase Order (opens in new tab) — independent corroboration for rungs 15 ('Ready for printout') and 20 ('Document printed') of the purchase-order line-status (PUST) decode.
- M3 BE — Dispatch Handling (opens in new tab) — the delivery flow behind MHDISH: the direction-scoped progress-status ladder, the packing-status ladder, and MITALO's role as the picking line.
- M3 BE — Create Agreements with Supplier (opens in new tab) — the purchase-agreement flow: PPS100 as the maintenance program, the MPAGRH/MPAGRL/MPAGRP file set, and PPS535's role as the print report.
- M3 BE — Display Stock Transaction History (MWS070) (opens in new tab) — the program behind the MITTRA pairing: all physical stock transactions are stored in MITTRA, displayed through MWS070.
- M3 BE — Display Item per Location (opens in new tab) — the published statement that 'Balance Identity. Display' (MMS060) reads the MITLOC file; the citation behind the MMS060 → MITLOC pairing.
- M3 BE — Stock and Inventory Information (opens in new tab) — Infor's statement of the whole balance-grain ladder (MITFAC per facility, MITBAL per warehouse, MITLOC per location, MILOMA per lot) and the programs at each level, including MWS068 over the item's locations.
- M3 BE — Material Plan (MMS080) (opens in new tab) — the material-plan view over MITPLO, and the source naming MMS060 and MWS068 as the balance-identity displays.
- Infor M3 Cross-BOD mapping (2023) (opens in new tab) — an Infor-published integration mapping that prints literal TABLE.FIELD names; the corroboration behind many field prefixes and MI transaction lists in this catalog.
Third-party / partner
- Databricks — Infor Nexus & Databricks (opens in new tab) — the scope of Infor's first-party Databricks integration to date: Infor Nexus network data over Delta Sharing (June 2025), not M3 ERP tables; the evidence behind the extraction guide's connector claim.
- Omnata — Infor Data Lake connector (opens in new tab) — partner-connector evidence for the extraction guide's path (c), and an independent freshness signal on the Compass JDBC driver version.