Search Results jtf_objects_tl_u1

Overview

JTF.JTF_OBJECTS_TL is the translation table for JTF_OBJECTS_B within the Oracle E-Business Suite JTF (Java Technology Foundation) schema. It stores language-specific, MLS-enabled descriptive text for the object registration records maintained in the base table. In EBS 12.1.1 and 12.2.2, this table supplies the multilingual strings that drive the display of object metadata, such as object names, descriptions, and list-of-values (LOV) window and column titles used by the CRM and application framework components.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as a seeded reference object carrying translation data rather than high-volume transactional data. The primary key is composed of OBJECT_CODE and LANGUAGE, with an additional unique index, JTF_OBJECTS_TL_U1, defined on OBJECT_CODE, LANGUAGE, and ZD_EDITION_NAME. From a data modeling perspective, the heuristic Data Vault classification is satellite-leaning: the table behaves as a descriptive satellite hanging off the base entity JTF_OBJECTS_B, keyed by the parent business key (OBJECT_CODE) with language as the additional qualifying context. In 12.2.2, the ZD_EDITION_NAME column supports the editioning and online patching architecture, so the same business key can carry multiple edition-tagged rows.

Key Information Stored

• OBJECT_CODE — the object type identifier; this is the substantive business key matching the parent row and is the leading column of the primary key and unique index.
• LANGUAGE — the language to which the record is translated; combined with OBJECT_CODE it forms the unique business key JTF_OBJECTS_TL_U1.
• ZD_EDITION_NAME — the edition discriminator used in the 12.2 online patching model; the third column of the unique index JTF_OBJECTS_TL_U1.
• SOURCE_LANG — the language from which the translation was made, supporting MLS translation workflows.
• NAME — the display name of the source object in the target language.
• DESCRIPTION — a short description of the object type.
• LOV_WINDOW_TITLE — the localized title of the list-of-values window associated with the object.
• LOV_NAME_TITLE — the localized title of the name column shown in the LOV.
• LOV_DETAILS_TITLE — the localized title of the details column shown in the LOV.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns tracking row creation and modification.
• SECURITY_GROUP_ID — used in hosted environments; it is a foreign key to FND_SECURITY_GROUPS.

The surrogate primary key JTF_OBJECTS_TL_PK (OBJECT_CODE, LANGUAGE) should be distinguished from the business-key candidate represented by the unique index JTF_OBJECTS_TL_U1, which extends the same key with ZD_EDITION_NAME.

Common Use Cases and Queries

The most common scenario is joining the translation table to its base table to retrieve localized object metadata for a given language. A representative pattern is:

• SELECT t.OBJECT_CODE, t.NAME, t.DESCRIPTION FROM JTF.JTF_OBJECTS_TL t WHERE t.LANGUAGE = USERENV('LANG');
• Joining to the base: SELECT b.OBJECT_CODE, t.NAME, t.LOV_WINDOW_TITLE FROM JTF.JTF_OBJECTS_B b, JTF.JTF_OBJECTS_TL t WHERE b.OBJECT_CODE = t.OBJECT_CODE AND t.LANGUAGE = :lang;
• Verifying translation completeness by comparing source and target language rows, using SOURCE_LANG against LANGUAGE.
• Extracting LOV window and column titles for building or auditing application LOV definitions.

Reporting use cases include audit reports on who created or last updated translations (via the WHO columns), hosted-environment security filtering on SECURITY_GROUP_ID, and edition-aware extracts that include ZD_EDITION_NAME in 12.2.2. Because this table carries seed data, direct DML should normally be left to the supported application maintenance or patching mechanisms rather than manual updates.

Related Objects

• JTF.JTF_OBJECTS_B — the base table; joined on OBJECT_CODE (OBJECT_CODE → JTF_OBJECTS_B). This is the primary parent relationship.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID (SECURITY_GROUP_ID → FND_SECURITY_GROUPS) for hosted environment isolation.
• FND_USER — related indirectly through CREATED_BY and LAST_UPDATED_BY, which are foreign keys to FND_USER.USER_ID.
• FND_LOGINS — related through LAST_UPDATE_LOGIN, a foreign key to FND_LOGINS.LOGIN_ID.
• JTF_OBJECTS_TL_U1 — the unique index on OBJECT_CODE, LANGUAGE, ZD_EDITION_NAME, the object most commonly referenced when the user searched for "jtf_objects_tl_u1".
• JTF_OBJECTS_TL_PK — the primary key constraint (OBJECT_CODE, LANGUAGE) that enforces one translation row per object per language.

No database objects are documented as being referenced by JTF_OBJECTS_TL itself beyond the foreign keys above; the dependencies flow from this table toward the base and security objects, and downward through the indexes and constraints defined on it.