Results for “mtl_transaction_types”

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

Overview

MTL_TRANSACTION_TYPES is a foundational reference table in the Oracle Inventory (INV) module of Oracle E-Business Suite, holding in its 12.1.1 and 12.2.2 releases. It defines the valid classes of inventory transactions that the system may post against inventory organizations, subinventories, and material balances. Every material movement captured in Oracle Inventory — receipts, issues, transfers, subinventory transfers, WIP component issues, cycle count adjustments, and miscellaneous transactions — is classified by a row in this table. Because it acts as the central catalogue of transaction semantics, MTL_TRANSACTION_TYPES governs which attributes the transaction requires (for example, whether a location is mandatory), which shortage messaging behaviour applies, and which source type feeds the transaction.

The table resides in the INV schema under the ETRM 12.2.2 documented physical schema and exposes 33 columns. From a Data Vault modelling perspective, the mined foreign-key structure classifies this object as hub-leaning: TRANSACTION_TYPE_ID behaves as a stable business key referenced widely across the EBS inventory and manufacturing subledgers, making the table a natural candidate for a hub entity, with its descriptive attributes (name, description, type class, control flags) suitable for satellite treatment. This is offered as a modelling suggestion rather than an implementation directive.

Key Information Stored

The table is anchored by the surrogate primary key TRANSACTION_TYPE_ID, defined by MTL_TRANSACTION_TYPES_PK. In multi-tenant or edition-enabled 12.2.2 environments, the unique index MTL_TRANSACTION_TYPES_U1 combines TRANSACTION_TYPE_ID with ZD_EDITION_NAME, forming the business-key candidate and supporting editioning.

The most significant descriptive and functional columns are:

• TRANSACTION_TYPE_NAME — the human-readable label, such as "Subinventory Transfer" or "Miscellaneous Issue".
• DESCRIPTION — supporting narrative for the transaction type.
• TRANSACTION_ACTION_ID — identifies the action performed (issue, receipt, transfer, and similar).
• TRANSACTION_SOURCE_TYPE_ID — the foreign key to MTL_TXN_SOURCE_TYPES that identifies the originating source of the transaction.
• USER_DEFINED_FLAG — indicates whether the row is a seeded Oracle type or a user-defined type.
• TYPE_CLASS — the internal classification controlling transaction behaviour.
• STATUS_CONTROL_FLAG — determines whether material status control applies.
• LOCATION_REQUIRED_FLAG — governs whether a locator must be supplied.
• SHORTAGE_MSG_ONLINE_FLAG and SHORTAGE_MSG_BACKGROUND_FLAG — control shortage warning behaviour for interactive and concurrent processing.
• DISABLE_DATE — the date after which the type is no longer selectable.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexible attribute columns.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Common Use Cases and Queries

Reporting and integration logic commonly join MTL_MATERIAL_TRANSACTIONS to MTL_TRANSACTION_TYPES to render readable transaction activity, as demonstrated below:

• Transaction history reporting: SELECT mmt.transaction_id, mtt.transaction_type_name, mmt.transaction_quantity FROM mtl_material_transactions mmt, mtl_transaction_types mtt WHERE mmt.transaction_type_id = mtt.transaction_type_id.
• Identifying valid types for a given process by filtering on TRANSACTION_ACTION_ID, TRANSACTION_SOURCE_TYPE_ID, and DISABLE_DATE.
• Auditing user-defined versus seeded transaction types through USER_DEFINED_FLAG.
• Moving order analysis by joining MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES to this table.
• Determining whether location entry is mandatory via LOCATION_REQUIRED_FLAG before building transaction interfaces.

Related Objects

MTL_TRANSACTION_TYPES participates in an extensive referential network. It references MTL_TXN_SOURCE_TYPES through TRANSACTION_SOURCE_TYPE_ID. Conversely, it is referenced by MTL_MATERIAL_TRANSACTIONS, MTL_TXN_REQUEST_HEADERS, MTL_TXN_REQUEST_LINES, and MTL_STATUS_TRANSACTION_CONTROL via TRANSACTION_TYPE_ID. Manufacturing and asset modules depend on it through EAM_JOB_COMPLETION_TXNS and EAM_OP_COMPLETION_TXNS, while AHL_WORKORDER_MTL_TXNS, CSP_USAGE_HISTORIES, and several JAI (India localization) tables — JAI_CMN_TRANSACTIONS_T, JAI_MTL_TRXS, and JAI_PO_OSP_CENVAT_HDRS — also join on TRANSACTION_TYPE_ID. This breadth confirms the table's hub status as a master reference for inventory transaction semantics.