# Infor M3 Allocation Table: MITALO Reference and Queries > Source: https://netray.co/erp-help/infor-m3-allocation-table-mitalo-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer M3 records material and stock allocations in the allocation table, MITALO, one row per allocation of an item to a demand such as a customer order line or a manufacturing order material line. The allocated total is also summarised on the item-warehouse balance, which is why the two can disagree when something goes wrong. ## Kind advanced ## System infor-m3 ## Erp Infor M3 ## Module Inventory / Allocation (MITALO) ## Query infor m3 allocation table ## Alternate Queries - allocation table infor m3 - m3 MITALO table - m3 which table holds allocations - m3 allocated quantity item balance ## Applies To Infor M3 Business Engine, on-prem database access or Data Fabric / reporting replicas. Column details vary by release, so confirm in your data dictionary. ## Steps ### Investigate allocations for an item **Items:** - Identify the item and warehouse in question, and the demand (order number and line) if you have it. - Look at the allocation in the application first: open the demand line (customer order line, MO material line, or similar) and display the allocation or reservation information from it. - For a database-level view, query MITALO filtered by company, warehouse and item number, and read the reference order category, order number and line columns to see what each row serves. - Compare the sum of allocated quantity in MITALO to the allocated quantity on the item-warehouse balance. A difference points to a stuck or orphaned allocation. - Check the demand document status. An allocation against a cancelled or fully delivered line should not exist. - Use the standard re-allocation or deallocation function on the demand, not a direct update to MITALO. - Re-run the comparison after the fix. ## Sections ### What MITALO represents **Body:** MITALO is the detail behind the allocated quantity you see on an item balance. Each row ties a quantity of an item in a warehouse (and, depending on settings, a lot, location or container) to a reference order: a customer order line, a distribution order, or a material line on a manufacturing order. The reference fields, order category, order number, line and sub-line, are how you join it back to the demand. Because it is per demand line, it is the right table to answer which orders have a claim on this stock, and which order is blocking a shortage. ### Query pattern **Body:** Treat the SQL below as a pattern. Table and column names differ across M3 releases and database platforms, and the schema qualifier depends on your install. Use read-only access to a replica or reporting copy, never update M3 tables directly. Group by the reference order category first to see where demand is coming from, then drill into one category. **Code:** - -- Pattern only: confirm column names in your data dictionary - SELECT MQCONO, MQWHLO, MQITNO, MQRORC, MQRIDN, MQRIDL, MQALQT - FROM MITALO - WHERE MQCONO = 100 AND MQWHLO = 'A01' AND MQITNO = 'ITEM-123' - ORDER BY MQRORC, MQRIDN, MQRIDL; ### Why allocated quantities disagree **Body:** Common causes are an order cancelled or changed through an interface that skipped the standard deallocation, an interrupted batch allocation job, a manual stock correction made while allocations existed, and customizations that touch the balance fields. Fix these through the application: deallocate and reallocate from the demand line, or run the standard balance reconciliation functions that your M3 version offers. Direct database changes bypass M3 business rules and are not supportable. ## Pitfalls - Updating MITALO or the balance directly in SQL. It bypasses business logic and can corrupt planning. - Querying without company and warehouse and summing across different scopes. - Assuming every allocation row is a hard reservation. Settings decide how and when allocation happens. - Copying column names from another release without checking them. - Ignoring lot and location allocation, which multiply rows per demand line. ## Ai Angle This is a good question for a read-only data assistant: which orders hold the allocation on this item, and does it match the balance. ERPray-style querying over a replica shows the SQL, so the planner can verify it. Netray can host that on-prem next to the M3 database so no inventory data leaves your site. ## Faq ### Which M3 table holds the allocations? **Answer:** MITALO, the allocation table. The summarised allocated quantity sits on the item-warehouse balance (MITBAL), and location level stock is in MITLOC. ### Can I delete rows from MITALO to free stock? **Answer:** No. Use the application function to deallocate from the demand line. Direct deletes skip the balance updates and can leave the system inconsistent. ### Why is allocated quantity higher than on-hand? **Answer:** Allocations can exist against expected receipts or be left over from a cancelled order. Compare each allocation's demand status and check the source of the stock being allocated. ## Search terms infor m3 allocation table, allocation table infor m3, m3 MITALO, m3 allocated quantity, m3 MITBAL allocated, infor m3 inventory allocation, m3 deallocate order, m3 sql allocation query --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json