Search Results mtl_transaction_types

Overview

The MTL_TRANSACTION_TYPES table is a core master data table within the Oracle E-Business Suite Inventory (INV) module. It serves as the definitive repository for all valid transaction types that can be performed on inventory items. Every material movement in the system, such as a receipt, issue, transfer, or adjustment, is classified by a specific transaction type defined in this table. This classification is fundamental to inventory accounting, costing, and reporting, as it determines the financial and physical impact of each transaction. The table's integrity is enforced by a primary key and it is extensively referenced by transactional tables across multiple EBS modules, making it a critical control point for inventory operations.

Key Information Stored

The table's primary identifier is the TRANSACTION_TYPE_ID, a unique numeric key. While the provided ETRM excerpt does not list all columns, based on its central role, the table typically stores descriptive and control attributes for each transaction type. Key columns generally include TRANSACTION_TYPE_NAME (a user-recognizable name), DESCRIPTION, and various flags that control transaction behavior. These flags often indicate if the transaction affects inventory quantities (e.g., increments or decrements on-hand balance), requires source documentation (like a purchase order or work order), impacts cost, or allows negative balances. The TRANSACTION_SOURCE_TYPE_ID column, noted in the foreign key relationship, links the transaction type to a category of source documents (e.g., Purchase Order, Sales Order, Work Order) defined in the MTL_TXN_SOURCE_TYPES table.

Common Use Cases and Queries

This table is primarily used for validation, reporting, and troubleshooting. Common scenarios include generating reports that summarize inventory activity by transaction type, validating user input in custom interfaces, and understanding the flow of transactions. A fundamental query is joining MTL_TRANSACTION_TYPES to the main transaction table, MTL_MATERIAL_TRANSACTIONS, to translate type IDs into meaningful names for reports. For example:

• SELECT mmt.TRANSACTION_ID, mtt.TRANSACTION_TYPE_NAME, mmt.TRANSACTION_QUANTITY FROM inv.mtl_material_transactions mmt, inv.mtl_transaction_types mtt WHERE mmt.transaction_type_id = mtt.transaction_type_id;

Another critical use case is querying the table itself to understand the system-defined transaction types and their controlling attributes, which is essential for configuring and supporting inventory processes.

Related Objects

As evidenced by the foreign key relationships, MTL_TRANSACTION_TYPES is a parent table to numerous transactional entities. The most significant relationship is with MTL_MATERIAL_TRANSACTIONS, the core table recording all inventory movements. It is also referenced by transaction request tables (MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES) and modules beyond core Inventory, including Enterprise Asset Management (EAM_JOB_COMPLETION_TXNS, EAM_OP_COMPLETION_TXNS), Complex Service Processing (CSP_USAGE_HISTORIES), and various localized extensions (JAI_* tables). The table itself references MTL_TXN_SOURCE_TYPES via TRANSACTION_SOURCE_TYPE_ID. This extensive web of dependencies underscores its role as a central master data entity.