INV Transaction Types – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
None
Report Parameters
Source, Transaction Source Type, Show DFF Attributes
Oracle EBS Tables Used
mtl_transaction_types, mtl_txn_source_types
Report Categories
Related Reports
INV Transaction Historical Summary, CAC WIP Jobs With Complete Status Which Are Ready for Close, CAC AP Accrual IR ISO Match Analysis, CAC Internal Order Shipment Margin
Running This SQL Without Blitz Report
Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | INV Transaction Types 21-Jul-2024 010119.xlsx |
| Blitz Report™ XML Import | INV_Transaction_Types.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/inv-transaction-types/ |
INV Transaction Types - Case Study & Technical Analysis
Executive Summary
The INV Transaction Types report is a configuration document that lists all the defined “Actions” that can be performed on inventory. Examples include “PO Receipt”, “Subinventory Transfer”, “Miscellaneous Issue”, and “WIP Assembly Return”. This report defines the rules for each action.
Business Challenge
Transaction Types control the financial and operational behavior of a movement.
- Financial Impact: “Does this ‘Sample Issue’ hit the Marketing Expense account or the Scrap account?”
- Process Control: “Does this ‘RMA Receipt’ require a Quality Inspection?”
- Location Control: “Can I perform this transaction in a WMS-enabled organization?”
Solution
The INV Transaction Types report details the setup of each transaction type. It shows the link between the user-facing name (e.g., “Misc Issue”) and the system behavior (e.g., “Issue from Stores”).
Key Features:
- Action Definition: Shows the “Source Type” (e.g., Inventory) and “Action” (e.g., Issue from Stores).
- Financial Flags: Indicates if the transaction is “Project Enabled” or “Location Required”.
- Status Control: Shows if the transaction is valid for certain material statuses.
Technical Architecture
The report queries the transaction type definition table.
Key Tables and Views
MTL_TRANSACTION_TYPES: The master table for transaction definitions.MTL_TXN_SOURCE_TYPES: The source type linked to the transaction.
Core Logic
- Retrieval: Selects all records from
MTL_TRANSACTION_TYPES. - Context: Joins to
MTL_TXN_SOURCE_TYPESto explain the source. - Validation: Checks flags for Status Control and Location Control.
Business Impact
- Process Standardization: Ensures that everyone uses the correct transaction type for a given business scenario (e.g., using “Scrap Issue” instead of “Misc Issue”).
- Financial Accuracy: Ensures that transactions drive the correct accounting entries.
- System Governance: Documents the allowed inventory movements for audit purposes.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics