Search Results ecx_transactions_tl




Overview
Explore in AI Chat

Overview

ECX_TRANSACTIONS_TL is the translation (language-dependent) table for internal transaction definitions within the Oracle XML Gateway (ECX) module of Oracle E-Business Suite. The parent entity, ECX_TRANSACTIONS, stores the language-independent definition of each internal transaction that the XML Gateway can process — the transaction type, subtype, and the processing logic that routes an inbound or outbound XML business document. ECX_TRANSACTIONS_TL holds the translated descriptive text for those definitions, allowing the transaction description to be presented in the session language of the user or concurrent program that references it.

The object is owned by the ECX schema and is documented as VALID in both the 12.1.1 and 12.2.2 releases. The ETRM metadata classifies this table, using a heuristic derived from its foreign-key structure, as standalone rather than as a hub, link, or satellite. In Data Vault modeling terms this suggests the table behaves as a purely dependent translation segment attached to its base table rather than as an independently integrated entity; a modeler would typically represent it as a descriptive satellite keyed by the base transaction identifier plus language.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • TRANSACTION_ID — The surrogate identifier of the internal transaction definition. This column joins back to the base ECX_TRANSACTIONS table and forms the leading component of the primary key.
  • LANGUAGE — The language code for the translated row. Together with TRANSACTION_ID it constitutes the composite primary key ECX_TRANSACTIONS_TL_PK, meaning one translated description is permitted per transaction per installed language.
  • TRANSACTION_DESCRIPTION — The translated description of the internal transaction. This is the principal payload of the table and the column most commonly surfaced in reports and XML Gateway setup inquiries.
  • SOURCE_LANG — Identifies the source language from which the translation was derived, used by the Oracle translation framework to track the origin of the text.
  • ZD_EDITION_NAME — The editioning column introduced by the Oracle E-Business Suite online patching infrastructure. It participates in the unique index ECX_TRANSACTIONS_TL_U1 (TRANSACTION_ID, LANGUAGE, ZD_EDITION_NAME) and is populated by the editioning runtime rather than by application users.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns capturing audit information for row creation and the most recent modification, including the login identifier of the updating session.

The documented business-key candidate is the unique index ECX_TRANSACTIONS_TL_U1 over TRANSACTION_ID, LANGUAGE, and ZD_EDITION_NAME. Because the editioning column is system-managed, the effective business key for application purposes remains TRANSACTION_ID plus LANGUAGE.

Common Use Cases and Queries

The primary use of this table is retrieval of a translated transaction description for display in XML Gateway setup forms, concurrent program reports, and custom diagnostic queries. A typical join retrieves the base definition alongside its translation:

  • Reporting the list of defined transactions in a specific language: SELECT t.transaction_type, tl.transaction_description FROM ecx_transactions t, ecx_transactions_tl tl WHERE t.transaction_id = tl.transaction_id AND tl.language = USERENV('LANG');
  • Verifying translation coverage by counting languages per transaction, which identifies definitions that lack a description in a deployed language.
  • Auditing recent description changes through the LAST_UPDATED_BY and LAST_UPDATE_DATE columns, useful when troubleshooting XML Gateway configuration drift.
  • Joining to transaction type and document mapping tables to produce a complete picture of the XML Gateway processing path for a given business document.

Because the table is language-dependent, queries must always constrain LANGUAGE to avoid returning duplicate rows for the same transaction.

Related Objects

  • ECX_TRANSACTIONS — The base, language-independent table; joined on TRANSACTION_ID. This is the parent of the translation row.
  • ECX_TRANSACTION_TYPES_TL — Sibling translation table for transaction types, used in the same setup and reporting flows.
  • ECX_OUT_HEADERS / ECX_IN_HEADERS — Header tables for outbound and inbound XML messages that reference transaction definitions during processing.
  • ECX_DOCUMENTS_TL — Document definition translations referenced alongside transaction definitions.
  • FND_LANGUAGES — Provides the valid values and descriptions for the LANGUAGE and SOURCE_LANG columns.
  • FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user names in audit reports.