Results for “ar_standard_text_tl”

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

Overview

AR_STANDARD_TEXT_TL is the multilingual support (MLS) table in the Oracle Receivables (AR) schema that stores translated content for the standard text messages used on printed and electronic customer statements. Its non-translated counterpart, AR_STANDARD_TEXT_B, holds the language-independent definition of each standard text record—principally the STANDARD_TEXT_ID surrogate key—while this table carries the actual message body (TEXT) per installed language. In Oracle EBS 12.1.1 and 12.2.2, the _TL suffix identifies a translation table participating in the standard MLS architecture: one row per base entity per language, maintained by the Translation (MLS) framework and populated through the standard texts setup user interface or the translation APIs.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as standalone, meaning no foreign key dependencies to other tables were mined from the constraint structure. Where the object is modeled, it is best treated as a satellite-like descriptive table attached to the AR_STANDARD_TEXT_B hub on STANDARD_TEXT_ID, with LANGUAGE forming part of the natural composite key. The absence of documented FK constraints reflects standard EBS MLS design: referential integrity to the base table is enforced by the application and by the primary key structure rather than by database-level foreign keys between the base and translation tables.

Key Information Stored

The table contains ten documented columns, of which the following are most significant:

• STANDARD_TEXT_ID — Surrogate identifier of the parent standard text record; joins directly to AR_STANDARD_TEXT_B. It is the leading column of the primary key.
• LANGUAGE — The installed Oracle language code (for example, US, D, ZHS) in which the TEXT value is expressed. Together with STANDARD_TEXT_ID it forms the composite primary key AR_STANDARD_TEXT_TL_PK.
• TEXT — The translated statement message text displayed to customers using that language. This is the substantive payload of the row.
• SOURCE_LANG — The language from which the current row was derived, indicating the base language of the source content and supporting the MLS translation workflow.
• ZD_EDITION_NAME — The edition identifier used by Oracle's edition-based redefinition (EBR) infrastructure, included in the unique index AR_STANDARD_TEXT_TL_U1 (STANDARD_TEXT_ID, LANGUAGE, ZD_EDITION_NAME) to support online patching in Release 12.2.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record the standard who/when audit trail required for all EBS transactional and setup tables.

The primary key AR_STANDARD_TEXT_TL_PK is the surrogate composite key (STANDARD_TEXT_ID, LANGUAGE). The business-key candidate is AR_STANDARD_TEXT_TL_U1, which extends that key with ZD_EDITION_NAME to guarantee a single translated row per standard text, per language, per edition.

Common Use Cases and Queries

Functional consultants and developers query this table when generating statements, verifying which languages a standard text has been translated into, or auditing statement content for a specific operating unit. A typical join pairs the translation row with its base definition:

• Retrieve statement text in a specific language: SELECT text FROM ar_standard_text_tl WHERE standard_text_id = :id AND language = 'US';
• Identify untranslated standard texts by comparing base and translation row counts per LANGUAGE.
• Reporting on statement content: join AR_STANDARD_TEXT_TL to AR_STANDARD_TEXT_B on STANDARD_TEXT_ID to display message name alongside translated text for user-facing extracts and BI Publisher statement templates.
• Migration and setup validation: extract all rows for a target language to confirm post-clone or post-patch translation coverage.

Because the table is keyed by language, reports intended for a multilingual customer base should filter on LANGUAGE and, in 12.2, on the active ZD_EDITION_NAME to avoid returning rows from inactive editions.

Related Objects

• AR_STANDARD_TEXT_B — The base MLS table holding the language-independent definition; joined on STANDARD_TEXT_ID.
• AR_STANDARD_TEXT_VL — The MLS view that joins the base and translation rows, exposing TEXT in the session or user-selected language; this is the view most application queries should reference.
• AR_STANDARD_TEXT_TL_PK / AR_STANDARD_TEXT_TL_U1 — Primary key and unique index constraints enforcing uniqueness of STANDARD_TEXT_ID, LANGUAGE, and edition.
• AR_STATEMENTS — Statement definitions that reference standard texts used during statement printing.
• FND_LANGUAGES — Reference table validating the LANGUAGE code values stored in this table.
• FND_APPLICATION / FND_ORACLE_USERID — Supporting audit and responsibility context for the CREATED_BY and LAST_UPDATED_BY columns.

No database-level foreign keys to these objects are documented for AR_STANDARD_TEXT_TL; the relationships above are maintained through the MLS framework, joins, and application logic rather than enforced referential constraints.