Skip to content
EBS Reference

OE_TRANSACTION_TYPES_TL

Schema: ONTcontrolLanguage-striped

Translation companion for order/line transaction types — the display name and description per installed language; the only place the type name exists

Module: Order ManagementNot org-partitioned
What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K 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

Table fields: position, field name, description, data type, and flags. 5 fields.
#FieldDescriptionTypeFlags
1TRANSACTION_TYPE_IDThe transaction typeNUMBER
Key
2LANGUAGELanguage of this row — one row per installed language per typeVARCHAR2
Key
3SOURCE_LANGThe language this row's text was translated fromVARCHAR2
4NAMEThe type's display name — exists only on this table, not on the baseVARCHAR2
5DESCRIPTIONType description in this row's languageVARCHAR2

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

Query parameters
-- ============================================================
-- 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;

5 parameters not filled: <catalog>, <schema>, <language>, <TRANSACTION_TYPE_ID>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • OE_TRANSACTION_TYPES_ALLOE_TRANSACTION_TYPES_TLtranslation · 1:N
    ON OE_TRANSACTION_TYPES_ALL.TRANSACTION_TYPE_ID = OE_TRANSACTION_TYPES_TL.TRANSACTION_TYPE_ID AND OE_TRANSACTION_TYPES_TL.LANGUAGE = '<language>'

Browse more Order Managementtables →

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.