Results for “jtf_task_priorities_b”

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

Overview

JTF_TASK_PRIORITIES_B is a CRM Foundation (JTF) reference table that stores the definition of all task priorities available within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Task priorities are the business-level severity or urgency codes assigned to tasks created through the Tasks framework, which underpins Oracle Sales, Oracle Service, Oracle TeleService, and other CRM modules. Because the table holds the master set of priority definitions rather than transactional task data, it behaves as a lookup or reference object shared across many consumers.

The table is owned by the JTF schema and is documented as VALID in the ETRM metadata, with 32 physical columns and a primary key constraint, JTF_TASK_PRIORITIES_B_PK, defined on TASK_PRIORITY_ID. A second unique index, JTF_TASK_PRIORITIES_B_U1, is defined on (TASK_PRIORITY_ID, ZD_EDITION_NAME), which supports the editioning/online patching model introduced in EBS 12.2. Under the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a hub: its surrogate TASK_PRIORITY_ID is the stable business key, and the descriptive attributes (importance level, active dates, descriptive flexfield columns) function as hub-adjacent attributes or, if historized, as a satellite dependent on that hub.

Key Information Stored

The most important columns of JTF_TASK_PRIORITIES_B are:

• TASK_PRIORITY_ID — the surrogate primary key and the value referenced by every dependent table; this is the column most often searched as "task_priority_id". It is also part of the JTF_TASK_PRIORITIES_B_U1 unique index alongside ZD_EDITION_NAME.
• IMPORTANCE_LEVEL — the numeric ranking that determines the relative ordering or weight of the priority when tasks are sorted or escalated.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the priority definition is valid and selectable.
• SEEDED_FLAG — indicates whether the row was delivered as seed data by Oracle or created by the customer.
• ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM_REFERENCE_ID — identify the originating external or upstream system and its reference key, supporting data migration and multi-source integration.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS that enforces multi-organization / security-group access control over the priority definition.
• UPGRADE_STATUS_FLAG — tracks the upgrade or migration state of the row during patching cycles.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the underlying AOL/BC4J framework to detect concurrent updates.
• ZD_EDITION_NAME — the edition identifier required by the 12.2 online patching architecture; combined with TASK_PRIORITY_ID it forms the business-key candidate JTF_TASK_PRIORITIES_B_U1.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segment columns used to capture customer-specific priority attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard WHO audit columns present on nearly every EBS transactional and reference table.

Common Use Cases and Queries

Typical uses of this table include populating priority list-of-values in task entry forms, reporting task volumes by priority in CRM dashboards, and validating that a priority reference passed by an interface is active. A common lookup query resolves the identifier to its definition and confirms the effective date window:

• SELECT task_priority_id, importance_level, seeded_flag, start_date_active, end_date_active FROM jtf.jtf_task_priorities_b WHERE task_priority_id = :p_id;
• SELECT p.task_priority_id, p.importance_level, COUNT(t.task_id) FROM jtf.jtf_task_priorities_b p, jtf.jtf_tasks_b t WHERE p.task_priority_id = t.task_priority_id AND TRUNC(SYSDATE) BETWEEN NVL(p.start_date_active, SYSDATE) AND NVL(p.end_date_active, SYSDATE) GROUP BY p.task_priority_id, p.importance_level ORDER BY p.importance_level;
• Flexfield reporting on ATTRIBUTE1–ATTRIBUTE15 filtered by ATTRIBUTE_CATEGORY to surface customer-defined priority metadata.
• Seeded-versus-custom reconciliation using SEEDED_FLAG, frequently executed after an upgrade to identify priorities modified or added in-house.

Related Objects

The metadata identifies the following principal dependents and references of JTF_TASK_PRIORITIES_B:

• JTF_TASKS_B — the base task table; joins on TASK_PRIORITY_ID to assign a priority to each task instance.
• JTF_TASK_TEMPLATES_B — task templates; joins on TASK_PRIORITY_ID to default the priority for tasks generated from a template.
• JTF_TASK_AUDITS_B — the task audit table; references the priority through both OLD_TASK_PRIORITY_ID and NEW_TASK_PRIORITY_ID, enabling before/after tracking of priority changes.
• CUG_SR_TASK_TYPE_DETS_B — service request task type details; joins on TASK_PRIORITY_ID to enforce default priorities by task type.
• IEU_UWQM_ITEMS_GTT — a global temporary table in the interaction/universal work queue area that references TASK_PRIORITY_ID during queue processing.
• FND_SECURITY_GROUPS — referenced by JTF_TASK_PRIORITIES_B.SECURITY_GROUP_ID to constrain visibility of priority definitions by security group.

Together these relationships confirm the table's role as a controlled vocabulary for task priority, central to both transactional task processing and CRM reporting.