Skip to content
EBS Reference

MTL_TRANSACTION_TYPES

Schema: INVcontrol

The transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions

Identity
Module: InventoryNot org-partitioned
Notes

Global reference data — no org column. USER_DEFINED_FLAG separates site-defined types from seeded ones; treat user-defined type ids as configuration, not constants, across environments.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

7 fields · 1 key

7 fields.

Table fields: position, field name, description, data type, and flags. 7 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_TYPE_IDTransaction type id — what the material ledger carriesNUMBER
Primary-key field
2TRANSACTION_TYPE_NAMEThe type's display nameVARCHAR2
3TRANSACTION_ACTION_IDThe physical action the type performsNUMBER
Decodes via FND_LOOKUP_VALUES — the exact lookup type is unattested; confirm it against your instance
4TRANSACTION_SOURCE_TYPE_IDThe document source type the type pairs withNUMBER
5DESCRIPTIONType descriptionVARCHAR2
6DISABLE_DATEWhen the type was disabled — NULL while activeDATE
7USER_DEFINED_FLAGSite-defined vs seeded type — user-defined ids differ across environmentsVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading MTL_TRANSACTION_TYPES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <TRANSACTION_TYPE_ID>, <watermark>

-- ============================================================
-- Table  : MTL_TRANSACTION_TYPES — The transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions
-- Purpose: Column-selected read of MTL_TRANSACTION_TYPES — auto-generated from field metadata
-- Grain  : One row per TRANSACTION_TYPE_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.TRANSACTION_TYPE_ID AS "Transaction type id — what the material ledger carries",
  t.TRANSACTION_TYPE_NAME AS "The type's display name",
  t.TRANSACTION_ACTION_ID AS "The physical action the type performs",  -- decode t.TRANSACTION_ACTION_ID via FND_LOOKUP_VALUES (LANGUAGE-filtered; confirm the LOOKUP_TYPE against your instance) — see quirks guide #lookups
  t.TRANSACTION_SOURCE_TYPE_ID AS "The document source type the type pairs with",
  t.DESCRIPTION AS "Type description",
  t.DISABLE_DATE AS "When the type was disabled — NULL while active",
  t.USER_DEFINED_FLAG AS "Site-defined vs seeded type — user-defined ids differ across environments"
FROM <catalog>.<schema>.MTL_TRANSACTION_TYPES t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.TRANSACTION_TYPE_ID = <TRANSACTION_TYPE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.TRANSACTION_TYPE_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • MTL_MATERIAL_TRANSACTIONSMTL_TRANSACTION_TYPESforeign key · N:1
    ON MTL_MATERIAL_TRANSACTIONS.TRANSACTION_TYPE_ID = MTL_TRANSACTION_TYPES.TRANSACTION_TYPE_ID
  • MTL_TXN_REQUEST_HEADERSMTL_TRANSACTION_TYPESforeign key · N:1
    ON MTL_TXN_REQUEST_HEADERS.TRANSACTION_TYPE_ID = MTL_TRANSACTION_TYPES.TRANSACTION_TYPE_ID

Browse more Inventory tables

More Inventory tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.