Search Results jtf_task_statuses




Overview
Explore in AI Chat

Overview

JTF_TASK_STATUSES_B is a foundational reference table within the JTF (CRM Foundation) product family of Oracle E-Business Suite, holding most currently documented rows in the Oracle 12.1.1 and 12.2.2 releases. As its description states, JTF_TASK_STATUSES stores all the task statuses available to the CRM task and resource management subsystem—the codes and behavior flags that govern how a task moves through its lifecycle, from assignment and acceptance through completion, hold, rejection, or cancellation.

Sitting at the center of the Task Management model, this table supplies the status values referenced by transactional task records, task templates, service request type definitions, and audit history. It is delivered as a seeded reference set, meaning most rows are created during installation or upgrade rather than by end users.

Applying a Data Vault modeling heuristic to the documented foreign key structure, the object classifies as hub-leaning: the primary key TASK_STATUS_ID identifies each unique status, and the same identifier is republished as a foreign key into a wide ring of dependent tables. This makes it a natural business hub around which task lifecycle satellites accumulate. The companion translation object (JTF_TASK_STATUSES_TL) supplies language-specific status names for multilingual deployments.

Key Information Stored

The table is keyed by a surrogate primary key, TASK_STATUS_ID, defined by constraint JTF_TASK_STATUSES_B_PK. The unique index JTF_TASK_STATUSES_B_U1 (TASK_STATUS_ID, ZD_EDITION_NAME) confirms the business-key candidate and supports the editioning mechanism used in 12.2.x.

The most significant columns fall into three groups:

The SECURITY_GROUP_ID column links each status to a security grouping in FND_SECURITY_GROUPS, enforcing multi-tenant style data separation. SEEDED_FLAG distinguishes Oracle-delivered statuses from customer-defined ones, a useful filter when diagnosing upgrade behavior.

Common Use Cases and Queries

Typical usage centers on task workflow configuration and status-driven reporting. Because the table stores behavioral flags rather than descriptive text, most queries join to the translation table for a user-facing label. A representative pattern:

SELECT t.task_status_id, t.status_name, b.closed_flag, b.completed_flag
FROM jtf_task_statuses_tl t, jtf_task_statuses_b b
WHERE t.task_status_id = b.task_status_id
AND t.language = USERENV('LANG')
AND b.seeded_flag = 'Y';

Report authors commonly enumerate open tasks by joining JTF_TASKS_B to this table and filtering on CLOSED_FLAG = 'N'. Administrators query SEEDED_FLAG and CLOSED_FLAG together to audit which statuses remain active. Transactional processing—status advancement, validation, and audit trails—references valid status values from this table when applying transitions.

Related Objects

The documented foreign key relationships identify the principal dependents, each joining on TASK_STATUS_ID:

  • JTF_TASKS_B — the core task transaction table, carrying the current TASK_STATUS_ID for every task instance.
  • JTF_TASK_AUDITS_B — task audit history, recording prior and new statuses via OLD_TASK_STATUS_ID and NEW_TASK_STATUS_ID, enabling full lifecycle reconstruction.
  • JTF_TASK_TEMPLATES_B — predefined task templates that inherit an initial status.
  • CUG_SR_TASK_TYPE_DETS_B — service request task type detail definitions, tying status options to specific SR task types.
  • AD_TASK_TIMING — task timing configuration referencing status values.
  • JTF_TASK_STATUSES_TL — translation table supplying display names.
  • FND_SECURITY_GROUPS — upstream security group definition referenced by SECURITY_GROUP_ID for row-level access control.

Together these objects form the status backbone of the CRM task model, and JTF_TASK_STATUSES_B should be treated as a controlled reference set rather than transactional data.