MTL_MATERIAL_TRANSACTIONS
Historical log of every inventory transaction (receipt, issue, transfer, adjustment) that moved or changed on-hand quantity.
Key Columns
Used In
Related
Item and on-hand data model
EGP_SYSTEM_ITEMS_B is the item master (per item per org). MTL_ONHAND_QUANTITIES_DETAIL is the current snapshot of quantity by subinventory; MTL_MATERIAL_TRANSACTIONS is the full historical log of everything that moved that quantity.
Inventory transaction types
Every row in MTL_MATERIAL_TRANSACTIONS is classified by a predefined type from MTL_TRANSACTION_TYPES — common ones are Miscellaneous Issue/Receipt (manual quantity adjustments not tied to a PO or sales order, typically requiring an account for the offsetting entry), Subinventory Transfer (moving quantity between subinventories/locators within the same org, no accounting impact), and Inter-organization Transfer (moving quantity between orgs, which can be in-transit and does have accounting impact). Shipping and receiving-driven transactions (ship confirm, PO receipt) are generated automatically by those processes rather than entered directly in Inventory.
Work order data model
A work order is identified by WIP_ENTITIES and detailed in WIP_DISCRETE_JOBS (quantities, status). Material issued to or completed from the job is recorded in MTL_MATERIAL_TRANSACTIONS, which is also what Costing reads to value the job.
How Fusion Cost Accounting values inventory transactions
Fusion Cost Accounting is a distinct accounting engine — separate from Subledger Accounting (SLA) — that costs inventory and WIP transactions as they happen: receipts, issues, transfers, and WIP completions. It maintains the current item cost (CST_ITEM_COST_DETAILS) and, under perpetual average/FIFO costing, cost layers (CST_LAYER_COST_DETAILS). Each costed transaction generates its own accounting distribution (CST_AE_HEADERS/CST_AE_LINES) before that entry is transferred to GL, using the same event-driven pattern SLA uses for AP/AR — just in Cost Accounting's own schema.