Results for “jtf_tasks_b_u1”

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

Overview

JTF.JTF_TASKS_B is the foundation base table of the Oracle E-Business Suite Task Manager, a shared infrastructure component used across multiple application families including CRM, Service, Sales, Marketing, and Field Service. The table stores general information about a given task, with each row representing a single task record that captures ownership, source object affiliation, customer context, scheduling dates, effort and duration measures, and numerous control flags consumed by the various applications that rely on the Task Manager foundation. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is registered in FND Design Data as JTF.JTF_TASKS_B.

From a dimensional modeling perspective, the mined foreign-key structure suggests classifying JTF_TASKS_B as a hub. It carries a stable surrogate primary key (TASK_ID) and a small set of durable business identifiers, with most descriptive and transactional attributes distributed across dependent satellite-style tables such as JTF_TASK_DATES, JTF_TASK_ASSIGNMENTS, and JTF_TASK_CONTACTS.

Key Information Stored

The table contains 103 documented columns. The most significant include:

• TASK_ID — the surrogate primary key, a NUMBER column enforced by unique index JTF_TASKS_B_U1 and the JTF_TASKS_B_PK constraint.
• TASK_NUMBER — the user-facing business key, enforced by unique index JTF_TASKS_B_U2 (the object referenced in the user's search).
• TASK_TYPE_ID, TASK_STATUS_ID, TASK_PRIORITY_ID — lookups against JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, and JTF_TASK_PRIORITIES_B respectively.
• OWNER_ID, OWNER_TYPE_CODE, OWNER_TERRITORY_ID, ASSIGNED_BY_ID — ownership and assignment context.
• SOURCE_OBJECT_TYPE_CODE and SOURCE_OBJECT_ID — polymorphic reference linking the task to its originating entity (for example a service incident or party).
• CUSTOMER_ID, CUST_ACCOUNT_ID, ADDRESS_ID — customer and site context against HZ_PARTIES, HZ_CUST_ACCOUNTS, and HZ_PARTY_SITES.
• PLANNED_START_DATE/PLANNED_END_DATE, SCHEDULED_START_DATE/SCHEDULED_END_DATE, ACTUAL_START_DATE/ACTUAL_END_DATE, CALENDAR_START_DATE/CALENDAR_END_DATE — the family of date pairs indexed for range queries.
• PARENT_TASK_ID — self-referencing hierarchy link enabling task/sub-task structures.
• OPEN_FLAG, DELETED_FLAG, PERCENTAGE_COMPLETE, DURATION, PLANNED_EFFORT, ACTUAL_EFFORT, MILESTONE_FLAG, BILLABLE_FLAG — control and progress indicators used by consumers of the Task Manager.
• RECURRENCE_RULE_ID, TEMPLATE_ID, TEMPLATE_GROUP_ID — recurring and templated task support.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Typical reporting scenarios include open task worklists by owner, overdue task analysis, customer task history, and task counts by type or status. Because OPEN_FLAG, TASK_TYPE_ID, and TASK_STATUS_ID are indexed together (JTF_TASKS_B_N16) and with owner columns (JTF_TASKS_B_N2, _N3), these are the primary access paths.

• Open tasks for an owner: SELECT task_id, task_number, scheduled_start_date FROM jtf_tasks_b WHERE owner_id = :p_owner AND open_flag = 'Y' AND deleted_flag = 'N';
• Tasks linked to a service incident: SELECT * FROM jtf_tasks_b WHERE source_object_type_code = 'SR' AND source_object_id = :incident_id;
• Task hierarchy retrieval: SELECT ... FROM jtf_tasks_b START WITH parent_task_id IS NULL CONNECT BY PRIOR task_id = parent_task_id;
• Overdue analysis by scheduled window using index JTF_TASKS_B_N12.

Related Objects

JTF_TASKS_B sits at the center of an extensive relationship graph. The most significant dependent tables (those referencing TASK_ID) include:

• JTF_TASK_DATES — granular date records per task.
• JTF_TASK_ASSIGNMENTS — resource and assignee mapping.
• JTF_TASK_CONTACTS — contact associations.
• JTF_TASK_REFERENCES_B and JTF_TASK_AUDITS_B — reference and audit trails.
• JTF_IH_ACTIVITIES — interaction history activity links.
• CSD_REPAIRS, CSP_REQUIREMENT_HEADERS — Service module integration.
• AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES_B — Marketing campaign task linkage.
• Lookup dependencies on JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, JTF_TASK_PRIORITIES_B, and JTF_TASK_RECUR_RULES.