Results for “jtf_tasks_tl”

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

Overview

JTF_TASKS_TL is the translation (language) table for JTF_TASKS_B within the JTF — CRM Foundation product of Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to store all columns and data required for Multi-Language Support (MLS), allowing task definitions to be presented in the session or installation language of the user. In Oracle EBS, any base table that requires translated descriptive text is paired with a "_TL" companion table; JTF_TASKS_B holds the language-independent attributes, while JTF_TASKS_TL holds the language-dependent text keyed by TASK_ID and LANGUAGE. The object is owned by the JTF schema and is documented as VALID in ETRM 12.2.2 with a physical schema of 12 columns.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as standalone. Where the surrounding CRM task model is concerned, JTF_TASKS_TL can be modelled as a satellite attached to the task hub (JTF_TASKS_B), since it carries descriptive, language-qualified attributes (TASK_NAME, DESCRIPTION) that describe the same business key rather than introducing new relationships. The classification is a modeling suggestion only; the object does contain one documented foreign key to FND_SECURITY_GROUPS, which is an operational attribute rather than a true business relationship.

Key Information Stored

The table is keyed by a composite primary key, JTF_TASKS_TL_PK, defined on (TASK_ID, LANGUAGE). A second unique index, JTF_TASKS_TL_U1, is also defined on (TASK_ID, LANGUAGE), confirming the business-key candidate for this translation object. The most significant columns are:

• TASK_ID — Surrogate/foreign key to the base task record in JTF_TASKS_B; part of the primary key.
• LANGUAGE — The language code qualifying the translated row; part of the primary key and the MLS discriminator.
• SOURCE_LANG — The language in which the source text was originally authored, used by the translation framework to identify rows pending translation.
• TASK_NAME — The translated name of the task, the primary user-visible label.
• DESCRIPTION — The translated long description of the task.
• REJECTION_MESSAGE — Language-specific message text associated with task rejection handling.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces multi-tenant/group data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns providing audit and concurrency information.

The surrogate key (TASK_ID, LANGUAGE) should be distinguished from the business-key candidate expressed by JTF_TASKS_TL_U1; in practice they are the same column pair, which is typical for MLS translation tables.

Common Use Cases and Queries

The most frequent usage is joining translated text to the base task row for a specific language. A typical query returns the task name and description for the current session language:

• Language-specific task lookup: SELECT b.task_id, t.task_name, t.description FROM jtf.jtf_tasks_b b, jtf.jtf_tasks_tl t WHERE b.task_id = t.task_id AND t.language = USERENV('LANG');
• Translation completeness reporting: SELECT task_id, language, source_lang FROM jtf.jtf_tasks_tl WHERE source_lang <> language ORDER BY task_id;
• Security-filtered extraction: SELECT t.task_id, t.task_name FROM jtf.jtf_tasks_tl t WHERE t.security_group_id = :p_security_group_id;
• Audit/change tracking: SELECT task_id, language, last_updated_by, last_update_date FROM jtf.jtf_tasks_tl WHERE last_update_date >= :p_since;

These patterns support CRM task list reports, localization audits, translation workflow monitoring, and security-group-scoped reporting.

Related Objects

• JTF_TASKS_B — Base task table; joined on TASK_ID, the parent of this translation row.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; governs data visibility.
• JTF_TASKS_VL / JTF_TASKS_V — MLS views that join JTF_TASKS_B and JTF_TASKS_TL to expose translated task data.
• JTF_TASKS_VL / JTF_OBJECTS_B — Related CRM Foundation task and object definitions used when building task lists.
• FND_LANGUAGES — Source of valid LANGUAGE and SOURCE_LANG codes.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Context for the JTF application owning these tasks.

Queries should always constrain by LANGUAGE to avoid returning multiple translated rows per task, and should rely on the (TASK_ID, LANGUAGE) key for deterministic joins.