Search Results jtf_task_types_b

Overview

The JTF_TASK_TYPES_B table is a core master data table within the Oracle E-Business Suite CRM Foundation (JTF) module. It serves as the central repository for defining and storing all task types available across the application. A task type categorizes the nature of a work activity, such as a "Service Call," "Sales Visit," "Meeting," or "Follow-up." This classification is fundamental to the task management functionality, enabling consistent reporting, process automation, and the application of type-specific business rules. The table's structure supports multilingual descriptions through its corresponding translatable view, JTF_TASK_TYPES_TL. As a base table with a "_B" suffix, it holds the primary, non-translatable columns and is the anchor for a network of related transactional and setup tables.

Key Information Stored

While the provided metadata does not list specific columns, based on its role as a setup table, JTF_TASK_TYPES_B typically contains key identifier and control columns. The primary key, TASK_TYPE_ID, is a unique numeric identifier for each task type record. Other standard columns often include a SEEDED_FLAG indicating if the type is a pre-delivered Oracle seed data record, START_DATE_ACTIVE and END_DATE_ACTIVE for controlling the type's availability, and CREATION_DATE/CREATED_BY for auditing. The table also stores a NAME or CODE column for the internal unique identifier of the task type. Descriptive information is managed in the associated JTF_TASK_TYPES_TL table, which holds the LANGUAGE and DESCRIPTION (or DISPLAY_NAME) for user interfaces.

Common Use Cases and Queries

This table is primarily referenced for validation, reporting, and setup purposes. A common use case is generating a list of all active task types for a LOV (List of Values) in a task creation form or a report parameter. Developers and administrators query this table to understand the task type hierarchy or to validate custom integrations. Sample queries include selecting active types for a given date or joining with the tasks table to analyze task volume by type.

• List Active Task Types: SELECT task_type_id, name FROM jtf_task_types_b WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE) ORDER BY name;
• Count Tasks by Type: SELECT tt.name, COUNT(t.task_id) FROM jtf_task_types_b tt, jtf_tasks_b t WHERE tt.task_type_id = t.task_type_id GROUP BY tt.name;

Related Objects

JTF_TASK_TYPES_B is a pivotal parent table with numerous foreign key relationships, as documented in the metadata. Its TASK_TYPE_ID column is referenced by key transactional tables, establishing critical data integrity. The primary relationships are:

• JTF_TASKS_B: The main tasks table links to JTF_TASK_TYPES_B via TASK_TYPE_ID, classifying every task instance.
• JTF_TASK_TEMPLATES_B: Task templates are associated with a specific type via TASK_TYPE_ID.
• JTF_TASK_RSC_REQS: Resource requirements for tasks are defined per task type.
• JTF_TASK_AUDITS_B: Tracks history when a task's type is changed, referencing both OLD_TASK_TYPE_ID and NEW_TASK_TYPE_ID.
• CUG_TSK_TYP_ATTR_MAPS_B & CUG_TSK_TYP_ATTR_DEPS_B: These tables manage custom attribute mappings and dependencies specific to a task type (TASK_TYPE_ID).

For user-facing applications, the translatable view JTF_TASK_TYPES_TL is joined to this base table to retrieve language-specific descriptions.