Results for “jtf_task_templates_tl”

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

Overview

JTF_TASK_TEMPLATES_TL is the translation table for the Oracle CRM Foundation (JTF) task template entity in Oracle E-Business Suite 12.1.1 and 12.2.2. While the base table (referenced in the documentation as JTF_TASKS_B, with the template entity materialized as JTF_TASK_TEMPLATES_B) holds language-independent template attributes, this companion table stores the language-dependent descriptive text required for Multi-Language Support (MLS). Each template can therefore carry a localized TASK_NAME and DESCRIPTION for every installed language, enabling global deployments to present task template content in the end user's session language.

The object is owned by the JTF schema and is classified as VALID in the ETRM dictionary. Its role is narrow but essential: it is the runtime source of translated template captions rendered in CRM task and calendar interfaces, and it is the join target whenever a report or concurrent program must return a template name in a specific language rather than the base-language value.

The ETRM metadata annotates the object with a heuristic Data Vault classification of standalone. In Data Vault terms this suggests modeling the table as an independent satellite-like structure attached to the template hub rather than as a link, since its grain is the template plus language combination and it carries purely descriptive attributes. This is offered as a modeling suggestion only; the physical implementation is a standard EBS MLS translation table.

Key Information Stored

The table contains twelve documented columns. The primary key, JTF_TASK_TEMPLATES_TL_PK, is the composite (TASK_TEMPLATE_ID, LANGUAGE). TASK_TEMPLATE_ID is the surrogate identifier of the parent template and also the foreign key back to the base entity; LANGUAGE is the Oracle language code (for example, US or JA) identifying the locale of the translated row.

• TASK_TEMPLATE_ID — surrogate key linking the translation row to its base template record.
• LANGUAGE — the NLS language code; together with TASK_TEMPLATE_ID it forms the primary key.
• SOURCE_LANG — the language of the source record from which this translation was derived; used by the MLS translation framework to identify the originating language.
• TASK_NAME — the translated display name of the task template, the primary business-facing attribute.
• DESCRIPTION — the translated long description of the template.
• ZD_EDITION_NAME — the editioning column used by the EBS online patching architecture; it is part of the unique index JTF_TASK_TEMPLATES_TL_U1 (TASK_TEMPLATE_ID, LANGUAGE, ZD_EDITION_NAME), which serves as the business-key candidate beyond the physical primary key.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing the security group (operating unit) context under which the row is visible.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification and the login under which it occurred.

Common Use Cases and Queries

The most common requirement is retrieving a template name in the user's language. A typical query joins the base table to the translation table on the template ID and constrains the language:

SELECT b.task_template_id, t.task_name, t.description
FROM jtf_task_templates_b b, jtf_task_templates_tl t
WHERE b.task_template_id = t.task_template_id
AND t.language = USERENV('LANG');

Reporting use cases include multilingual template inventory listings, translation completeness audits that compare jtf_task_templates_tl against jtf_task_templates_b to detect missing languages, and seeded-data verification after upgrades or patches. Because ZD_EDITION_NAME participates in the unique index, queries run under the editioning views used in 12.2.2 online patching behave consistently with prior releases, but direct queries against the table should be aware of the edition column when duplicate physical rows may exist across editions. Note that inserts into this table should generally be performed through the seeded template setup or the DML that maintains the base record, since MLS tables must be kept synchronized with their base entity.

Related Objects

• JTF_TASK_TEMPLATES_B — the base (language-independent) template table; joined on TASK_TEMPLATE_ID.
• JTF_TASK_TEMPLATES_VL — the MLS view that unions base and translation data and is the preferred query entry point.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID to scope row visibility by security group.
• JTF_TASKS_B / JTF_TASKS_TL — related task entities whose templates drive task creation defaults.
• FND_LANGUAGES — defines the valid LANGUAGE values used in this table.
• FND_APPLICATION / JTF product registrations — govern the schema and MLS configuration that control translation behavior for this object.