Search Results fnd_irep_classes_tl




Overview
Explore in AI Chat

Overview

FND_IREP_CLASSES_TL is the translation (TL) table for the IREP Classes table within the Oracle E-Business Suite Application Object Library (FND) product. It resides in the APPLSYS schema and is documented as VALID in ETRM for release 12.2.2, with equivalent behavior in 12.1.1. IREP refers to Oracle's Internet Reporting / integrated reporting infrastructure used to categorize and publish reports through the EBS framework. The base definition of each IREP class is held in FND_IREP_CLASSES; the corresponding translatable text — the display name and short description — is stored here, one row per installed language per class.

In Oracle EBS, TL tables conform to the Multilingual Support (MLS) architecture. Every translatable entity carries a language-independent definition row plus one translation row for each active language, distinguished by the LANGUAGE and SOURCE_LANG columns. Applications then resolve the correct row at runtime based on the session language, or fall back to the source language when a translation is missing.

Under the heuristic Data Vault classification mined from the foreign key structure, FND_IREP_CLASSES_TL is treated as standalone. In practice, because it carries descriptive attributes keyed by CLASS_ID and effective language, a Data Vault model would most naturally treat it as a satellite attached to the FND_IREP_CLASSES hub, with the language acting as a multi-active discriminator. This is a modeling suggestion only; no independent hub or link role is implied by the documented metadata.

Key Information Stored

The table exposes 12 documented columns. The most significant for consumers are:

  • CLASS_ID — The identifier of the IREP class. It is the component that ties each translation row back to the base definition row in FND_IREP_CLASSES.
  • LANGUAGE — The language of the translated text, stored as an Oracle language code (for example, US for American English). This is the discriminator that makes each row uniquely a translation rather than a duplicate definition.
  • SOURCE_LANG — The language in which the row was originally entered. It identifies the source of truth for the text and drives the MLS fallback behavior when a requested translation is absent.
  • DISPLAY_NAME — The translated, user-facing name of the IREP class. This is the primary attribute presented to end users in reporting and publishing screens.
  • SHORT_DESCRIPTION — The translated short description accompanying the class, used in pick lists and selection dialogs.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns that audit row creation and modification.
  • SECURITY_GROUP_ID — Identifies the security group that governs access to the row; it references FND_SECURITY_GROUPS, which is the sole documented foreign key on the table.
  • ZD_EDITION_NAME — The edition identifier supporting Oracle's Edition-Based Redefinition (EBR) capabilities, present in 12.2.x.

The unique index FND_IREP_CLASSES_TL_U1 covering (CLASS_ID, LANGUAGE, ZD_EDITION_NAME) is the documented business-key candidate; it enforces one translation per class per language per edition. CLASS_ID is the effective parent reference rather than a surrogate key generated within this table.

Common Use Cases and Queries

The table is consumed whenever IREP class names or descriptions must be rendered in the user's language, and by administrative queries that audit translation coverage. A typical retrieval joins the base table to the translation table for a specific language:

  • Resolving translated class names — Join FND_IREP_CLASSES to FND_IREP_CLASSES_TL on CLASS_ID = CLASS_ID where LANG is the session language and SOURCE_LANG is the base language.
  • Translation coverage audit — Compare the count of rows per CLASS_ID against the number of installed languages to find classes lacking translations.
  • Reporting extracts — Feed reporting metadata warehouses by selecting CLASS_ID, LANGUAGE, DISPLAY_NAME, and SHORT_DESCRIPTION alongside the base attributes.
  • Change tracking — Use LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recently modified classes as part of migration validation or audit against the source environment.
  • Security scoping — Filter by SECURITY_GROUP_ID to confirm class visibility in a secured reporting setup.

Related Objects

The following objects depend on or reference FND_IREP_CLASSES_TL. The relationships below reflect the documented foreign key plus the surrounding IREP framework:

  • FND_IREP_CLASSES — The base, language-independent table. It is the owner of CLASS_ID and the primary join partner for all translation lookups.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID; the documented FK. It governs access to IREP class rows.
  • FND_LANGUAGES — Provides the valid values and metadata for LANGUAGE and SOURCE_LANG, enabling joins that resolve language codes to names.
  • FND_IREP_OBJECTS — Related reporting definition structures that reference the IREP class hierarchy, sharing CLASS_ID-based context.
  • FND_IREP_CLASSES_TL historical/audit views — MLS-aware views and reporting extracts that join the base and translation tables transparently for display purposes.

Because the table is small and purely descriptive, most integration work occurs through the base class table and the MLS views rather than direct DML against this table.