INV Material Transactions
Description:
Detail report of Inventory transactions with item, primary qty, secondary qty, transaction type, transaction ID and total transaction qty
Parameters
Operating Unit, Organization Code, Subinventory, Item, Item Description, Category Set 1, Category Set 2, Category Set 3, Transaction within Days, Transaction Date From, Transaction Date To, Source Type, Exclude Source Type, Action, Exclude Action, Transaction Type, Supplier, Project, Show Lots, Exclude Transaction Type, Created By, Exclude Logical Transactions
Used tables
gl_periods, mtl_item_locations_kfv, gl_ledgers, hr_all_organization_units_vl, org_organization_definitions, mtl_material_transactions, mtl_transaction_types, mtl_txn_source_types, mtl_system_items_vl, mtl_parameters, hz_locations, mtl_transaction_reasons, mtl_generic_dispositions, mtl_sales_orders, cst_cost_updates, mtl_cycle_count_headers, gl_code_combinations_kfv, mtl_physical_inventories, po_headers_all, ap_suppliers, okc_k_headers_all_b, po_requisition_headers_all, wip_entities, mtl_txn_request_headers, mtl_transaction_lot_numbers, pa_projects_all, pa_tasks, org_access_view
Categories
Dependencies
If you would like to try one of these Oracle EBS SQLs without having Blitz Report installed, note that some of the reports require functions from utility package xxen_util.
Example Report
INV Material Transactions 24-Jul-2017 143718.xlsx
Report SQL
www.enginatics.com/reports/inv-material-transactions/
Blitz Report™ import options
Case Study & Technical Analysis: INV Material Transactions
Executive Summary
The INV Material Transactions report is the definitive audit trail for all inventory movements within the Oracle E-Business Suite. It captures every receipt, issue, transfer, and adjustment, providing a granular history of stock activity. This report is indispensable for Warehouse Managers, Cost Accountants, and Auditors to ensure inventory accuracy, investigate variances, and maintain compliance.
Business Challenge
Inventory is often the largest asset on a company’s balance sheet, yet it is prone to errors.
- Loss of Control: Without detailed tracking, it is impossible to know who moved stock, when it moved, and where it went.
- Reconciliation Nightmares: When physical counts don’t match system records, finding the discrepancy requires digging through thousands of transactions.
- Compliance Risks: For regulated industries, tracing the history of a specific Lot or Serial number is a legal requirement.
The Solution
This report provides a powerful search engine for the MTL_MATERIAL_TRANSACTIONS table, offering a complete Operational View of material flow.
- Root Cause Analysis: Users can filter by specific items or transaction types (e.g., “Account Alias Issue”) to identify process gaps or theft.
- Audit Readiness: It provides a complete lineage for any item, showing the exact time, user, and reference document (e.g., PO or Sales Order) for every move.
- Cost Visibility: It often includes transaction costs, helping cost accountants validate the value of inventory updates.
Technical Architecture (High Level)
The report queries the core inventory transaction history table, which is typically one of the largest tables in an Oracle EBS database.
- Primary Tables:
MTL_MATERIAL_TRANSACTIONS(MMT): The massive header table containing all transaction data.MTL_SYSTEM_ITEMS_B: Item master data (Description, UOM).MTL_TRANSACTION_TYPES: Definitions of transaction actions (e.g., “PO Receipt”, “Subinventory Transfer”).ORG_ORGANIZATION_DEFINITIONS: Organization names and codes.MTL_TRANSACTION_LOT_NUMBERS: (Joined if needed) For lot-controlled items.
- Logical Relationships:
- MMT is the center of the star schema. It joins to
MTL_SYSTEM_ITEMS_BonINVENTORY_ITEM_IDandORGANIZATION_ID. - It links to
MTL_TRANSACTION_TYPESonTRANSACTION_TYPE_IDto decode the nature of the move. - Source documents are linked via
TRANSACTION_SOURCE_ID(which can point to PO headers, WIP Jobs, or Sales Orders depending on the Source Type).
- MMT is the center of the star schema. It joins to
Parameters & Filtering
- Organization Code / Subinventory: Essential for narrowing the scope to a specific warehouse or storage location.
- Item / Item Description: Allows tracing the history of a single product.
- Transaction Date From/To: Filters the massive dataset to a manageable time window.
- Transaction Type / Source Type: Critical for specific analysis (e.g., “Show me all ‘Sales Order Issues’ to analyze shipping volume”).
- Show Lots: A parameter to optionally join lot details, which can expand the row count significantly but is necessary for lot traceability.
Performance & Optimization
- Indexed Access: The query is heavily dependent on the composite indexes on
MTL_MATERIAL_TRANSACTIONS(typicallyINVENTORY_ITEM_ID,ORGANIZATION_ID, andTRANSACTION_DATE). - Partition Pruning: In large environments, MMT is often partitioned by date. Using the “Transaction Date” parameter allows the database to skip scanning older partitions, drastically improving speed.
- Avoid XML Parsing: By extracting directly to Excel/Text, the report avoids the heavy memory usage associated with rendering millions of transaction lines in standard PDF reports.
FAQ
Q: Why can’t I see the cost for some transactions? A: If the organization uses Standard Costing, costs are typically updated periodically or may not be stamped on every transaction type in the same way as Average Costing. Also, some “Logical” transactions might not carry a value impact in the same way as physical moves.
Q: Does this report show serial numbers?
A: Standard Material Transaction reports focus on Quantity and Lot. Serial numbers are stored in a child table (MTL_UNIT_TRANSACTIONS). While some versions of this report join to that table, it often multiplies the row count (one row per serial), so it is sometimes a separate option or report.
Q: What is the difference between “Transaction Date” and “Creation Date”? A: “Transaction Date” is when the movement physically occurred (or was backdated to). “Creation Date” is when the record was actually entered into the system. Large gaps between these two can indicate process issues (e.g., users entering data days after the work was done).
Oracle E-Business Suite Reporting Library
We provide an open source Oracle EBS SQLs as a part of operational and project implementation support toolkits for rapid Excel reports generation.
Blitz Report™ is based on Oracle EBS forms technology, and hence requires minimal training. There are no data or performance limitations since the output files are created directly from the database without going through intermediate file formats such as XML.
Blitz Report can be used as BI Publisher and Oracle Discoverer replacement tool. Standard Oracle BI Publisher and Discoverer reports can also be imported into Blitz Report for immediate output to Excel. Typically, reports can be created and version tracked within hours instead of days. The concurrent request output automatically opens upon completion without the need for re-formatting.
The Filters, Columns, Rows and Values fields are used to create and deliver the data in pivot table format with full drill down to details.

The Excel template upload functionality in Blitz Report allows users to create their own layouts by uploading an Excel template with additional sheets and charts, automatically refreshed when the report runs again. This allows to create custom dashboards and more advanced visualizations of report data.

You can download and use Blitz Report free of charge for your first 30 reports.
The installation and implementation process usually takes less than 1 hour; you can refer to our installation and user guides for specific details.
If you would like to optimize your Oracle EBS implementation and or operational reporting you can visit www.enginatics.com to review great ideas and example usage in blog. Or why not try for yourself in our demo environment.
Useful Links
Blitz Report™ – World’s fastest data upload and reporting for Oracle EBS
Oracle Discoverer replacement – importing worksheets into Blitz Report™
Blitz Report™ Questions & Answers
Supply Chain Hub by Blitz Report™
© 2025 Enginatics