Search Results fnd_object_instance_sets_tl




Overview
Explore in AI Chat

Overview

FND_OBJECT_INSTANCE_SETS_TL is the translation subtable for Object Instance Sets in Oracle E-Business Suite, owned by the APPLSYS schema and delivered as part of the FND — Application Object Library product. An Object Instance Set defines a named collection of metadata instances that Oracle EBS uses in conjunction with configuration, personalization, and migration utilities. Because display-oriented attributes must be presented in the user's running language, the base definition is stored in a language-neutral parent table while the translatable text is held here, segmented by LANGUAGE.

The table resides in APPLSYS and is documented with 11 columns in the ETRM 12.2.2 physical schema; the same structure is valid in 12.1.1 and 12.2.2. Its primary key, SYS_C00134090, is composed of INSTANCE_SET_ID and LANGUAGE. A unique business-key index, FND_OBJECT_INSTANCE_SETS_TL_U1, extends this to INSTANCE_SET_ID, LANGUAGE, and ZD_EDITION_NAME. Mined from its foreign-key structure, the heuristic Data Vault classification for this object is standalone; a modeling suggestion therefore treats it as a self-contained reference or descriptive table rather than a hub, link, or satellite, though in practice it functions as a translation satellite attached to its base object instance set record.

Key Information Stored

The documented columns fall into three logical groups. The first is the identity and language key: INSTANCE_SET_ID identifies the parent object instance set, LANGUAGE identifies the language of the translated row, and SOURCE_LANG records the source language from which the translation originated. ZD_EDITION_NAME supports the editioning mechanism used in Online Patching environments, ensuring translations are scoped to the correct edition.

The second group carries the actual user-facing text: DISPLAY_NAME holds the translated name shown in Oracle EBS user interfaces and lookup lists, while DESCRIPTION holds the translated descriptive text. These are the only textual attributes defined for this table.

The third group comprises standard Oracle EBS audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These track who created and last modified each translated row and remain consistent across all APPLSYS-translated tables.

The surrogate primary key (INSTANCE_SET_ID, LANGUAGE) guarantees one translated row per instance set per language. The unique index FND_OBJECT_INSTANCE_SETS_TL_U1 adds ZD_EDITION_NAME, confirming that a single instance set can carry distinct translations per edition, which matters when patch editions run concurrently. No independent business-key column exists outside the composite; the effective business key is the combination of the parent identifier and language.

Common Use Cases and Queries

The most frequent scenario is retrieving the localized display name of an object instance set for a specific session language. A join between the translation subtable and its base table on INSTANCE_SET_ID, filtered by LANGUAGE, returns the correct text:

  • Querying display names: SELECT t.INSTANCE_SET_ID, b., t.DISPLAY_NAME, t.DESCRIPTION FROM APPLSYS.FND_OBJECT_INSTANCE_SETS_TL t, APPLSYS.FND_OBJECT_INSTANCE_SETS_B b WHERE t.INSTANCE_SET_ID = b.INSTANCE_SET_ID AND t.LANGUAGE = USERENV('LANG');
  • Auditing translation completeness: compare counts per INSTANCE_SET_ID across expected languages to find missing DISPLAY_NAME rows.
  • Migration and configuration work: extract translation rows by INSTANCE_SET_ID for movement between environments.
  • Edition-aware reporting: filter on ZD_EDITION_NAME to isolate translations introduced by a specific patch edition.
  • Last-update tracking: use LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently changed translations.

Related Objects

The base (non-translated) parent table, FND_OBJECT_INSTANCE_SETS_B, is the principal related object, joining through INSTANCE_SET_ID; the _B table holds language-independent attributes while this _TL table holds translated text. The corresponding views FND_OBJECT_INSTANCE_SETS_VL and FND_OBJECT_INSTANCE_SETS_TL views (or their generated equivalents) typically join _B and _TL to present a complete, language-resolved record. The standard FND language tables, such as FND_LANGUAGES, support interpretation of the LANGUAGE and SOURCE_LANG columns. References to instance sets also appear in object and personalization metadata tables that consume INSTANCE_SET_ID as a foreign-key value. When querying, always pair this subtable with FND_OBJECT_INSTANCE_SETS_B and constrain LANGUAGE to avoid returning multiple translated rows.