Search Results jtf_task_templates

Overview

JTF_TASK_TEMP_DEPENDS_V is an internal Oracle E-Business Suite view owned by the APPS schema in the JTF (CRM Foundation) product. Its documented purpose is to expose task dependency records that pertain specifically to task templates, drawing data from JTF_TASK_TEMPLATES and JTF_TASKS_B lineage. The view is a filtered, denormalized presentation of the JTF_TASK_DEPENDS base table, joined to the JTF_TASK_TEMPLATES_VL template view so that dependency rows carry human-readable template identifiers.

The view is not a primary end-user object. It supports internal processing, template administration, and reporting where consumers need to enumerate predecessor/successor relationships among template task definitions without writing the join to JTF_TASK_TEMPLATES_VL themselves. Because it filters on TEMPLATE_FLAG = 'Y', it returns only template-scoped dependency rows and excludes runtime task dependencies. In Oracle EBS 12.1.1 and 12.2.2 it is delivered as a VALID view and remains part of the CRM Foundation object set available to report developers and integrators querying the APPS schema.

Underlying Base Objects

The view text joins two objects: JTF_TASK_DEPENDS (aliased JTD) and JTF_TASK_TEMPLATES_VL (aliased JTA). In the documented metadata, JTF_TASK_DEPENDS is listed as a synonym and JTF_TASK_TEMPLATES_VL as a view, so the underlying storage ultimately resolves through the CRM Foundation task tables, notably JTF_TASKS_B referenced in the view description.

The driving join condition is JTD.DEPENDENT_ON_TASK_ID = JTA.TASK_TEMPLATE_ID, restricting the result set to dependency rows whose predecessor is a template. A second predicate, JTD.TEMPLATE_FLAG = 'Y', further restricts output to template dependencies. The JTA side supplies the DEPENDENT_ON_TASK_NUMBER and DEPENDENT_ON_TASK_NAME columns, which are not stored on JTF_TASK_DEPENDS and therefore are only available through this join. ROW_ID is carried as JTD.ROWID to provide a row identifier, and the standard WHO audit columns plus fifteen descriptive flexfield attributes and OBJECT_VERSION_NUMBER are passed through unchanged.

Key Columns

• DEPENDENCY_ID — Primary identifier of the dependency record in JTF_TASK_DEPENDS.
• TASK_ID — The task (successor) that owns the dependency.
• DEPENDENT_ON_TASK_ID — The predecessor template task that the TASK_ID depends on.
• DEPENDENT_ON_TASK_NUMBER / DEPENDENT_ON_TASK_NAME — Template identifier and name sourced from JTF_TASK_TEMPLATES_VL.
• DEPENDENCY_TYPE_CODE — The lookup-backed code classifying the relationship (for example start-to-start, finish-to-finish, or similar scheduling semantics). This is the column most frequently referenced in the query that led to this object.
• ADJUSTMENT_TIME / ADJUSTMENT_TIME_UOM — Offset applied to the dependency and its unit of measure.
• TEMPLATE_FLAG — Indicates template scope; the view predicate fixes this to 'Y'.
• ROW_ID — ROWID of the underlying JTF_TASK_DEPENDS row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — Descriptive flexfield segments.
• OBJECT_VERSION_NUMBER — Optimistic locking version for the row.

Common Use Cases and Queries

Typical uses include enumerating template dependencies for setup validation, driving custom scheduling reports, and building integrations that import or replicate task template structures. To list dependencies by type:

• SELECT dependency_id, task_id, dependent_on_task_id, dependent_on_task_name, dependency_type_code, adjustment_time, adjustment_time_uom FROM apps.jtf_task_temp_depends_v WHERE dependency_type_code = :p_code;
• SELECT task_id, dependent_on_task_number, dependent_on_task_name FROM apps.jtf_task_temp_depends_v WHERE dependent_on_task_id = :template_task_id;
• SELECT dependency_type_code, COUNT(*) FROM apps.jtf_task_temp_depends_v GROUP BY dependency_type_code;

Because DEPENDENCY_TYPE_CODE values are typically maintained as CRM Foundation lookups, join to the relevant lookup view (for example FND_LOOKUP_VALUES) to render meaningful descriptions. Queries should always scope by TASK_ID or DEPENDENT_ON_TASK_ID where possible, and callers should treat the view as read-only internal metadata rather than a supported public interface.