M3 Reference
All Infor M3 Tables
Every table in the reference, sorted alphabetically. Use the jump-bar to skip to a letter, or filter by module, data class, and company partition.
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide). - master
- Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
- Shared across companies
- The table carries no
CONO— rows aren’t partitioned per company (see the quirks guide). - Division-level
- The table carries
DIVI— rows are scoped below company to a division, one layer more granular thanCONOalone (see the quirks guide).
In field listings, K marks a primary-key field.
FilterShowing 33 of 33 tables
Module
Tables starting with C
- CFACILThe facility master — one row per facility (the costing/manufacturing level between division and warehouse), with its name and division; warehouses and orders reference it by FACIPrefix: CFmasterfoundation
- CIDMASThe supplier master — one row per supplier per company with identity, status, and name; purchasing and supplier-ledger records join back to it on SUNOPrefix: IDmasterpurchasing
- CMNDIVThe division master — one row per division within a company; the DIVI that financial and divisional tables carry resolves herePrefix: CCmasterfoundation
- CSYTABThe generic system code table — hundreds of logical code tables share this one physical table, separated by the STCO constant; a code field elsewhere decodes here by matching its value against STKY under the right STCO (M3's analog of JDE's UDC table)Prefix: CTcodesfoundation
Tables starting with F
- FGLEDGThe general ledger — one row per voucher line, with the accounting date, accounting-dimension string, and amounts; the voucher is identified by division, fiscal year, voucher series, and voucher number, and carries one or more lines below that key; every subledger posting lands herePrefix: EGtransactionfinance
- FPLEDGThe accounts payable ledger — one row per supplier invoice or payment transaction, mirroring the receivable ledger on the payable side; its voucher (division, fiscal year, series, number) can carry more than one such row, and joins it to the general ledgerPrefix: EPtransactionfinance
- FSLEDGThe accounts receivable ledger — one row per customer invoice or payment transaction, carrying the payer, invoice number, due date, and amount; its voucher (division, fiscal year, series, number) can carry more than one such row, and joins it to the general ledgerPrefix: EStransactionfinance
Tables starting with M
- MHDISHThe delivery header — one row per delivery (inbound or outbound, discriminated by INOU) identified by the delivery index DLIX, carrying the warehouse and the shipment it rides on; the unit picking and dispatch work against. DLIX is scoped by direction — inbound and outbound deliveries share the number space, so the key is CONO + INOU + DLIX, and a join from an order table that carries no direction column matches on DLIX alonePrefix: OQtransactiondeliveries
- MHDISLThe delivery line — one row per order line placed on a delivery, keyed by the delivery index and the order reference; the quantity actually moving on this delivery, joined to its header by DLIXPrefix: URtransactiondeliveries
- MILOMAThe lot master — one row per item and lot (batch) number, carrying the lot's identity and life-cycle dates; location balances and allocations reference it by BANOPrefix: LMmasterinventory
- MITALOAllocations — one row per item, location, and lot allocated to a specific order line, connecting demand (the order reference) to the exact stock that will fill it; the bridge between order lines and MITLOC balancesPrefix: MQtransactioninventory
- MITAUNAlternate units of measure — one row per item, unit type, and alternate unit, carrying the conversion factor between the alternate unit and the item's basic unit; the table that answers 'how many eaches in a case'Prefix: MUmasteritems
- 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 balancesPrefix: MBbalanceinventory
- MITFACThe item/facility record — one row per item and facility, where costing lives; the approved cost the facility values the item at sits here, between the company-wide item master and the warehouse-level balancesPrefix: M9masteritems
- 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 rowsPrefix: MLbalanceinventory
- 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 ITNOPrefix: MMmasteritems
- MITPLOThe material plan — one row per planned transaction (demand or supply) per item and warehouse, ordered by planning date; the table behind M3's material plan view and the starting point for supply/demand pegging analysisPrefix: MOtransactionplanning
- MITPOPItem aliases — one row per alias type, qualifier, and alias number, mapping external identities (customer or supplier item numbers, barcodes) to the internal ITNO; the lookup behind alias-based item searchPrefix: MPmasteritems
- 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 itPrefix: MTtransactioninventory
- MITWHLThe warehouse master — one row per warehouse with its name, facility, and warehouse type; the WHLO every balance and movement carries resolves herePrefix: MWmasterinventory
- MPAGRHThe purchase agreement header — one row per supplier purchase agreement (agreement number), the negotiated terms record purchase-order pricing draws fromPrefix: AHmasterpurchasing
- MPDHEDThe product structure header — one row per product and structure type per facility, the design-time recipe that manufacturing orders are created fromPrefix: PHmastermanufacturing
- MPDMATProduct structure materials — one row per component in a product structure, with the quantity consumed per unit produced; the design-time counterpart of MWOMAT, joined to its header by PRNO + STRTPrefix: PMmastermanufacturing
- 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 patternPrefix: IAtransactionpurchasing
- 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 PUNOPrefix: IBtransactionpurchasing
- MWOHEDThe manufacturing order header — one row per order, carrying the product being made, its status ladder, ordered and completed quantities, and start/finish dates; the manufactured product number joins to the item master on ITNOPrefix: VHtransactionmanufacturing
- MWOMATManufacturing order materials — one row per component line on an order, with required and reported quantities; copied from the product structure at order creation and then consumed against, joined to its header by MFNOPrefix: VMtransactionmanufacturing
- MWOOPEManufacturing order operations — one row per operation step on an order with its work center; the grain for capacity and labor reporting, joined to its header by MFNOPrefix: VOtransactionmanufacturing
Tables starting with O
- 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 inheritPrefix: OKmastersales
- ODHEADThe invoiced-delivery header — one row per delivered and invoiced customer order delivery, carrying the invoice number and date, payer, and currency; the payment term is part of its key, so one delivery can settle under more than one term; it carries no direction column, so its DLIX join to MHDISH matches on the delivery index alonePrefix: UAtransactiondeliveries
- ODLINEThe invoiced-delivery line — one row per invoiced order line per delivery, with the invoiced quantity and price; the revenue-at-line grain of order-to-cash analytics, joined to its header by ORNO + DLIX + payment termPrefix: UBtransactiondeliveries
- 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 standPrefix: OAtransactionsales
- 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 ORNOPrefix: OBtransactionsales