Results for “jtf_task_templates_tl_u1”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF.JTF_TASK_TEMPLATES_TL is the translation (language) table that complements JTF.JTF_TASK_TEMPLATES_B within the Oracle E-Business Suite Foundation (JTF) product. Its documented purpose is to store all columns and data required for Multi-Language Support (MLS) of task templates. Task templates provide reusable definitions for tasks, and this table holds the translatable seed data — that is, the task name and description text — so the same logical task template can be presented in multiple installed languages.
The object is classified as VALID in the ETRM registry and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It is owned by the JTF schema and carries the FND Design Data reference JTF.JTF_TASK_TEMPLATES_TL. From a data modeling perspective, the mined relationship metadata classifies this table as standalone rather than a classic hub, link, or satellite, reflecting its role as a dependent translation table rather than a transactional integration point.
Key Information Stored
The physical schema documents 12 columns. The most significant are described below.
- TASK_TEMPLATE_ID (NUMBER) — the unique task template identifier. It is the surrogate parent key pointing back to the base table JTF_TASK_TEMPLATES_B.
- LANGUAGE (VARCHAR2) — the language to which the text is translated; identifies the specific translation row for a given template.
- SOURCE_LANG (VARCHAR2) — the language from which the text was translated, supporting the MLS source/target convention.
- TASK_NAME (VARCHAR2, length 80) — the translated task template name.
- DESCRIPTION (VARCHAR2, length 4000) — the translated description of the task.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row creation and last modification, with foreign keys to FND_USER and FND_LOGINS.
- SECURITY_GROUP_ID (NUMBER) — used in hosted environments and referencing FND_SECURITY_GROUPS.
- ZD_EDITION_NAME — the editioning column present in the 12.2.2 documented schema, supporting Edition-Based Redefinition.
The primary key is JTF_TASK_TEMPLATES_TL_PK over (TASK_TEMPLATE_ID, LANGUAGE). The unique index JTF_TASK_TEMPLATES_TL_U1 covers (TASK_TEMPLATE_ID, LANGUAGE, ZD_EDITION_NAME) and is the business-key candidate reported by the search. Because LANGUAGE forms part of the key, a template may hold at most one row per installed language.
Common Use Cases and Queries
The principal use of this table is language-specific retrieval of template text. Reporting queries typically join the translation table to the base table on TASK_TEMPLATE_ID and constrain LANGUAGE to the session or user language. A representative pattern is:
- Listing templates in a chosen language:
SELECT b.TASK_TEMPLATE_ID, t.TASK_NAME, t.DESCRIPTION FROM JTF.JTF_TASK_TEMPLATES_B b, JTF.JTF_TASK_TEMPLATES_TL t WHERE b.TASK_TEMPLATE_ID = t.TASK_TEMPLATE_ID AND t.LANGUAGE = :P_LANG; - Auditing translation coverage by comparing installed languages against rows returned here for each TASK_TEMPLATE_ID.
- Validating metadata and auditing WHO columns, for example filtering on LAST_UPDATE_DATE to identify recently retranslated content.
Because the row set is comparatively small (one row per template per language), full scans are inexpensive and are frequently used in setup and validation reports.
Related Objects
- JTF.JTF_TASK_TEMPLATES_B — the base table holding non-translatable template attributes; joined on TASK_TEMPLATE_ID.
- JTF_TASK_TEMPLATES_TL (APPS synonym/view) — the application-facing access point referenced by the ETRM listing.
- FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted deployments.
- FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY.
- FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
This table does not reference any database object beyond the foreign keys noted above, and it is referenced primarily through the base-template relationship and the APPS synonym.
-
Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support.
-
Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.2.2
Interface table to store data that needs to be displayed in Excel