Search Results jtf_tasks_b

Overview

The JTF_TASKS_B table is the core base table within Oracle E-Business Suite (EBS) CRM Foundation, specifically for releases 12.1.1 and 12.2.2. It serves as the central repository for storing the fundamental, non-transient attributes of a Task. A Task is a fundamental CRM entity representing any unit of work, activity, or assignment that needs to be tracked and managed, such as a service call, a sales follow-up, or a project milestone. This table is part of the underlying data model that supports the Task Manager and related CRM functionalities, providing the structural integrity and relational context for task-related data across the application.

Key Information Stored

The table's primary key is TASK_ID, which uniquely identifies each task record. As indicated by its extensive foreign key relationships, JTF_TASKS_B stores critical relational pointers that define a task's context and properties. Key columns include TASK_TYPE_ID, TASK_STATUS_ID, and TASK_PRIORITY_ID, which link to their respective reference tables to classify and track the task's state. It captures assignment details via ASSIGNED_BY_ID (linking to FND_USER) and customer information via CUSTOMER_ID and CUST_ACCOUNT_ID (linking to HZ_PARTIES and HZ_CUST_ACCOUNTS). The table supports task hierarchy through PARENT_TASK_ID, which self-references JTF_TASKS_B. Furthermore, it enables integration with other EBS objects through SOURCE_OBJECT_TYPE_CODE and SOURCE_OBJECT_ID, allowing tasks to be linked to entities like Service Requests (CS_INCIDENTS_ALL_B). Additional columns manage scheduling, location (ADDRESS_ID), currency (CURRENCY_CODE), and recurrence rules (RECURRENCE_RULE_ID).

Common Use Cases and Queries

This table is central to reporting, data extraction, and custom integrations involving task data. Common scenarios include generating task lists for specific users or teams, analyzing task duration and status trends, and building interfaces to synchronize tasks with external systems. A typical query might join JTF_TASKS_B with its descriptive reference tables to produce a comprehensive task report. For example:

• Retrieving all open, high-priority tasks for a customer account.
• Listing child tasks for a given parent task to understand work breakdowns.
• Identifying tasks created from specific source objects, such as all tasks linked to a particular service request.

Sample SQL Pattern:
SELECT t.task_number, t.planned_start_date, ts.name status, tp.name priority, u.user_name assigned_to FROM jtf.jtf_tasks_b t, jtf.jtf_task_statuses_b ts, jtf.jtf_task_priorities_b tp, fnd_user u WHERE t.task_status_id = ts.task_status_id AND t.task_priority_id = tp.task_priority_id AND t.assigned_to_id = u.user_id AND t.cust_account_id = :p_cust_acct_id;

Related Objects

JTF_TASKS_B has a dense network of relationships within the EBS schema. It is the base for the entity, with corresponding descriptive detail tables (e.g., JTF_TASKS_TL for translatable columns). Its integrity is defined by foreign keys to numerous critical tables:

• Reference Tables: JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, JTF_TASK_PRIORITIES_B, JTF_TASK_RECUR_RULES, HZ_TIMEZONES, FND_CURRENCIES.
• Party/Customer Model: HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES.
• User and Object Management: FND_USER, JTF_OBJECTS_B.
• Cross-Module Integration: CS_INCIDENTS_ALL_B (Service Requests).
• Hierarchical Structure: Self-referencing via PARENT_TASK_ID to JTF_TASKS_B.

Applications and APIs, such as those in the JTF Task Manager, interact with this table through public interfaces and views rather than directly, ensuring business logic encapsulation.