Infor M3 & CloudSuiteFree referencePDF, Excel, Word exportInfor M3

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.

Download:
TableColumn prefixAreaHoldsKey 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.

Talk to an ExpertExplore More Free Tools

Related Tools

Infor M3 & CloudSuite

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 & CloudSuite

Infor 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 & CloudSuite

Infor 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 & CloudSuite

Infor 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
Back to All Tools