Search Results oke_object_attributes_tl




Overview
Explore in AI Chat

Overview

OKE_OBJECT_ATTRIBUTES_TL is a translation (TL) table in the OKE schema (Project Contracts) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the multi-lingual, descriptive text associated with contract attributes defined in the OKE module. In Oracle EBS, the "_TL" suffix designates a table that holds language-dependent columns—typically a NAME/DESCRIPTION pair—while the corresponding base table holds the language-independent structural columns. This separation allows the same contract attribute to be displayed in the user's session language without duplicating business logic per locale.

The object exists to hold the human-readable attribute name and description that appear in Project Contracts setup, attribute groups, and contract authoring pages. Because it is a child of an attribute definition rather than a transactional intersection, the ETRM metadata classifies it heuristically as standalone in Data Vault terms. From a dimensional-modeling perspective, this is best treated as a satellite attached to the language-independent contract-attribute hub: the descriptive text is a dependent, descriptive attribute keyed by the attribute's identity plus a language discriminators, making it a natural multi-active satellite rather than a true hub or link.

Key Information Stored

The table carries 12 documented columns. Only the most significant are described here.

  • DATABASE_OBJECT_NAME — Identifies the underlying database object (entity/view) that owns the attribute. This is a leading component of the primary key and of both unique indexes.
  • ATTRIBUTE_CODE — The internal, language-independent code for the attribute. Combined with DATABASE_OBJECT_NAME and LANGUAGE, it forms the primary key and is the stable identifier used by application logic and joins.
  • LANGUAGE — The language code for this translation row, the third PK component. Only one row per attribute per installed language typically exists.
  • ATTRIBUTE_NAME — The user-visible translated attribute label. This column appears in the business-key candidate index OKE_OBJECT_ATTRIBUTES_TL_U2.
  • DESCRIPTION — The translated long description or help text shown for the attribute.
  • SOURCE_LANG — The language in which the base (source) row was originally created, used by the Translation/MLS framework to identify the "owner" language row.
  • ZD_EDITION_NAME — Editioning column used by the EBS 12.2 online patching (Edition-Based Redefinition) architecture; present in both unique indexes.
  • The remaining columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are standard Oracle EBS WHO columns providing audit and concurrency information.

The surrogate primary key is OKE_OBJECT_ATTRIBUTES_TL_PK, defined over (DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, LANGUAGE). Two documented unique indexes act as business-key candidates: OKE_OBJECT_ATTRIBUTES_TL_U1 (DATABASE_OBJECT_NAME, ATTRIBUTE_CODE, LANGUAGE, ZD_EDITION_NAME) and OKE_OBJECT_ATTRIBUTES_TL_U2 (DATABASE_OBJECT_NAME, ATTRIBUTE_NAME, LANGUAGE, ZD_EDITION_NAME), the latter enforcing that the displayed name is unique per object/language.

Common Use Cases and Queries

Typical uses include localized display of contract attribute setup, troubleshooting missing translations, and reporting on attributes for a specific language or database object.

  • Retrieve translated attribute labels for one entity and language: 
    SELECT ATTRIBUTE_CODE, ATTRIBUTE_NAME, DESCRIPTION
FROM   OKE_OBJECT_ATTRIBUTES_TL
WHERE  DATABASE_OBJECT_NAME = :entity
AND    LANGUAGE = USERENV('LANG')
AND    ZD_EDITION_NAME = 'SET1';
  • Find attributes lacking a translation row: 
    SELECT b.ATTRIBUTE_CODE
FROM   OKE_OBJECT_ATTRIBUTES b,
       OKE_OBJECT_ATTRIBUTES_TL t
WHERE  b.ATTRIBUTE_CODE = t.ATTRIBUTE_CODE(+)
AND    b.DATABASE_OBJECT_NAME = t.DATABASE_OBJECT_NAME(+)
AND    NVL(t.LANGUAGE,'xx') = 'xx';
  • Reporting on all installed languages for an attribute to audit translation coverage.

Related Objects

The metadata identifies this as a standalone object with no outward foreign keys, but as a translation table it depends logically on several language-independent and MLS-framework objects. The most significant are described below, joined on the columns shared in the documented keys.

  • OKE_OBJECT_ATTRIBUTES (base attribute table) — The primary parent; joined on DATABASE_OBJECT_NAME and ATTRIBUTE_CODE.
  • OKE_OBJECT_ATTRIBUTES_VL — The MLS view that unions the base table with this TL table, the normal query access path for language-aware reads.
  • OKE_OBJECT_FORMS / OKE attribute-group setup tables — Consume attribute names and descriptions during contract authoring and setup, resolved through the attribute code.
  • FND_LANGUAGES — Provides the LANGUAGE valid values and source-language definitions used to populate and interpret SOURCE_LANG.
  • OKE_CONTRACT_ATTRIBUTES and related contract-attribute transactional tables — Reference attributes whose display text ultimately resolves to rows in this TL table.

Collectively, these relationships mean that OKE_OBJECT_ATTRIBUTES_TL should be joined through the base/MLS view rather than queried in isolation whenever a language-independent result is required.