Results for “fnd_objects_tl_u1”

12 results




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

Overview

APPLSYS.FND_OBJECTS_TL is the translation subtable for the FND_OBJECTS entity in Oracle E-Business Suite. FND_OBJECTS stores the base definition of every registered object in the application object library — including forms, functions, menus, and other metadata-driven constructs — while FND_OBJECTS_TL holds the language-specific display names and descriptive text for those objects. The suffix "_TL" denotes an MLS (Multi-Lingual Support) translation table, meaning one row exists per object per installed language, enabling EBS to present the same object definition in multiple locales without duplicating the base record.

The table resides in the APPLSYS schema, is registered as FND design data under the FND.FND_OBJECTS_TL object definition, and carries VALID status. Storage is allocated in the APPS_TS_SEED tablespace, consistent with the table's role as seeded, shipped metadata rather than transactional data. The physical model is a classic satellite pattern: the base object identity and structural attributes live in FND_OBJECTS, while the descriptive, language-dependent attributes live here. Following the heuristic Data Vault classification supplied in the metadata, FND_OBJECTS_TL is best modeled as a satellite attached to the FND_OBJECTS hub, since its rows are keyed by the parent object plus a language discriminator and carry only descriptive attributes.

Key Information Stored

The table contains eleven documented columns. The most consequential are:

  • OBJECT_ID (NUMBER, 15) — Foreign key to FND_OBJECTS and the first component of the primary key. It identifies which base object the translation row describes. Part of the primary key FND_OBJECTS_TL_PK (OBJECT_ID, LANGUAGE).
  • LANGUAGE (VARCHAR2) — The language code for which this row provides translation text; it is the second component of the primary key.
  • SOURCE_LANG (VARCHAR2) — The language from which the translation was derived (typically the source install language such as US).
  • DISPLAY_NAME (VARCHAR2, 240) — The translated display name of the object.
  • DESCRIPTION (VARCHAR2, 2000) — The translated long description of the object.
  • ZD_EDITION_NAME (VARCHAR2, 30) — Edition column supporting Edition-Based Redefinition (EBR), which is present in 12.2.x.
  • Standard WHO audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

The surrogate primary key is FND_OBJECTS_TL_PK (OBJECT_ID, LANGUAGE). A separate unique index, FND_OBJECTS_TL_U1, is defined on (OBJECT_ID, LANGUAGE, ZD_EDITION_NAME) in the APPS_TS_SEED tablespace, acting as the business-key candidate for the edition-aware model. Note that FND_OBJECTS_TL_U1 is a superset of the primary key, so any query navigating by OBJECT_ID should be supported by it.

Common Use Cases and Queries

The primary operational use is resolving an object's display name and description in a specific language. A typical join retrieves the English (or session-language) translation alongside the base object:

  • List all objects and their translated names for a language segment: SELECT o.object_id, t.display_name, t.description FROM fnd_objects o, fnd_objects_tl t WHERE o.object_id = t.object_id AND t.language = 'US'.
  • Detect missing translations for a locale by comparing FND_OBJECTS against FND_OBJECTS_TL for the target LANGUAGE.
  • Drive object discovery in personalization, function security menus, and metadata UI, where the runtime fetches DISPLAY_NAME via OBJECT_ID.
  • Audit seeded metadata changes using CREATION_DATE and LAST_UPDATE_DATE, and reconcile translation drift after upgrades or patches.

Because OBJECT_ID is indexed via FND_OBJECTS_TL_U1 and the primary key, filtered single-object lookups are efficient.

Related Objects

  • APPLSYS.FND_OBJECTS — The parent base table. Joined on FND_OBJECTS.OBJECT_ID = FND_OBJECTS_TL.OBJECT_ID.
  • APPLSYS.FND_OBJECTS_TL# — The editioning/underlying view reference noted in the dependency metadata.
  • FND_OBJECTS_VL — The translated view pattern that joins the base and _TL tables to expose MLS rows in a single result set.
  • Other _TL subtables (e.g., FND_MENUS_TL, FND_FORM_TL, FND_FUNCTION_TL) follow the same MLS satellite pattern and are frequently queried together for localization reporting.
  • FND application APIs and concurrent programs that load seed data, such as those driven by FNDLOAD, read and write FND_OBJECTS and FND_OBJECTS_TL directly.