Results for “jtf_task_dates”

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

Overview

JTF_TASK_DATES is a CRM Foundation (JTF) transactional table within the Oracle E-Business Suite database, owned by the JTF schema and holding status VALID. Its stated purpose is to store the actual date values associated with a task: rather than persisting a fixed set of date columns directly on the task record, Oracle models task dates as repeating child rows, one per date type per task. This design allows the set of meaningful dates for a task (for example a due date, a start date, or a completion date) to be configured and extended through the JTF_TASK_DATE_TYPES_B lookup table rather than hard-coded.

The table is present in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 it is documented with 27 physical columns. Under the heuristic Data Vault classification mined from its foreign key structure, JTF_TASK_DATES is a link table, because it resolves the association between two independent business entities — a task and a task date type — while also carrying the descriptive date value. A Data Vault modeler would therefore treat TASK_ID and DATE_TYPE_ID as the hub references and DATE_VALUE as link-degenerate descriptive data.

Key Information Stored

The table's surrogate primary key is TASK_DATE_ID, enforced by the index JTF_TASK_DATES_PK. A second unique index, JTF_TASK_DATES_U1, also exists on TASK_DATE_ID, making it the documented business-key candidate for the row itself. The most significant columns are:

• TASK_DATE_ID — surrogate identifier and primary key for each task-date row.
• TASK_ID — foreign key to JTF_TASKS_B; identifies the parent task.
• DATE_TYPE_ID — foreign key to JTF_TASK_DATE_TYPES_B; identifies which configured date the row represents.
• DATE_VALUE — the actual date stored for the task/date-type combination; the core payload of the record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security-group filtering.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard JTF/CRM descriptive flexfield (DFF) columns for customer-defined extensions.

Common Use Cases and Queries

Typical usage is to retrieve the resolved dates for a task, or to report on tasks by a particular date type. A join to the date-type table provides the human-readable meaning of DATE_TYPE_ID:

• List all dates for a task: SELECT d.task_date_id, t.name, d.date_value FROM jtf_task_dates d, jtf_task_date_types_b t WHERE d.date_type_id = t.date_type_id AND d.task_id = :task_id;
• Find overdue tasks by due date type: query JTF_TASK_DATES filtered on DATE_TYPE_ID for the due-date type and DATE_VALUE less than SYSDATE, joined back to JTF_TASKS_B.
• Reporting: date-sensitive CRM dashboards, task aging, and SLA reporting frequently consume this table because the actual date is not stored on JTF_TASKS_B itself.
• DFF extraction: ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 are read when customer-defined task date attributes must be included in extracts.

Related Objects

• JTF_TASKS_B — parent task table; joined on JTF_TASK_DATES.TASK_ID = JTF_TASKS_B.TASK_ID.
• JTF_TASK_DATE_TYPES_B — lookup of valid date types; joined on JTF_TASK_DATES.DATE_TYPE_ID = JTF_TASK_DATE_TYPES_B.DATE_TYPE_ID.
• FND_SECURITY_GROUPS — security group definition; joined on JTF_TASK_DATES.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• JTF_TASKS_VL / JTF_TASKS_TL — translated task views commonly joined when task names are needed.
• JTF_TASK_DATE_TYPES_TL — translated date-type names for multilingual reporting.