Search Results jtf_task_statuses_tl




Overview
Explore in AI Chat

Overview

JTF_TASK_STATUSES_TL is the translation (language) table that accompanies JTF_TASKS_B and, more specifically, the task status base table in the JTF — CRM Foundation product. Its documented role is to store all columns and data required for Multi-Language Support, allowing a single task status identifier to carry locale-specific text such as names and descriptions. The table is owned by the JTF schema and is flagged as VALID in the ETRM metadata for 12.1.1 / 12.2.2.

Its primary key, JTF_TASK_STATUSES_TL_PK, is composed of TASK_STATUS_ID and LANGUAGE. The heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms this suggests the object behaves as a reference or lookup table rather than a transaction hub, link, or pure satellite; the multi-language rows effectively act as localized descriptors attached to a status identifier, while the language column supplies the differentiating key.

Key Information Stored

The table contains 12 documented columns. The most operationally significant are:

  • TASK_STATUS_ID — surrogate identifier tying the row to the corresponding base task status record and part of the composite primary key.
  • LANGUAGE — the language/locale code, completing the primary key and enabling multilingual storage.
  • SOURCE_LANG — indicates the source language of the translated text, used by the translation framework to track origin.
  • NAME — the translated status name displayed to users in the target language.
  • DESCRIPTION — the translated long description of the status.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant / security-group isolation.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last changed each row.
  • ZD_EDITION_NAME — editioning column supporting Online Patching in EBS 12.2, absent from the earlier 12.1.1 architecture.

Two unique indexes are documented: the primary key JTF_TASK_STATUSES_TL_PK (TASK_STATUS_ID, LANGUAGE) and JTF_TASK_STATUSES_TL_U1 (TASK_STATUS_ID, LANGUAGE, ZD_EDITION_NAME). The U1 index is the business-key candidate under the editioning model.

Common Use Cases and Queries

Typical usage resolves the localized name of a task status for a given language, or lists all translations for a status identifier.

  • Retrieve the translated name for one status and language:
    SELECT name, description FROM jtf.jtf_task_statuses_tl WHERE task_status_id = :id AND language = USERENV('LANG');
  • List all available translations for a status:
    SELECT language, name FROM jtf.jtf_task_statuses_tl WHERE task_status_id = :id ORDER BY language;
  • Detect missing translations by comparing against defined statuses in the base table.
  • Feed multilingual status pick lists and LOVs in CRM task and activity screens.

Reporting should always constrain by LANGUAGE to avoid duplicate rows, and should join back to the base status table on TASK_STATUS_ID.

Related Objects

  • JTF_TASKS_B — the base table this translation table documents; joined on TASK_STATUS_ID.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security-group isolation.
  • FND_LANGUAGES — the standard source of valid LANGUAGE values used in the key.
  • JTF_TASK_STATUSES_B / base status table — parent records supplying the surrogate TASK_STATUS_ID.
  • FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — context for the JTF CRM Foundation product registration.
  • ZD_EDITION_NAME / AD_ZD_* editioning objects — used during Online Patching in 12.2.

The table should be treated as a read-mostly translation store maintained through the CRM Foundation translation utilities rather than direct DML.