Results for “jtf_task_types_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_TASK_TYPES_TL is the translation (multi-language support) table for the Oracle CRM Foundation task type entity in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the JTF schema and belongs to the JTF – CRM Foundation product family. Rather than holding the canonical definition of a task type, this table stores the language-dependent attributes — most notably the display name and description — for each task type defined in its base counterpart, JTF_TASKS_B. The presence of a dedicated translation table reflects Oracle's standard MLS (Multi-Language Support) architecture, in which language-neutral business rows live in a base table and translated text lives in a "_TL" companion keyed on the same entity identifier plus a LANGUAGE code. From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone; in dimensional-modeling terms it functions effectively as a language-specific descriptive satellite attached to the task type hub, since it carries descriptive attributes keyed by TASK_TYPE_ID and LANGUAGE without owning link relationships of its own.

Key Information Stored

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

• TASK_TYPE_ID — Surrogate/foreign identifier linking each translation row to its parent task type. Part of the composite primary key.
• LANGUAGE — The language code for which the NAME and DESCRIPTION values apply. Part of the composite primary key.
• SOURCE_LANG — The source language from which the translated value was derived, used by the MLS translation workflow.
• NAME — The translated, user-facing name of the task type, displayed in list-of-values and task entry screens.
• DESCRIPTION — The translated long description of the task type.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access control.
• ZD_EDITION_NAME — Editioning metadata column (part of the unique business key in 12.2.2).
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard WHO-column traceability.

The primary key is JTF_TASK_TYPES_TL_PK on (TASK_TYPE_ID, LANGUAGE). A unique index, JTF_TASK_TYPES_TL_U1 on (TASK_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), serves as the business-key candidate in the editioned 12.2.2 schema. The surrogate identity here is the TASK_TYPE_ID/LANGUAGE pair; the true business key is the combination including the edition name.

Common Use Cases and Queries

Typical usage centers on resolving the correct display text for a task type in a given language, and on reporting or auditing translation coverage. A common query joins the translation table to the base table to return the localized name:

• Resolving display names: SELECT tt.name FROM jtf_task_types_tl tt WHERE tt.task_type_id = :id AND tt.language = USERENV('LANG');
• Checking translation coverage: compare COUNT(*) in JTF_TASKS_B against rows in JTF_TASK_TYPES_TL for a LANGUAGE to find untranslated task types.
• Reporting localized task-type catalogs for a specific language, filtering on LANGUAGE and SECURITY_GROUP_ID.

Because the table is predominantly read-only reference data, reporting queries should always constrain LANGUAGE to avoid returning multiple rows per TASK_TYPE_ID.

Related Objects

• JTF_TASKS_B — The base task type table; its rows are translated by this table on TASK_TYPE_ID.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID to govern access.
• JTF_TASK_TYPES_VL — The MLS view that joins base and translation rows, commonly the preferred query target.
• JTF_TASKS_B / JTF_TASKS_TL — Parent task entity tables that consume task type values.
• JTF_TASK_TYPES_TL_PK / _U1 — Constraint and unique index objects enforcing key integrity.