Infor M3 Core Database Tables Reference: Prefixes and Key Fields
Every column in an Infor M3 table starts with the same two letters, which makes joins easy once you know the prefix. This reference lists the core tables a report writer or consultant touches most, with the prefix and the fields that identify a row.
| Table | Column prefix | Area | Holds | Key fields |
|---|---|---|---|---|
MITMAS | MM | Item | Item master, one row per item | MMCONO, MMITNO |
MITBAL | MB | Item | Item balance per warehouse (on hand, allocated, planning values) | MBCONO, MBWHLO, MBITNO |
MITWHL | MW | Warehouse | Warehouse master | MWCONO, MWWHLO |
MITLOC | ML | Item | Balance by location, lot and container | MLCONO, MLWHLO, MLITNO, MLWHSL, MLBANO, MLCAMU, MLREPN |
MITTRA | MT | Item | Stock transaction history | MTCONO plus transaction identifiers; check the table in MDB for your version |
MITFAC | M9 | Item | Item data per facility | M9CONO, M9FACI, M9ITNO |
MITPOP | MP | Item | Item alias and customer or supplier part cross reference | Several; the alias qualifier and alias number identify a row |
CFACIL | CF | Organisation | Facility master | CFCONO, CFFACI |
CMNDIV | CC | Organisation | Division master | CCCONO, CCDIVI |
CMNCMP | CO | Organisation | Company master | COCONO |
CSYTAB | CT | System | General system tables such as codes and constants | CTCONO, CTDIVI, CTSTCO, CTSTKY |
OCUSMA | OK | Customer | Customer master | OKCONO, OKCUNO |
OCUSAD | OP | Customer | Customer address, including ship-to addresses | OPCONO, OPCUNO, OPADRT, OPADID |
OOHEAD | OA | Sales | Customer order header | OACONO, OAORNO |
OOLINE | OB | Sales | Customer order line | OBCONO, OBORNO, OBPONR, OBPOSX |
OOTYPE | OO | Sales | Customer order type settings | OOCONO, OOORTP |
CIDMAS | ID | Supplier | Supplier master | IDCONO, IDSUNO |
MPHEAD | IA | Purchasing | Purchase order header | IACONO, IAPUNO |
MPLINE | IB | Purchasing | Purchase order line | IBCONO, IBPUNO, IBPNLI, IBPNLS |
MWOHED | VH | Production | Manufacturing order header | VHCONO, VHFACI, VHPRNO, VHMFNO |
MWOMAT | VM | Production | Manufacturing order material lines | VMCONO, VMFACI, VMPRNO, VMMFNO, VMMSEQ |
MWOOPE | VO | Production | Manufacturing order operations | VOCONO, VOFACI, VOPRNO, VOMFNO, VOOPNO |
FGLEDG | EG | Finance | General ledger transactions | EGCONO, EGDIVI plus year, journal and sequence fields |
Table names and prefixes follow the M3 naming convention (first two letters of every column match the table). Confirm exact column lists in your own version, for example through the table browser in M3 or the Data Fabric catalog, before building reports.
Ask your M3 data in plain English
Want questions answered from your own M3 tables without writing SQL? We can walk through a read-only ERPray setup.
Optional. The tool and every export work without this. No spam.
How to use this table
Type a table name, a prefix or a word such as 'order' into the search box to filter the list. Use the Key fields column to build joins: a customer order line joins to its header on company and order number, so OOLINE.OBCONO equals OOHEAD.OACONO and OBORNO equals OAORNO. Export the result to Excel to keep a project data dictionary alongside your mapping documents.
- Search by prefix when you only have a column name from a screen or report
- Always include the company number (CONO) in joins, since M3 data is company-scoped
- Use the facility or warehouse columns when the table is facility-specific
Reading the naming convention
The prefix is the table's two-letter code. In MITMAS the item number is MMITNO, in MITBAL the same item number is MBITNO, and in OOLINE it is OBITNO. The part after the prefix is the field name, so ITNO always means item number and WHLO always means warehouse. The companion field glossary on this site decodes the four-letter field names.
Common mistakes
Reading production databases directly can bypass business rules and is not supported in every deployment, particularly in the multi-tenant cloud. Prefer the M3 APIs for transactional reads and writes, and Data Fabric or Data Lake for reporting. A second mistake is forgetting the line suffix: an order line is identified by line number and suffix, so a join on line number alone can duplicate rows.
Frequently Asked Questions
Why do M3 column names start with two letters?
The first two letters are the table prefix, a long-standing M3 convention. It keeps column names unique across tables, so MMITNO is the item number in MITMAS and MBITNO is the item number in MITBAL, which helps when reading joins and logs.
Can I query these tables directly in M3 Cloud?
In multi-tenant cloud you normally work through M3 APIs, Infor OS and Data Lake rather than direct database access. Table and field names still matter because the APIs and Data Fabric objects are built on them.
Is this the complete M3 table list?
No. M3 has thousands of tables. This list covers the core item, order, purchasing, production and finance tables. Use the M3 table documentation for your release to find any others.
Does the prefix change between versions?
The core tables and prefixes have been stable for many releases, but new fields are added over time. Check the table definition in your own environment before you rely on a specific column.
If you want natural-language questions answered directly from your M3 data with the generated query shown and ERP roles respected, ERPray can be set up read-only against M3.
Related Tools
Infor M3 Field Name Glossary
Searchable list of common M3 field codes and what they mean, useful for MI APIs, reports and mapping documents.
Infor M3 & CloudSuiteInfor M3 SQL Query Generator
Fill in company, warehouse and filters to get ready-to-adapt SQL against MITMAS, MITBAL, OOHEAD, OOLINE and MPLINE.
Infor M3 & CloudSuiteInfor M3 Item Planning Parameter Worksheet
Work out safety stock and reorder point for each item and warehouse before loading planning parameters into M3.
Infor M3 & CloudSuiteInfor ION BOD Verbs and Nouns Reference for M3
Look up what each ION BOD verb does, common nouns used with M3, and key ION components in plain language.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- Infor M3 Upgrade Test Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
New to Infor M3? Start with the Infor M3 guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.
Keep exploring
Free tools
- Infor M3 Upgrade Test ChecklistA structured test checklist for an M3 upgrade or update, covering technical checks, core processes, integrations and cut-over.
- Infor M3 AI Assistant Sizing and Value CalculatorSize the GPUs and estimate the monthly value and payback of a private, on-prem AI assistant for Infor M3.
- Infor M3 OOHEAD and OOLINE Customer Order Columns ReferenceColumn-level reference for M3 customer order tables OOHEAD and OOLINE and the delivery tables they join to, with keys, joins and the OIS100MI fields that fill them.
ERP fixes and how-tos
- Private AI Layer for Infor M3 On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor M3 on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Infor M3 Master Data: The Core Objects and the Programs That Maintain ThemInfor M3 master data explained: items, customers, suppliers, product structures and operations, which M3 programs maintain them and which tables hold them.
- Infor M3 Date Format: User Setting, API and DatabaseHow dates work in Infor M3: the user display format in MNS150, the 8-digit YYYYMMDD format used by MI APIs and tables, and how to convert them.
Runs with your ERP
- Infor M3 Scheduling Workbench and M3: finite scheduling explainedHow Infor M3 Scheduling Workbench schedules against capacity and materials and writes orders back to M3 via PSMI, with setup, pitfalls and AI help.
- Infor EDI Managed Service and Infor M3 over IONHow Infor's EDI managed service connects to Infor M3 through ION with pre-built trading partner links: data flows, setup steps, pitfalls and a private AI layer.
- TrueCommerce EDI and Infor M3TrueCommerce managed EDI for Infor M3 (also VISUAL and other Infor ERPs): documents, data flows, setup steps, pitfalls, alternatives and where AI helps.
Guides
- Infor M3 Technical Architecture Explained Layer by LayerInfor M3 technical architecture explained: M3 Business Engine, Infor Grid, database tables, H5 client, and integration layers for on-prem and CloudSuite teams.
- AI Distribution Optimization for Infor M3Optimize Infor M3 distribution with AI. Warehouse automation, order fulfillment optimization, and demand forecasting for distribution-intensive operations.
- Infor M3 Upgrade: Risk Assessment FrameworkAssess risks before upgrading Infor M3. Customization impact analysis, integration compatibility testing, and go/no-go decision framework.
AI on your ERP
- Infor M3 AI: A Practical Path from MI Programs to a Private AssistantInfor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
- Infor M3 Supply Chain Planning With AI That Explains the MRP OutputAI for Infor M3 supply chain planning: explain MRP action messages, review planned orders, and trace shortages through MITBAL and MITMAS on private infrastructure.
Integrations
- How to use ChatGPT with Infor M3How to use ChatGPT with Infor M3: exports, custom GPT actions over the M3 API or ION, enterprise data controls, and when a private model is the safer choice.
- How to connect Power BI to Infor M3How to connect Power BI to Infor M3: Data Lake and Compass, direct database, or API options, on-prem gateway, key manufacturing dashboards, and natural-language Q&A.