Search Results jtf_objects_tl




Overview
Explore in AI Chat

Overview

JTF_OBJECTS_TL is the translation (multi-language) table for the CRM Foundation object registry owned by the JTF schema. In Oracle E-Business Suite 12.1.1 and 12.2.2, JTF_OBJECTS_B stores the language-independent definition of a registered CRM object, while JTF_OBJECTS_TL holds the language-dependent descriptive attributes — the object name, description, and the titles used by the List of Values (LOV) framework when the object is rendered in a specific language. Every row in JTF_OBJECTS_TL is keyed by OBJECT_CODE plus LANGUAGE, which together form the primary key constraint JTF_OBJECTS_TL_PK.

Because the table carries descriptive, translatable attributes that hang off a parent business entity rather than representing a business entity itself, the heuristic Data Vault classification is satellite-leaning. In a Data Vault model it would be treated as a satellite attached to the JTF_OBJECTS_B hub, with LANGUAGE acting as a driving key for the multi-active (multi-language) row set.

Key Information Stored

The documented physical schema for 12.2.2 contains 15 columns. The most significant include:

  • OBJECT_CODE — the business identifier of the CRM object; part of the primary key and the FK to JTF_OBJECTS_B.
  • LANGUAGE — the NLS language code; the second component of the primary key.
  • SOURCE_LANG — the language in which the row was originally authored, used by the translation framework to identify untranslated rows.
  • NAME — the display name of the object in the given language.
  • DESCRIPTION — the translatable description of the object.
  • LOV_WINDOW_TITLE — the window title shown when the object's LOV is invoked.
  • LOV_NAME_TITLE — the column heading for the name column in the LOV.
  • LOV_DETAILS_TITLE — the heading for the detail column in the LOV.
  • SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing multi-org/security-group isolation.
  • ZD_EDITION_NAME — the editioning column used by the 12.2 online patching (Edition-Based Redefinition) architecture.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The surrogate primary key is JTF_OBJECTS_TL_PK (OBJECT_CODE, LANGUAGE). The business-key candidate from the unique index is JTF_OBJECTS_TL_U1 (OBJECT_CODE, LANGUAGE, ZD_EDITION_NAME), which adds the editioning column to distinguish patched editions of the same translation row.

Common Use Cases and Queries

Typical usage resolves the display name and LOV titles for a CRM object in the session language. A join to the base table is the standard pattern:

  • Lookup of an object's localized name/description: SELECT t.NAME, t.DESCRIPTION FROM JTF_OBJECTS_TL t WHERE t.OBJECT_CODE = :code AND t.LANGUAGE = USERENV('LANG');
  • Detecting untranslated rows: compare LANGUAGE to SOURCE_LANG, or identify objects present in JTF_OBJECTS_B with no matching TL row.
  • LOV configuration auditing: report on LOV_WINDOW_TITLE, LOV_NAME_TITLE and LOV_DETAILS_TITLE to verify customized LOV captions.
  • Security-group-scoped reporting when multiple security groups are enabled.

In 12.2, EBR requires the query to resolve the correct edition; ZD_EDITION_NAME should be included when reconciling against the base table to avoid duplicate rows across editions.

Related Objects

  • JTF_OBJECTS_B — the base (language-independent) object registry; joined on OBJECT_CODE.
  • FND_SECURITY_GROUPS — the security group definition; joined on SECURITY_GROUP_ID.
  • JTF_OBJECTS_VL / JTF_OBJECTS_V — the translated and base views exposed to forms and OAF pages.
  • FND_LANGUAGES — provides the valid LANGUAGE values.
  • JTF_OBJECTS_TL_PK / JTF_OBJECTS_TL_U1 — the primary key constraint and unique index enforcing key integrity.