Search Results jtf_task_references_tl




Overview
Explore in AI Chat

Overview

JTF_TASK_REFERENCES_TL is a translation table within the JTF (CRM Foundation) schema of Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose in the ETRM metadata is to serve as the Multi-Language Support (MLS) translation table for JTF_TASKS_B, storing the language-dependent descriptive columns associated with task reference records. In a standard MLS design, the base table holds language-independent attributes and the "_TL" companion holds translated text keyed by language code, allowing a single logical record to present different text values depending on the session's NLS configuration.

The heuristic Data Vault classification mined from the foreign-key structure identifies this object as standalone, meaning no parent FK dependencies were detected beyond the security group reference. As a modeling suggestion, this classification is somewhat unusual for a translation table, which would normally be modeled as a satellite hanging off the task reference hub or a language-dependent link. The absence of a strong FK to the base task reference table in the mined metadata may reflect unenforced or disabled constraints rather than a true absence of a relationship; implementers should validate the logical dependency on JTF_TASK_REFERENCES_B directly in the database before relying on the classification for lineage work.

Key Information Stored

The table contains 10 documented columns. The primary key, JTF_TASK_REFERENCES_TL_PK, is composite and comprises TASK_REFERENCE_ID and LANGUAGE. This is the surrogate-and-language combination that uniquely identifies each translated row. A second unique index, JTF_TASK_REFERENCES_TL_U1, is defined on the identical column pair (TASK_REFERENCE_ID, LANGUAGE), which means the business-key candidate and the primary key are effectively coextensive — there is no separate natural business key beyond the identifier plus language.

  • TASK_REFERENCE_ID — the identifier linking the translated row to its corresponding task reference record; part of both the PK and the unique index.
  • LANGUAGE — the NLS language code identifying which translation this row carries; the second component of the PK and unique index.
  • SOURCE_LANG — indicates the source language of the translated text, used by the MLS framework to track translation provenance.
  • USAGE — a usage or context indicator for the translated reference entry.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or operating-unit data isolation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing insert and update attribution and timing.

Notably, the documented column list does not enumerate a translated text or description column, even though the table's stated purpose is to hold language-dependent data. This is a common documentation gap for _TL tables; the actual translated attribute (typically a NAME or DESCRIPTION column) should be confirmed against the live data dictionary using ALL_TAB_COLUMNS.

Common Use Cases and Queries

The primary use case is resolving translated task reference text for a user's current language. A typical query joins the translation table to the base table and filters on the session language, with a fallback when no translation exists:

SELECT b.task_reference_id,
       NVL(tl.description, b.description) AS display_text
FROM   jtf_task_references_b b,
       jtf_task_references_tl tl
WHERE  b.task_reference_id = tl.task_reference_id (+)
AND    tl.language (+) = USERENV('LANG');

Reporting scenarios include auditing which languages have been populated for each reference, identifying untranslated records, and validating that every TASK_REFERENCE_ID has at least one row for each enabled language. A coverage query can be expressed as a count of distinct LANGUAGE values grouped by TASK_REFERENCE_ID, compared against the set of installed languages in FND_LANGUAGES. Because both the PK and U1 index cover the same columns, lookups by TASK_REFERENCE_ID plus LANGUAGE are optimally indexed; queries filtering on LANGUAGE alone will not use the leading column efficiently.

Related Objects

  • JTF_TASKS_B — the documented base table for which this object is the translation companion; logically related through TASK_REFERENCE_ID.
  • JTF_TASK_REFERENCES_B — the presumed language-independent base table for task references, joined on TASK_REFERENCE_ID.
  • FND_SECURITY_GROUPS — referenced by the confirmed foreign key SECURITY_GROUP_ID, providing data security grouping.
  • FND_LANGUAGES — supplies the installed language codes validated against the LANGUAGE column.
  • JTF_TASK_REFERENCES_TL_PK / JTF_TASK_REFERENCES_TL_U1 — the primary key constraint and unique index that enforce row uniqueness on TASK_REFERENCE_ID and LANGUAGE.