Search Results jtf_task_references_tl_u1




Overview

JTF.JTF_TASK_REFERENCES_TL is the translation (multi-language support) table for the base table JTF.JTF_TASK_REFERENCES_B within the Oracle E-Business Suite 12.1.1 and 12.2.2 JTF (Common Technology Foundation) schema. It stores the language-dependent text attributes associated with task references — records that link a task to an external artifact such as a document, URL, or related entity. For every translatable row in the base table, the _TL table holds one row per installed language, enabling users in different locales to maintain their own descriptive text without duplicating the structural data.

In a heuristic Data Vault classification, this object behaves as a satellite: its key structure is a composite of the parent business key (TASK_REFERENCE_ID) plus the LANGUAGE discriminator, and it carries descriptive, timestamped, and who-column attributes that change independently of the parent entity. It is not an independent hub, and it participates in no foreign-key relationships other than an optional reference to FND_SECURITY_GROUPS.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • TASK_REFERENCE_ID (NUMBER) — Unique task reference identifier; the foreign key back to the base table and the leading column of the primary key.
  • LANGUAGE (VARCHAR2) — The language into which the text is translated; the second component of the primary key and of the unique index JTF_TASK_REFERENCES_TL_U1.
  • SOURCE_LANG (VARCHAR2) — The language from which the text was translated, used by the translation (TPS) framework to determine staleness.
  • USAGE (VARCHAR2, 2000) — User comment describing the usage of the reference; this is the principal translatable descriptive attribute.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing audit trail and row versioning.
  • SECURITY_GROUP_ID (NUMBER) — Used in hosted/multi-tenant environments; the only documented foreign key, referencing FND_SECURITY_GROUPS.

The composite primary key is JTF_TASK_REFERENCES_TL_PK (TASK_REFERENCE_ID, LANGUAGE). The unique index JTF_TASK_REFERENCES_TL_U1 covers the same two columns and is the business-key candidate that guarantees one translation row per task reference per language. There is no single-column surrogate key; the identifier is meaningful and inherited from the parent.

Common Use Cases and Queries

Typical usage is retrieving locale-specific descriptive text for a task reference while joining to the base table for the language-independent attributes. A reporting query returns only rows for the session's language:

  • Translation maintenance: insert or update a USAGE value for a specific LANGUAGE, and keep SOURCE_LANG synchronized so the TPS framework flags the row as current.
  • Locale-aware extraction: join JTF_TASK_REFERENCES_B to _TL on TASK_REFERENCE_ID and filter on LANGUAGE = userenv('LANG') or the FND language code.
  • Completeness auditing: identify base rows with no corresponding _TL row for an installed language (LEFT JOIN ... WHERE TL.TASK_REFERENCE_ID IS NULL).
  • Staleness detection: select rows where SOURCE_LANG <> the base row's source language, indicating pending re-translation.
  • Hosted-environment filtering: constrain by SECURITY_GROUP_ID when multiple operating units share the schema.

The canonical access path, as documented, is SELECT TASK_REFERENCE_ID, LANGUAGE, SOURCE_LANG, USAGE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, SECURITY_GROUP_ID FROM JTF.JTF_TASK_REFERENCES_TL;

Related Objects

Significant related objects include:

  • JTF.JTF_TASK_REFERENCES_B — The base table; join on TASK_REFERENCE_ID. All translation rows derive from this parent.
  • JTF.JTF_TASK_REFERENCES_TL# — The documented dependent object referenced by this table (internal/public synonym and dependency chain).
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for hosted-environment security partitioning.
  • FND_USER — Implicit reference for CREATED_BY and LAST_UPDATED_BY.
  • FND_LOGINS — Implicit reference for LAST_UPDATE_LOGIN.
  • JTF_TASKS / JTF_TASK_REFERENCES views and the JTF task-management APIs that populate and read translated reference text.

Because it carries no outgoing business foreign keys and only the SECURITY_GROUP_ID reference, the table's principal dependency is its parent base table, making it a straightforward satellite for translation and multi-language reporting.