EBS Reference
OE_TRANSACTION_TYPES_TL
Schema: ONTcontrolLanguage-stripedTranslation companion for order/line transaction types — the display name and description per installed language; the only place the type name exists
Identity
Module: Order ManagementNot org-partitioned
Fusion equivalents (3)
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.
- 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 withORGANIZATION_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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
In field listings, the Key chip marks a primary-key field.
Translations
OE_TRANSACTION_TYPES_TL holds the per-language translation rows for OE_TRANSACTION_TYPES_ALL — one row per LANGUAGE. Filter to one LANGUAGE or rows multiply.
Fields
5 fields · 2 key
5 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | TRANSACTION_TYPE_ID | The transaction type | NUMBER | Primary-key field |
| 2 | LANGUAGE | Language of this row — one row per installed language per type | VARCHAR2 | Primary-key field |
| 3 | SOURCE_LANG | The language this row's text was translated from | VARCHAR2 | |
| 4 | NAME | The type's display name — exists only on this table, not on the base | VARCHAR2 | |
| 5 | DESCRIPTION | Type description in this row's language | VARCHAR2 |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading OE_TRANSACTION_TYPES_TL 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
5 parameters not filled: <catalog>, <schema>, <language>, <TRANSACTION_TYPE_ID>, <watermark>
-- ============================================================
-- Table : OE_TRANSACTION_TYPES_TL — Translation companion for order/line transaction types — the display name and description per installed language; the only place the type name exists
-- Purpose: Column-selected read of OE_TRANSACTION_TYPES_TL — 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 "The transaction type",
t.LANGUAGE AS "Language of this row — one row per installed language per type",
t.SOURCE_LANG AS "The language this row's text was translated from",
t.NAME AS "The type's display name — exists only on this table, not on the base",
t.DESCRIPTION AS "Type description in this row's language"
FROM <catalog>.<schema>.OE_TRANSACTION_TYPES_TL t
WHERE
t.LANGUAGE = '<language>' -- one language or rows multiply; translations fall back to SOURCE_LANG
-- 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
ON OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID = OE_TRANSACTION_TYPES_TL.TRANSACTION_TYPE_ID AND OE_TRANSACTION_TYPES_TL.LANGUAGE = '<language>'
More Order Management tables
- OE_DROP_SHIP_SOURCESThe drop-ship bridge — one row linking a sales order line to the purchase requisition and purchase order raised to fulfill it from the supplier; the only physical tie between the order-to-cash and procure-to-pay flows
- OE_HOLD_DEFINITIONSHold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to
- OE_HOLD_SOURCES_ALLHold source criteria — the entity a hold was applied against (a customer, an order, an item, a warehouse), stored as a generic entity code plus a polymorphic id, with the hold-until date
- OE_ORDER_HEADERS_ALLThe sales order header — one row per order or quote, carrying the order number, type, customer references, currency, and the workflow status the whole order-to-cash cycle hangs off; operating-unit striped
- OE_ORDER_HOLDS_ALLHold instances on orders and lines — one row per applied hold, pointing at the hold source that applied it and the release record once lifted; the "why isn't this line shipping" table
- OE_ORDER_LINES_ALLSales order lines at their most granular workflow unit — shipment splits, model options, included items, and configuration items each get their own row, individually statused and quantity-tracked through booking, shipping, and invoicing