Results for “mtl_txn_source_types”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_TXN_SOURCE_TYPES is an Inventory (INV) module reference table that stores the valid transaction source types recognized by Oracle E-Business Suite. A transaction source type identifies the originating business process or subsystem responsible for an inventory transaction — for example manual entry, a move order, a sales order issue, a work in process completion, or an Oracle Warehouse Management operation. Because inventory transactions, reservations, material transaction distributions, serial number histories, and cost records all must attribute their activity to a valid originating source, this table functions as a foundational lookup that governs transactional integrity across the INV, CST, WIP, WMS, and MRP schemas.

The table carries 34 documented columns in the 12.2.2 physical schema, is owned by the INV schema, and is keyed by MTL_TXN_SOURCE_TYPES_PK on TRANSACTION_SOURCE_TYPE_ID. From a dimensional or Data Vault modeling perspective, the mined metadata classifies this object as hub-leaning: it is a relatively compact, stable set of reference codes that many downstream transactional tables reference by foreign key. A modeling suggestion would therefore be to treat it as a hub (or a durable reference dimension), with dependent transaction tables acting as satellites or links that carry the foreign key.

Key Information Stored

The table's most important columns fall into three groups: identity, descriptive attributes, and auditing/extension fields.

• TRANSACTION_SOURCE_TYPE_ID — surrogate primary key and the value propagated to every referencing table.
• TRANSACTION_SOURCE_TYPE_NAME — the human-readable name of the source type, used in list of values and reporting.
• DESCRIPTION — longer text describing the purpose of the source type.
• TRANSACTION_SOURCE_CATEGORY — groups source types into higher-level categories used by transaction processing logic.
• TRANSACTION_SOURCE — further qualifies the source, often aligning with the Oracle Application or subsystem origin.
• DISABLE_DATE — date on which the source type becomes unavailable for new transactions.
• USER_DEFINED_FLAG — indicates whether the row is a seeded Oracle value or a customer-defined entry.
• VALIDATED_FLAG — signals whether the source type has passed validation checks.
• DESCRIPTIVE_FLEX_CONTEXT_CODE and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield context and its segment values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard who-columns for audit and change tracking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for the last update.
• ZD_EDITION_NAME — edition column supporting EBS online patching (12.2.x). The unique index MTL_TXN_SOURCE_TYPES_U1 covers TRANSACTION_SOURCE_TYPE_ID and ZD_EDITION_NAME, making it the business-key candidate alongside the primary key.

Common Use Cases and Queries

The most frequent requirement is decoding a transaction's source type into a readable name for reporting. A typical join retrieves material transaction history with its source:

• Inventory transaction inquiry: join MTL_MATERIAL_TRANSACTIONS.TRANSACTION_SOURCE_TYPE_ID to this table to display the source type name alongside transaction quantity, date, and item.
• Reservation analysis: resolve MTL_RESERVATIONS.DEMAND_SOURCE_TYPE_ID and SUPPLY_SOURCE_TYPE_ID to distinguish which business demand created a reservation.
• Serial number history: decode MTL_SERIAL_NUMBERS.LAST_TXN_SOURCE_TYPE_ID to explain the origin of the most recent transaction on a serialized unit.
• Costing reconciliation: join costing tables such as CST_INV_LAYERS or MTL_TRANSACTION_ACCOUNTS to attribute cost activity by source.
• Configuration review: filter on USER_DEFINED_FLAG and DISABLE_DATE to audit which source types are active and customer-defined.

A representative pattern selects the ID, name, and category, restricting to enabled rows where DISABLE_DATE IS NULL and joining to the transaction table on TRANSACTION_SOURCE_TYPE_ID.

Related Objects

This table is referenced by a large number of foreign keys across multiple modules. The most significant include:

• MTL_MATERIAL_TRANSACTIONS — the primary transaction fact, joined on TRANSACTION_SOURCE_TYPE_ID.
• MTL_TRANSACTION_ACCOUNTS and MTL_TRANSACTION_LOT_NUMBERS — cost and lot-level transaction detail.
• MTL_RESERVATIONS and MTL_RESERVATIONS_INTERFACE — demand and supply source references.
• MTL_TRANSACTION_TYPES, MTL_TXN_REQUEST_LINES, and IC_TXN_REQUEST_LINES — transaction type and move order configuration.
• MTL_DEMAND and MTL_USER_SUPPLY — supply/demand source references.
• MTL_SERIAL_NUMBERS — last transaction source tracking.
• Costing and integration tables such as CST_INV_LAYERS and MTL_TRANSACTIONS_INTERFACE.

Because seeded source type IDs are referenced by so many dependents, rows should be added or disabled rather than deleted to preserve referential integrity.