# Infor M3 Core Database Tables Reference: Prefixes and Key Fields

> Source: https://netray.co/tools/infor-m3-core-database-tables-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Look up the main M3 tables, their two-letter column prefix and the key fields you join on. Searchable and exportable.

## Category

infor-cloudsuite

## Erp

Infor M3

## Audience

- M3 consultant
- M3 developer
- Report writer

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Column prefix

**Key:** prefix

**Type:** text

#### Area

**Key:** area

**Type:** text

#### Holds

**Key:** description

**Type:** text

#### Key fields

**Key:** keys

**Type:** text

**Rows:**

**Table:** MITMAS

**Prefix:** MM

**Area:** Item

**Description:** Item master, one row per item

**Keys:** MMCONO, MMITNO

**Table:** MITBAL

**Prefix:** MB

**Area:** Item

**Description:** Item balance per warehouse (on hand, allocated, planning values)

**Keys:** MBCONO, MBWHLO, MBITNO

**Table:** MITWHL

**Prefix:** MW

**Area:** Warehouse

**Description:** Warehouse master

**Keys:** MWCONO, MWWHLO

**Table:** MITLOC

**Prefix:** ML

**Area:** Item

**Description:** Balance by location, lot and container

**Keys:** MLCONO, MLWHLO, MLITNO, MLWHSL, MLBANO, MLCAMU, MLREPN

**Table:** MITTRA

**Prefix:** MT

**Area:** Item

**Description:** Stock transaction history

**Keys:** MTCONO plus transaction identifiers; check the table in MDB for your version

**Table:** MITFAC

**Prefix:** M9

**Area:** Item

**Description:** Item data per facility

**Keys:** M9CONO, M9FACI, M9ITNO

**Table:** MITPOP

**Prefix:** MP

**Area:** Item

**Description:** Item alias and customer or supplier part cross reference

**Keys:** Several; the alias qualifier and alias number identify a row

**Table:** CFACIL

**Prefix:** CF

**Area:** Organisation

**Description:** Facility master

**Keys:** CFCONO, CFFACI

**Table:** CMNDIV

**Prefix:** CC

**Area:** Organisation

**Description:** Division master

**Keys:** CCCONO, CCDIVI

**Table:** CMNCMP

**Prefix:** CO

**Area:** Organisation

**Description:** Company master

**Keys:** COCONO

**Table:** CSYTAB

**Prefix:** CT

**Area:** System

**Description:** General system tables such as codes and constants

**Keys:** CTCONO, CTDIVI, CTSTCO, CTSTKY

**Table:** OCUSMA

**Prefix:** OK

**Area:** Customer

**Description:** Customer master

**Keys:** OKCONO, OKCUNO

**Table:** OCUSAD

**Prefix:** OP

**Area:** Customer

**Description:** Customer address, including ship-to addresses

**Keys:** OPCONO, OPCUNO, OPADRT, OPADID

**Table:** OOHEAD

**Prefix:** OA

**Area:** Sales

**Description:** Customer order header

**Keys:** OACONO, OAORNO

**Table:** OOLINE

**Prefix:** OB

**Area:** Sales

**Description:** Customer order line

**Keys:** OBCONO, OBORNO, OBPONR, OBPOSX

**Table:** OOTYPE

**Prefix:** OO

**Area:** Sales

**Description:** Customer order type settings

**Keys:** OOCONO, OOORTP

**Table:** CIDMAS

**Prefix:** ID

**Area:** Supplier

**Description:** Supplier master

**Keys:** IDCONO, IDSUNO

**Table:** MPHEAD

**Prefix:** IA

**Area:** Purchasing

**Description:** Purchase order header

**Keys:** IACONO, IAPUNO

**Table:** MPLINE

**Prefix:** IB

**Area:** Purchasing

**Description:** Purchase order line

**Keys:** IBCONO, IBPUNO, IBPNLI, IBPNLS

**Table:** MWOHED

**Prefix:** VH

**Area:** Production

**Description:** Manufacturing order header

**Keys:** VHCONO, VHFACI, VHPRNO, VHMFNO

**Table:** MWOMAT

**Prefix:** VM

**Area:** Production

**Description:** Manufacturing order material lines

**Keys:** VMCONO, VMFACI, VMPRNO, VMMFNO, VMMSEQ

**Table:** MWOOPE

**Prefix:** VO

**Area:** Production

**Description:** Manufacturing order operations

**Keys:** VOCONO, VOFACI, VOPRNO, VOMFNO, VOOPNO

**Table:** FGLEDG

**Prefix:** EG

**Area:** Finance

**Description:** General ledger transactions

**Keys:** EGCONO, EGDIVI plus year, journal and sequence fields

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use this table

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Why do M3 column names start with two letters?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

infor m3 tables, m3 mitmas fields, m3 ooline table, m3 database table list, m3 column prefix, infor m3 data model, m3 mitbal columns, m3 sql join tables

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json