Search Results mtl_txn_source_types




Overview

The MTL_TXN_SOURCE_TYPES table is a foundational reference table within the Oracle E-Business Suite Inventory (INV) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for defining and validating the origin or source of all material transactions processed through the system. Every inventory movement, from a simple subinventory transfer to a complex receipt from purchasing, must be associated with a valid source type. This table provides the controlled list of these types, ensuring data integrity and enabling the system to correctly process and account for transactions based on their origin. Its primary role is to act as a key lookup for numerous transactional and planning tables, governing the flow of material and reservation data.

Key Information Stored

The table's core data is its unique identifier and descriptive name for each transaction source. The primary column is TRANSACTION_SOURCE_TYPE_ID, which is the numeric primary key (PK: MTL_TXN_SOURCE_TYPES_PK) used throughout the system to reference a specific source type. While the provided metadata does not list all columns, standard implementation includes a TRANSACTION_SOURCE_TYPE_NAME column containing the textual description (e.g., 'Inventory', 'Purchase Order', 'Sales Order', 'Work Order', 'Account alias'). The table may also contain columns for controlling user-defined statuses, enabling or disabling sources, and audit information like creation date and last update date. The existence of numerous foreign key relationships confirms that this ID is the critical piece of information stored and referenced.

Common Use Cases and Queries

This table is central to reporting, data validation, and troubleshooting transactional flows. A common use case is enriching transaction reports from MTL_MATERIAL_TRANSACTIONS with the source type name for readability. Developers use it to validate parameters before calling inventory transaction APIs. For instance, a query to list all material transactions with their source description would join on TRANSACTION_SOURCE_TYPE_ID. Sample SQL patterns include identifying all transactions originating from a specific source like purchase orders, or analyzing reservation sources in MTL_RESERVATIONS. Furthermore, understanding the valid source types is essential when creating manual transactions via the Move Order module or when interfacing transactions from external systems.

Related Objects

As evidenced by the extensive foreign key relationships in the metadata, MTL_TXN_SOURCE_TYPES is a critical parent table for a wide array of Inventory and Costing objects. Key related tables include: