Results for “ecx_standards_tl”

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

Overview

The ECX_STANDARDS_TL table resides in the ECX schema and belongs to the XML Gateway module of Oracle E-Business Suite. It stores the translated (language-specific) definitions of XML Gateway standards, which are the declarative specifications that describe how XML messages map to and from Oracle EBS business objects. In Oracle EBS 12.1.1 and 12.2.2, XML Gateway relies on standards to govern document types, transactions, and message transformations used during inbound and outbound integration processing. The table is a translation ("_TL") companion to the base standards definition table and holds one row per standard per installed language.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. Because ECX_STANDARDS_TL holds descriptive, language-dependent attributes of a standard and carries no outbound foreign keys to other tables, it is best modeled as a satellite attached to a standards hub, with the hub keyed by STANDARD_ID. The composite primary key of STANDARD_ID and LANGUAGE reflects the multi-language, non-volatile nature of the translated content.

Key Information Stored

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

• STANDARD_ID — Surrogate identifier of the parent standard; the principal business join key linking the translation row to its base definition.
• LANGUAGE — The language code of the translated row; combined with STANDARD_ID it forms the primary key ECX_STANDARDS_TL_PK.
• STANDARD_DESC — The translated descriptive text for the standard, the primary payload of this table.
• SOURCE_LANG — Indicates the source language from which the translation was derived, supporting the standard Oracle translation model.
• ZD_EDITION_NAME — Editioning column used for online patching in Oracle EBS 12.2.2, participating in the unique index ECX_STANDARDS_TL_U1 (STANDARD_ID, LANGUAGE, ZD_EDITION_NAME).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns that record creation and modification history.

The primary key is the surrogate/business composite ECX_STANDARDS_TL_PK (STANDARD_ID, LANGUAGE). The unique index ECX_STANDARDS_TL_U1 extends this with ZD_EDITION_NAME, making it the strongest business-key candidate under the 12.2.2 editioning model.

Common Use Cases and Queries

Typical scenarios involve reporting the available language translations of a standard, joining translated descriptions to the base standard definition, and diagnosing missing translations that cause English text to appear where a localized description is expected.

A representative query retrieves the translated description for a given standard and language:

• SELECT t.standard_id, t.language, t.standard_desc FROM ecx.ecx_standards_tl t WHERE t.standard_id = :standard_id AND t.language = USERENV('LANG');

A coverage report identifies which standards lack a translation for a target language:

• SELECT s.standard_id FROM ecx.ecx_standards s WHERE NOT EXISTS (SELECT 1 FROM ecx.ecx_standards_tl t WHERE t.standard_id = s.standard_id AND t.language = 'FR');

Auditing recent changes to translated content can be performed using LAST_UPDATE_DATE and LAST_UPDATED_BY, which is useful when validating translation uploads during an upgrade from 12.1.1 to 12.2.2.

Related Objects

The following objects are most significant to ECX_STANDARDS_TL:

• ECX_STANDARDS — The base standards definition; joined on STANDARD_ID.
• ECX_STANDARD_TL — Related translated standard content within the XML Gateway family.
• ECX_DOCUMENT_TYPES and ECX_DOCUMENT_TYPES_TL — Document type definitions referencing standards.
• ECX_TRANSACTIONS — Runtime transactions that consume the standards definitions.
• FND_LANGUAGES — Provides the installed language codes matched by the LANGUAGE column.

Because the object is classified as standalone, direct foreign-key dependencies are not documented; relationships are maintained conceptually through STANDARD_ID.