Results for “jtf_tasks_b_pk”

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

Overview

JTF_TASKS_B is the base table in the JTF (CRM Foundation) schema that stores the general, master-level information for a Task record in Oracle E-Business Suite 12.1.1 and 12.2.2. Tasks represent discrete units of work or activity—such as a scheduled call, a follow-up action, a service activity, or a campaign step—that can be associated with customers, resources, campaigns, service requests, and other CRM entities. As a "_B" (base) table, it holds the entity definition and core attributes, while the associated translation (_TL) tables hold language-dependent descriptive text. In the ETRM documentation, JTF_TASKS_B is classified as VALID and owned by the JTF schema.

Using the Data Vault modeling heuristic mined from its foreign-key structure, JTF_TASKS_B is best characterized as a hub. It carries the immutable business key (TASK_ID / TASK_NUMBER) that anchors the task entity, together with a large set of descriptive and contextual attributes. In Data Vault terms, many of the changing descriptive columns would typically be split out into one or more satellites, but the underlying hub identity remains centered on TASK_ID. This classification is offered as a modeling suggestion rather than a documented Oracle standard.

Key Information Stored

JTF_TASKS_B contains 103 documented columns. The most operationally significant are summarized below, distinguishing the surrogate primary key from business-key candidates.

• TASK_ID — The surrogate primary key (constraint JTF_TASKS_B_PK), uniquely identifying each task row. It is also enforced by the unique index JTF_TASKS_B_U1.
• TASK_NUMBER — The user-facing business identifier for a task, enforced by unique index JTF_TASKS_B_U2. Alongside TASK_ID, this is the primary business-key candidate.
• TASK_TYPE_ID — Foreign key to JTF_TASK_TYPES_B, classifying the nature of the task.
• TASK_STATUS_ID — Foreign key to JTF_TASK_STATUSES_B, indicating the workflow/status of the task.
• TASK_PRIORITY_ID — Foreign key to JTF_TASK_PRIORITIES_B, capturing the task priority.
• OWNER_ID / OWNER_TYPE_CODE / ASSIGNED_BY_ID — Ownership and assignment context; ASSIGNED_BY_ID references FND_USER.
• CUSTOMER_ID / CUST_ACCOUNT_ID / ADDRESS_ID — Relationships to the customer party (HZ_PARTIES), customer account (HZ_CUST_ACCOUNTS), and address/site (HZ_PARTY_SITES).
• SOURCE_OBJECT_TYPE_CODE / SOURCE_OBJECT_ID / SOURCE_OBJECT_NAME — The source entity from which the task originated, referencing JTF_OBJECTS_B and potentially CS_INCIDENTS_ALL_B.
• PARENT_TASK_ID — Self-referencing foreign key enabling hierarchical parent/child task structures.
• PLANNED_START_DATE / PLANNED_END_DATE / SCHEDULED_START_DATE / SCHEDULED_END_DATE / ACTUAL_START_DATE / ACTUAL_END_DATE — The core task timeline attributes.
• PERCENTAGE_COMPLETE — Progress indicator for the task.
• RECURRENCE_RULE_ID — Foreign key to JTF_TASK_RECUR_RULES for recurring task definitions.
• ORG_ID / SECURITY_GROUP_ID — Multi-org and security-group context (SECURITY_GROUP_ID references FND_SECURITY_GROUPS).

Common Use Cases and Queries

Typical uses include CRM activity reporting, task assignment workload analysis, campaign/service activity tracking, and integration with service requests.

• List open tasks for a given owner or resource, joined to status and priority lookup tables.
• Report tasks associated with a specific customer party or account.
• Derive task hierarchies using the PARENT_TASK_ID self-join.
• Extract tasks linked to campaigns (AMS_CAMPAIGNS_ALL_B) or service requests (CS_INCIDENTS_ALL_B) for cross-module reporting.

A representative query joining the master task to its status, priority, and type lookups:

• SELECT t.task_id, t.task_number, st.name status, p.name priority, ty.name task_type, t.planned_start_date, t.percentage_complete
• FROM jtf_tasks_b t, jtf_task_statuses_b st, jtf_task_priorities_b p, jtf_task_types_b ty
• WHERE t.task_status_id = st.task_status_id AND t.task_priority_id = p.task_priority_id AND t.task_type_id = ty.task_type_id
• AND t.deleted_flag = 'N' AND t.org_id = :org_id;

Related Objects

JTF_TASKS_B participates in an extensive relationship network documented in the ETRM metadata. The most significant related objects and join columns are:

• JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, JTF_TASK_PRIORITIES_B — Master lookups via TASK_TYPE_ID, TASK_STATUS_ID, and TASK_PRIORITY_ID.
• HZ_PARTIES / HZ_CUST_ACCOUNTS / HZ_PARTY_SITES — Customer party, account, and address context via CUSTOMER_ID, CUST_ACCOUNT_ID, and ADDRESS_ID.
• JTF_OBJECTS_B — Source object typing via SOURCE_OBJECT_TYPE_CODE.
• CS_INCIDENTS_ALL_B — Service request linkage via SOURCE_OBJECT_ID.
• FND_USER — Assignment audit via ASSIGNED_BY_ID.
• JTF_TASK_ASSIGNMENTS, JTF_TASK_DATES, JTF_TASK_CONTACTS, JTF_TASK_REFERENCES_B — Child detail tables referencing TASK_ID.
• AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES_B — Campaign linkage via TASK_ID.
• CSD_REPAIRS, CSP_REQUIREMENT_HEADERS — Service/repair processes referencing TASK_ID.
• JTF_TASKS_B (self) — Recursive parent/child linkage via PARENT_TASK_ID.