Search Results jtf_task_date_types_tl_u1

Overview

JTF.JTF_TASK_DATE_TYPES_TL is the translation (multi-language support) table that accompanies JTF_TASK_DATE_TYPES_B within the Oracle E-Business Suite 12.1.1 and 12.2.2 Java Task Framework (JTF) schema. Its purpose is to store the language-dependent attributes for each task date type — specifically the display name and description — in every installed language, while the base table retains the language-independent definition. This separation is a standard Oracle EBS pattern: the "_B" table holds the entity and its non-translatable columns, and the "_TL" table holds the translatable text.

The table resides in the APPS_TS_SEED tablespace, reflecting that task date type text is typically seeded reference data rather than high-volume transactional data. Each row is uniquely identified by the combination of DATE_TYPE_ID and LANGUAGE, which forms the primary key (JTF_TASK_DATE_TYPES_TL_PK) and is enforced by the unique index JTF_TASK_DATE_TYPES_TL_U1. The DATE_TYPE_ID column is a foreign key to JTF_TASK_DATE_TYPES_B, and SECURITY_GROUP_ID references FND_SECURITY_GROUPS for hosted environments. From a Data Vault modeling perspective, this object is best classified as satellite-leaning: it carries descriptive, language-qualified attributes that hang off the parent task date type hub/entity in JTF_TASK_DATE_TYPES_B.

Key Information Stored

The most significant columns are as follows. DATE_TYPE_ID is the surrogate identifier linking back to JTF_TASK_DATE_TYPES_B and is one half of the composite primary key. LANGUAGE stores the language into which the text is translated, and together with DATE_TYPE_ID it forms the documented business-key candidate (unique index JTF_TASK_DATE_TYPES_TL_U1). SOURCE_LANG records the language from which the text was translated, supporting MLS maintenance. DATE_TYPE holds the translated name of the date type (VARCHAR2(30)), and DESCRIPTION holds its translated description (VARCHAR2(400)).

• DATE_TYPE_ID — surrogate/foreign key to the base table; part of the primary key.
• LANGUAGE — target translation language; part of the primary key and unique index.
• SOURCE_LANG — originating language for the translation.
• DATE_TYPE — translated display name of the task date type.
• DESCRIPTION — translated descriptive text.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, used in hosted/multi-tenant deployments.

Standard WHO audit columns are present: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These record authorship and change history and are maintained automatically by the framework.

Common Use Cases and Queries

Typical usage involves resolving the language-specific name of a task date type for display in forms, reports, or APIs. A common pattern joins the translation table to the base table and filters by the current session language. For example:

• Retrieving translated labels for a given language: SELECT t.DATE_TYPE_ID, t.DATE_TYPE, t.DESCRIPTION FROM JTF.JTF_TASK_DATE_TYPES_TL t WHERE t.LANGUAGE = USERENV('LANG').
• Listing all translations for a specific date type: SELECT DATE_TYPE_ID, LANGUAGE, DATE_TYPE FROM JTF.JTF_TASK_DATE_TYPES_TL WHERE DATE_TYPE_ID = :id.
• Auditing translation coverage by comparing row counts per LANGUAGE against the base table to detect missing translations.
• Reporting seeded reference data for date type configuration across installed languages.

Because the table is seeded, direct DML is generally discouraged; translations are maintained through the standard MLS/translation maintenance mechanisms rather than ad hoc inserts.

Related Objects

The following objects are most significant in relation to this table, based on the documented dependency and foreign key metadata:

• JTF.JTF_TASK_DATE_TYPES_B — the base table; joined on DATE_TYPE_ID and the parent of the translation rows.
• APPS.JTF_TASK_DATE_TYPES_TL — the APPS synonym/view used by application code to access this table.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted environment support.
• FND_USER — implicit relationship via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — implicit relationship via LAST_UPDATE_LOGIN.

Together these objects form the reference-data backbone that supplies language-aware task date type information to the JTF task management components in Oracle EBS.