Search Results ecx_transactions_tl_u1

Overview

ECX.ECX_TRANSACTIONS_TL is the translation (TL) table for the E-Business Suite Common Exchange (ECX) transaction registry. It stores language-specific, descriptive text associated with transaction definitions owned by the ECX schema, allowing the same logical transaction to be presented in multiple runtime languages. In Oracle EBS 12.1.1 and 12.2.2, translation tables of this form follow the standard MLS (Multi-Lingual Support) pattern: one row per transaction per installed language, with the base language flagged in SOURCE_LANG and non-base languages carrying the translated value. The object resides in the APPS_TS_SEED tablespace and holds seed/data-type content rather than high-volume transactional data. From a heuristic Data Vault modeling perspective, this object is classified as standalone, meaning it is neither a pure hub, link, nor satellite on its own; in practice it behaves like a descriptive satellite keyed by the transaction identifier and language, and it should be modeled as such only if it is absorbed into a broader ECX integration model.

Key Information Stored

The most important columns fall into three groups: identity, descriptive text, and standard audit/MLS columns.

• TRANSACTION_ID (NUMBER) — Surrogate identifier of the parent ECX transaction. It is the leading column of both the primary key and the unique index, and it is the join key back to the base ECX transaction table.
• TRANSACTION_DESCRIPTION (VARCHAR2 256) — The internal transaction description; the primary payload of this table and the column most often surfaced in lookup/LOV queries.
• LANGUAGE (VARCHAR2) — The translated language of the row; the second component of the primary key.
• SOURCE_LANG (VARCHAR2) — The seeded/base language from which translations originate, used to select the correct row for display resolution.
• ZD_EDITION_NAME (VARCHAR2 30) — Editioning qualifier used by the Online Patching/editioning infrastructure; it participates in the U1 unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the user, timestamp, and login context of row creation and last update.

The documented surrogate primary key is ECX_TRANSACTIONS_TL_PK (TRANSACTION_ID, LANGUAGE). The business-key candidate is the unique index ECX_TRANSACTIONS_TL_U1 (TRANSACTION_ID, LANGUAGE, ZD_EDITION_NAME), which is also the exact index name the user searched for. The additional ZD_EDITION_NAME column in U1 reflects the editioning model introduced in the 12.2.x code line; on 12.1.1 deployments this column is generally not meaningful.

Common Use Cases and Queries

Typical use cases include resolving a display description for a transaction in the user's session language, building ECX transaction lookup reports, and auditing translation coverage for seed data. A common selection pattern retrieves the row matching a target language and falls back to the source language when no translation exists:

SELECT t.transaction_id
     , t.transaction_description
  FROM ecx.ecx_transactions_tl t
 WHERE t.transaction_id = :transaction_id
   AND t.language IN (:session_language, t.source_lang)
 ORDER BY DECODE(t.language, :session_language, 1, 2)
 FETCH FIRST 1 ROW ONLY;

For translation-coverage reporting, a useful query joins the base table to this TL table and highlights transactions with no translated row:

SELECT b.transaction_id
  FROM ecx.ecx_transactions b
  LEFT JOIN ecx.ecx_transactions_tl t
    ON t.transaction_id = b.transaction_id
   AND t.language = :target_language
 WHERE t.transaction_id IS NULL;

Because the object is flagged "Oracle Internal Use Only," all queries should be read-only and executed against standard APIs or views wherever possible, with direct access reserved for reporting and diagnostics.

Related Objects

The following objects are significant in the ECX translation ecosystem and the FK/join relationships documented for this table:

• ECX.ECX_TRANSACTIONS_TL# — The underlying editioning/trigger companion object for the TL table; referenced by the base object.
• ECX_TRANSACTIONS_TL_U1 — Unique index on (TRANSACTION_ID, LANGUAGE, ZD_EDITION_NAME); the primary business-key candidate and the index name in the user's search.
• ECX_TRANSACTIONS_TL_PK — Primary key on (TRANSACTION_ID, LANGUAGE).
• ECX.ECX_TRANSACTIONS (base table) — The parent transaction registry; joined on TRANSACTION_ID and the source-language relationship.
• FND_USER — Referenced by the CREATED_BY and LAST_UPDATED_BY columns.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN.

No additional foreign-key references are documented for this object in the ETRM metadata; it is functionally standalone and is primarily consumed by ECX concurrent programs and lookup logic rather than by other application tables.