Search Results jtf_task_date_types_tl




Overview
Explore in AI Chat

Overview

JTF_TASK_DATE_TYPES_TL is the translation (language) table that stores multilingual, descriptive text for the task date type definitions held in the base table JTF_TASK_DATE_TYPES_B. It resides in the JTF schema, part of the CRM Foundation (JTF) product family, and is classified as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store all columns and data required for Multi-Language Support (MLS), enabling date type names and descriptions to be presented in each installed language.

Under a heuristic Data Vault classification, this table is satellite-leaning. It carries the descriptive, language-dependent attributes of a parent business entity (the date type) rather than representing a standalone hub or an associative link. From a modeling perspective, JTF_TASK_DATE_TYPES_B would act as the hub, and JTF_TASK_DATE_TYPES_TL would serve as its language-specific satellite, keyed by the parent identifier plus LANGUAGE.

Key Information Stored

The table holds 11 documented columns. The most significant are:

  • DATE_TYPE_ID — Surrogate identifier linking each translation row to its parent date type definition in JTF_TASK_DATE_TYPES_B. It forms part of the primary key.
  • LANGUAGE — The installed language code for the translation; the second component of the primary key.
  • DATE_TYPE — The translated name of the date type, the primary user-facing text element.
  • DESCRIPTION — The translated descriptive text for the date type.
  • SOURCE_LANG — Indicates the source language of the record, supporting MLS behavior.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level security/access partitioning.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency information.

The surrogate primary key is JTF_TASK_DATE_TYPES_TL_PK, defined over (DATE_TYPE_ID, LANGUAGE). A unique index, JTF_TASK_DATE_TYPES_TL_U1, also covers the same (DATE_TYPE_ID, LANGUAGE) combination, making it the documented business-key candidate that guarantees one translation per date type per language.

Common Use Cases and Queries

Because the table supports MLS, typical usage joins it to the base table and filters by the runtime language. A common reporting pattern retrieves the localized date type name:

  • Lookup of translated date type labels for task due-date or start-date picklists.
  • Extracting a full language-by-language translation matrix for audit or migration purposes.
  • Verifying completeness of translations across installed languages.

A representative query pattern joins the base and translation tables on DATE_TYPE_ID and constrains LANGUAGE to the session or reporting language:

  • SELECT b.DATE_TYPE_ID, t.DATE_TYPE, t.DESCRIPTION FROM JTF_TASK_DATE_TYPES_B b, JTF_TASK_DATE_TYPES_TL t WHERE b.DATE_TYPE_ID = t.DATE_TYPE_ID AND t.LANGUAGE = USERENV('LANG').
  • Identify missing translations: compare base rows against translation rows where no matching LANGUAGE record exists.

Related Objects

The following objects are most significant in relation to this table:

  • JTF_TASK_DATE_TYPES_B — The base table holding language-independent date type definitions; joined on DATE_TYPE_ID. Referenced by the documented foreign key.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, used for access control.
  • JTF_TASKS_B — The task base table whose documentation this group of date type objects supports within the CRM Foundation task model.
  • Task-related JTF API packages — PL/SQL APIs that read translated date types when rendering task date attributes.
  • FND_LANGUAGES — Provides the valid LANGUAGE codes referenced logically by the LANGUAGE column.

Oracle proprietary and confidential information applies to the underlying metadata.