Results for “oe_transaction_types_tl”

50+ results




Overview
Explore in AI Chat

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

Overview

OE_TRANSACTION_TYPES_TL is the translation (multi-lingual) table for the base transaction type definition held in OE_TRANSACTION_TYPES_ALL within the Oracle Order Management (ONT) product. Transaction types drive the fundamental behavior of the order-to-cash flow in Oracle EBS 12.1.1 and 12.2.2: they determine whether a document behaves as an order, a quote, a return, or a mixed document, and they govern defaulting, pricing, fulfillment, and workflow behavior attached to that document. Because the operational attributes of a transaction type are language-independent, they reside in OE_TRANSACTION_TYPES_ALL, while the user-facing text — the name and description displayed on forms, reports, and self-service pages — is stored per installed language in this table.

From a Data Vault modeling perspective, the mined foreign-key structure classifies OE_TRANSACTION_TYPES_TL heuristically as a link. It connects two distinct hubs of reference data: OE_TRANSACTION_TYPES_ALL (the transaction type entity) and FND_LANGUAGES (the language entity). This classification is a modeling suggestion rather than a functional statement; operationally the table behaves as a language-dependent descriptor record keyed by the combination of transaction type and language.

Key Information Stored

The documented physical schema in ONT contains 13 columns. The most significant are:

  • TRANSACTION_TYPE_ID — Surrogate identifier of the transaction type; part of the composite primary key and a foreign key to OE_TRANSACTION_TYPES_ALL.
  • LANGUAGE — Installed language code; the second component of the composite primary key and a foreign key to FND_LANGUAGES.
  • SOURCE_LANG — The language in which the row was originally entered, used by the translation (TL) framework to distinguish the source row from translated rows.
  • NAME — The translated display name of the transaction type, shown in Order Management windows, pick lists, and reports.
  • DESCRIPTION — The translated description of the transaction type’s purpose or behavior.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent change and its session context.
  • PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — Concurrent program context identifying the process that created or last modified the row.

The composite primary key OE_TRANSACTION_TYPES_TL_PK spans (TRANSACTION_TYPE_ID, LANGUAGE), and a unique index, OE_TRANSACTION_TYPES_TL_U1, is documented on the same column pair. Together these enforce exactly one translated row per transaction type per language — the business-key candidate. The base table primary key (transaction type alone) is the surrogate key in Data Vault terms; the (TRANSACTION_TYPE_ID, LANGUAGE) pairing is the natural key that guarantees translation uniqueness.

Common Use Cases and Queries

The principal use case is resolving the translated name of a transaction type for forms, reports, and interfaces in a multi-language environment. A typical query joins the translation table to the base table, filtering to the user’s session language, with a fallback to the source language where no translated row exists:

  • Reporting on order volumes grouped by transaction type name, joining OE_HEADERS_ALL to OE_TRANSACTION_TYPES_ALL and restricting this table to a single LANGUAGE value to avoid duplicate rows.
  • Populating lookup lists in custom concurrent programs, order import interfaces, and OAF pages, selecting NAME and DESCRIPTION for the runtime language.
  • Translation maintenance and audits: identifying transaction types that lack a row for a given LANGUAGE, or comparing SOURCE_LANG against LANGUAGE to find untranslated definitions.
  • Data migration scripts for 12.1.1 to 12.2.2 upgrades, where translated rows must be preserved and SOURCE_LANG set correctly per the TL framework conventions.

A representative pattern selects the translated NAME from this table for a supplied TRANSACTION_TYPE_ID and LANGUAGE, falling back to the SOURCE_LANG row when the primary lookup returns no data.

Related Objects

  • OE_TRANSACTION_TYPES_ALL — The base multilingual master table; joined on TRANSACTION_TYPE_ID. It holds the functional, language-independent attributes of each transaction type.
  • FND_LANGUAGES — The language definition table; joined on LANGUAGE to resolve language names and installed-language status.
  • OE_ORDER_HEADERS_ALL — Stores the transaction type on each order header, indirectly referencing this table through the base table for display of order type names.
  • OE_TRANSACTION_TYPES_VL — The translated view layered over OE_TRANSACTION_TYPES_ALL and this table, exposing the current-language name and description for forms and reports.
  • OE_TRANSACTION_TYPES_TL_PK / OE_TRANSACTION_TYPES_TL_U1 — The primary key constraint and unique index enforcing one translated row per transaction type and language.
  • FND_LANGUAGE and the TL framework objects — Govern SOURCE_LANG handling and translation propagation whenever new transaction types are defined or languages are installed.