Results for “oke_terms_tl”

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

Overview

OKE_TERMS_TL is a translation (TL) table within the OKE – Project Contracts module of Oracle E-Business Suite, holding the multi-lingual descriptive information for contract terms and conditions. It is the language-specific companion to the base OKE_TERMS table. Every term defined in Project Contracts carries one or more translated rows in OKE_TERMS_TL, one per installed language, so that term names and descriptions can be presented to users in their session language. The table is owned by the OKE schema and is classified as VALID in release 12.1.1 and 12.2.2.

From a dimensional-modeling perspective, the mined Data Vault classification is standalone. This suggests the table can be treated as a small reference/satellite-style object rather than a hub or link; it does not participate in the FK structure of the contract model but rather provides descriptive attributes keyed to a shared business code plus a language. Its grain is one row per term code per language.

Key Information Stored

The table contains 11 documented columns. The most operationally significant are:

• TERM_CODE – The language-independent term identifier. It forms the leading element of the primary key and the business key linking back to the base OKE_TERMS table.
• LANGUAGE – The installed Oracle language code (for example, US, DE, FR) indicating the language of the translated text. Combined with TERM_CODE, it forms the primary key.
• TERM_NAME – The translated, user-facing name of the contract term. It is the second unique-key candidate and the value most often surfaced in list-of-values and reports.
• DESCRIPTION – The translated long description of the term, used in clause text and contract documentation.
• SOURCE_LANG – The language from which the current row was translated, supporting the Oracle translation framework.
• ZD_EDITION_NAME – The editioning column introduced by the EBS 12.2 online patching architecture. It is part of both documented unique indexes (OKE_TERMS_TL_U1 and OKE_TERMS_TL_U2) and must be considered in queries to isolate the runtime edition.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record who created and last changed each translated row.

The surrogate primary key OKE_TERMS_TL_PK is defined on (TERM_CODE, LANGUAGE). Business-key candidates are captured by the unique indexes OKE_TERMS_TL_U1 (TERM_CODE, LANGUAGE, ZD_EDITION_NAME) and OKE_TERMS_TL_U2 (TERM_NAME, LANGUAGE, ZD_EDITION_NAME). The U2 index enforces that no two terms share the same translated name within a language and edition.

Common Use Cases and Queries

Typical reporting needs center on retrieving human-readable term text. A standard query resolves a term in the user's language, falling back to the base language when a translation is absent:

• Populating term list-of-values and contract clause pickers with TERM_NAME filtered by LANGUAGE.
• Auditing which terms are translated and which remain in their source language using SOURCE_LANG.
• Extracting contract terms and their descriptions for legal documentation or term libraries.

A representative pattern:

SELECT t.TERM_CODE, t.TERM_NAME, t.DESCRIPTION
FROM OKE.OKE_TERMS_TL t
WHERE t.LANGUAGE = USERENV('LANG')
  AND t.ZD_EDITION_NAME = 'ORA$BASE';

In 12.2 environments, always constrain ZD_EDITION_NAME to the active edition to avoid duplicate rows produced by the editioning infrastructure.

Related Objects

• OKE_TERMS – The base term table; joined on TERM_CODE. OKE_TERMS_TL supplies the translated attributes for each base term row.
• OKE_TERMS_TL_PK / OKE_TERMS_TL_U1 / OKE_TERMS_TL_U2 – Primary and unique indexes enforcing term/language and translation-name integrity.
• OKE_CONTRACT_TERMS – Associates terms with contracts; resolves display text through TERM_CODE.
• OKE_TERMS_V (or equivalent views) – Language-joined views that expose base and translated attributes together for form and concurrent usage.
• OKE_TERM_API / OKE_TERM_PVT – Public and private term-definition APIs that insert and update both the base and translated rows.
• FND_LANGUAGES – Provides the valid installed language codes referenced by LANGUAGE.
• OKE_CONTRACT_HEADERS / OKE_CONTRACTS – Contract and header tables whose clause text draws term names from this table.