# Infor M3 Inventory and Allocation Tables: MITBAL, MITLOC, MITALO, MITTRA > Source: https://netray.co/tools/infor-m3-inventory-tables-mitbal-mitloc-mitalo-mittra-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Column-level reference for M3 stock, balance identity, allocation, material plan and transaction tables, with keys, joins and the programs that maintain them. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 report developer - M3 supply chain consultant - Data analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Column **Key:** column **Type:** text #### Description **Key:** desc **Type:** text #### Key **Key:** key **Type:** text #### Join to **Key:** join **Type:** text #### Maintained by program **Key:** program **Type:** text #### Notes **Key:** notes **Type:** text **Rows:** **Table:** MITMAS **Column:** MMITNO **Desc:** Item number (item master) **Key:** PK with MMCONO **Join:** All tables below on ITNO **Program:** MMS001 **Notes:** Link only; use for item name, type, basic U/M **Table:** MITWHL **Column:** MWWHLO **Desc:** Warehouse **Key:** PK with MWCONO **Join:** MITBAL.MBWHLO **Program:** MMS005 **Table:** MITWHL **Column:** MWWHNM **Desc:** Warehouse name **Key:** - **Join:** - **Program:** MMS005 **Table:** MITWHL **Column:** MWFACI **Desc:** Facility of the warehouse **Key:** - **Join:** CFACIL **Program:** MMS005 **Table:** MITBAL **Column:** MBWHLO / MBITNO **Desc:** Warehouse / item **Key:** PK with MBCONO **Join:** MITLOC, MITALO, MITPLO on WHLO and ITNO **Program:** MMS002 **Notes:** One row per item and warehouse **Table:** MITBAL **Column:** MBSTQT **Desc:** On-hand balance **Key:** - **Join:** - **Program:** Updated by transactions **Notes:** Sum of the warehouse; detail is in MITLOC **Table:** MITBAL **Column:** MBALQT **Desc:** Allocated quantity **Key:** - **Join:** - **Program:** Updated by allocation **Notes:** Should equal the sum of MLALQT for the item and warehouse **Table:** MITBAL **Column:** MBREOP **Desc:** Reorder point **Key:** - **Join:** - **Program:** MMS002 **Table:** MITBAL **Column:** MBSSQT **Desc:** Safety stock **Key:** - **Join:** - **Program:** MMS002 **Table:** MITBAL **Column:** MBWHSL **Desc:** Default location **Key:** - **Join:** MITPCE.MSWHSL **Program:** MMS002 **Table:** MITBAL **Column:** MBSTAT **Desc:** Item / warehouse status **Key:** - **Join:** - **Program:** MMS002 **Table:** MITLOC **Column:** MLWHLO / MLITNO **Desc:** Warehouse / item **Key:** PK part **Join:** MITBAL **Program:** MMS060 **Notes:** One row per balance identity **Table:** MITLOC **Column:** MLWHSL **Desc:** Location **Key:** PK part **Join:** MITPCE.MSWHSL **Program:** MMS060 **Table:** MITLOC **Column:** MLBANO **Desc:** Lot number **Key:** PK part **Join:** MILOMA.LMBANO **Program:** MMS060 **Notes:** Blank for items without lot control **Table:** MITLOC **Column:** MLCAMU **Desc:** Container **Key:** PK part **Join:** - **Program:** MMS060 **Table:** MITLOC **Column:** MLREPN **Desc:** Receiving number **Key:** PK part **Join:** MITTRA **Program:** MMS060 **Table:** MITLOC **Column:** MLSTQT **Desc:** On-hand balance for the balance ID **Key:** - **Join:** - **Program:** Updated by transactions **Table:** MITLOC **Column:** MLALQT **Desc:** Allocated quantity for the balance ID **Key:** - **Join:** - **Program:** Updated by allocation **Notes:** Available on a balance ID = MLSTQT - MLALQT if its status allows allocation **Table:** MITLOC **Column:** MLSTAS **Desc:** Balance ID status **Key:** - **Join:** - **Program:** MMS060 **Notes:** Only approved stock is normally allocatable **Table:** MITALO **Column:** MQWHLO / MQITNO **Desc:** Warehouse / item **Key:** Key part **Join:** MITBAL **Program:** Allocation **Notes:** One row per allocation of a balance ID to an order line **Table:** MITALO **Column:** MQTTYP **Desc:** Transaction type of the demand **Key:** Key part **Join:** - **Program:** Allocation **Notes:** Same numbering as MITTRA, for example 31 for customer order **Table:** MITALO **Column:** MQRIDN / MQRIDL **Desc:** Order number / order line **Key:** Key part **Join:** OOLINE.OBORNO / OBPONR when MQTTYP is 31 **Program:** Allocation **Table:** MITALO **Column:** MQWHSL / MQBANO **Desc:** Allocated location / lot **Key:** - **Join:** MITLOC **Program:** Allocation **Notes:** Ties the allocation to a balance ID **Table:** MITALO **Column:** MQALQT **Desc:** Allocated quantity **Key:** - **Join:** - **Program:** Allocation **Table:** MITPLO **Column:** MOWHLO / MOITNO **Desc:** Warehouse / item **Key:** Key part **Join:** MITBAL **Program:** MMS080 Material Plan **Notes:** Planned supply and demand lines **Table:** MITPLO **Column:** MOPLDT **Desc:** Planning date **Key:** Key part **Join:** - **Program:** MMS080 **Table:** MITPLO **Column:** MOORCA **Desc:** Order category **Key:** - **Join:** - **Program:** MMS080 **Notes:** Tells which order type created the line **Table:** MITPLO **Column:** MORIDN / MORIDL **Desc:** Order number / line **Key:** - **Join:** Order tables **Program:** MMS080 **Table:** MITPLO **Column:** MOTRQT **Desc:** Transaction quantity **Key:** - **Join:** - **Program:** MMS080 **Notes:** Positive supply, negative demand **Table:** MITTRA **Column:** MTWHLO / MTITNO **Desc:** Warehouse / item **Key:** Key part **Join:** MITBAL **Program:** Every stock transaction **Notes:** Stock transaction history **Table:** MITTRA **Column:** MTTRDT **Desc:** Transaction date (YYYYMMDD) **Key:** Key part **Join:** - **Program:** Every stock transaction **Notes:** Filter by date range; the table is large **Table:** MITTRA **Column:** MTTTYP **Desc:** Transaction type **Key:** - **Join:** - **Program:** Every stock transaction **Notes:** For example 10 MO receipt, 11 MO issue, 25 PO receipt, 31 CO issue; read the full list in the field help for your release **Table:** MITTRA **Column:** MTTRQT **Desc:** Transaction quantity **Key:** - **Join:** - **Program:** Every stock transaction **Notes:** Signed: issues negative, receipts positive **Table:** MITTRA **Column:** MTRIDN / MTRIDL **Desc:** Reference order number / line **Key:** - **Join:** OOLINE, MPLINE, MWOHED by type **Program:** Every stock transaction **Table:** MITTRA **Column:** MTWHSL / MTBANO **Desc:** Location / lot **Key:** - **Join:** MITLOC **Program:** Every stock transaction **Table:** MILOMA **Column:** LMITNO / LMBANO **Desc:** Item / lot number **Key:** PK with LMCONO **Join:** MITLOC.MLITNO / MLBANO **Program:** MMS235 **Notes:** Lot master, shared across warehouses **Table:** MILOMA **Column:** LMEXPI **Desc:** Expiration date **Key:** - **Join:** - **Program:** MMS235 **Notes:** Used in FEFO allocation **Table:** MITPCE **Column:** MSWHLO / MSWHSL **Desc:** Warehouse / stock location **Key:** PK with MSCONO **Join:** MITLOC.MLWHSL **Program:** MMS010 **Table:** MITPCE **Column:** MSSLTP **Desc:** Stock zone **Key:** - **Join:** - **Program:** MMS010 **Notes:** Column names follow the M3 convention of a two-letter table prefix plus the field name (MB for MITBAL, ML for MITLOC, MQ for MITALO, MO for MITPLO, MT for MITTRA). Confirm each column and the transaction type list in M3 Metadata Publisher (MDP) and field help for your 13.x release. ## Content **Intro:** This reference covers the M3 13.x tables behind stock and allocation: MITBAL for item and warehouse balances, MITLOC for balance identities, MITALO for allocations, MITPLO for the material plan and MITTRA for stock transactions, with lot, warehouse and location masters. It lists the key columns, joins and maintaining programs. **Sections:** #### How to use it **Body:** Search by table, column or concept (allocated, lot, location). Read the tables top down: MITBAL gives one row per item and warehouse with totals, MITLOC breaks that into balance identities (location, lot, container, receiving number), MITALO shows which balance IDs are allocated to which order lines, MITPLO is the time-phased material plan, and MITTRA is the history of every movement. The Notes column explains how quantities relate, which is where most report errors come from. #### Where this lives in M3 **Body:** MMS002 maintains item and warehouse data (MITBAL), MMS060 shows balance identities (MITLOC), MMS080 is the material plan (MITPLO), MMS010 stock locations (MITPCE), MMS005 warehouses (MITWHL) and MMS235 lots (MILOMA). Allocation, automatic or manual, writes MITALO. Stock transactions from receipts, issues, counts and moves land in MITTRA; transactions from a WMS arrive through MHS850MI or MMS850MI and land in MITTRA once processed. **Bullets:** - MBSTQT is the sum of MLSTQT for the item and warehouse - MBALQT matches the sum of MLALQT and of MQALQT - MITALO links allocations to order lines via TTYP, RIDN, RIDL - MITTRA grows fast; always filter on date #### Worked example: why is stock not available? **Body:** A planner sees 500 on hand for an item in warehouse 100 but cannot allocate. MITBAL shows MBSTQT 500 and MBALQT 300. MITLOC shows three balance IDs: one with 300 fully allocated (MLALQT 300), and two with 100 each where MLSTAS is not approved, so they cannot be allocated. MITALO rows with MQTTYP 31 show which customer order lines hold the 300. The fix is quality approval of the two lots, not a stock adjustment. #### Version differences and gotchas **Body:** Do not read available stock from MITBAL alone; balance ID status, lot expiry and allocation rules decide what is allocatable. Transaction quantities in MITTRA are signed, so sum them as they are. Lot masters (MILOMA) are not per warehouse. Some columns are added between 13.x releases, so confirm in MDP. For writes, use MMS850MI, MHS850MI or the programs, never direct SQL. **Cta:** If you want planners to ask M3 why stock is not available in plain English on your own servers, we can build that on these tables with read-only access. **Faq:** #### What is the M3 allocation table? **Answer:** MITALO holds allocations: each row links a balance identity (warehouse, location, lot) to a demand line identified by transaction type, order number and line, with the allocated quantity. MITBAL.MBALQT and MITLOC.MLALQT hold the totals. #### What is the difference between MITBAL and MITLOC? **Answer:** MITBAL has one row per item and warehouse with total on-hand and allocated quantities and planning parameters. MITLOC has one row per balance identity, meaning location, lot, container and receiving number, with the quantities at that level. Totals in MITBAL equal the sum of MITLOC rows. #### Where are stock transactions stored in M3? **Answer:** MITTRA stores every stock transaction with warehouse, item, date, transaction type, signed quantity and the reference order. Transaction types use M3 numbering, for example 31 for customer order issues and 25 for purchase order receipts. #### How do I get a list of M3 database tables? **Answer:** M3 Metadata Publisher (MDP) lists every table, column and index for your release. For an overview of the main tables by area see the M3 core database tables reference; this page goes to column level for inventory and allocation. ## Search terms infor m3 allocation table, infor m3 database tables, infor m3 table list, m3 mitbal, m3 mitloc, m3 mittra, m3 mitalo allocation --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json