Results for “jtf_task_types_b”

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

Overview

JTF_TASK_TYPES_B is a foundation table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, and it holds the master definition of all task types used throughout the CRM task management framework. In EBS 12.1.1 and 12.2.2 it functions as the reference list that classifies activities created in modules such as Oracle Sales, Oracle Service, Oracle Marketing, and Oracle TeleSales. Every user-created task, template, resource request, or audit record ultimately points back to a row in this table through the TASK_TYPE_ID column.

The table maintains 43 columns and is uniquely identified by the primary key JTF_TASK_TYPES_B_PK on TASK_TYPE_ID. The additional unique index JTF_TASK_TYPES_B_U1 covers TASK_TYPE_ID together with ZD_EDITION_NAME, reflecting the editioning behavior introduced in release 12.2 for online patching. In Data Vault modeling terms, the metadata classifies this object as hub-leaning: it is a stable, business-key-driven entity with multiple downstream link and satellite dependencies rather than a transactional detail table.

Key Information Stored

The most significant columns include:

• TASK_TYPE_ID — the surrogate primary key and the foreign key referenced by dependent child tables.
• START_DATE_ACTIVE and END_DATE_ACTIVE — control the effective window during which the task type can be selected.
• SEEDED_FLAG — distinguishes Oracle-delivered task types from customer-defined ones.
• WORKFLOW and WORKFLOW_TYPE — determine the workflow process associated with the task type.
• PLANNED_EFFORT and PLANNED_EFFORT_UOM — capture default effort estimates and their unit of measure.
• SCHEDULE_FLAG, NOTIFICATION_FLAG, PRIVATE_FLAG, BILLABLE_FLAG — behavioral indicators controlling scheduling, notification, visibility, and billing for tasks of this type.
• SPARES_ALLOWED_FLAG and SET_ACTUAL_DATES_FLAG — field service and date-handling controls.
• RULE — stores rule logic associated with the type.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS that enforces group-level security.
• ORIG_SYSTEM_REFERENCE and ORIG_SYSTEM_REFERENCE_ID — identify the originating system for imported or integrated task types.
• OBJECT_VERSION_NUMBER — supports optimistic locking via the OAF framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF extension columns.
• ZD_EDITION_NAME — the editioning marker used in 12.2 for online patching.

The business-key candidate is TASK_TYPE_ID, while ZD_EDITION_NAME participates only in the editioning unique index. The surrogate/administrative fields CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard audit tracking.

Common Use Cases and Queries

Typical usage includes LOV population for task entry screens, reporting on active task types, and integration extraction for external task systems. A frequent query lists all active, customer-defined task types:

• SELECT task_type_id, name, seeded_flag FROM jtf_task_types_v WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE);
• SELECT COUNT(*) FROM jtf_tasks_b t, jtf_task_types_b tt WHERE t.task_type_id = tt.task_type_id GROUP BY tt.task_type_id;
• Reporting joins to JTF_TASKS_B to summarize volumes by task type, and joins to JTF_TASK_TEMPLATES_B to identify which templates are configured per type.

Because the _B table stores the base record and the _TL table stores translated names, reports should query the translatable view (JTF_TASK_TYPES_VL) rather than the base table when display labels are required.

Related Objects

Significant dependent and referenced objects include:

• JTF_TASKS_B — the primary child table, joined on TASK_TYPE_ID, storing individual task instances.
• JTF_TASK_TEMPLATES_B — templates defined per task type, joined on TASK_TYPE_ID.
• JTF_TASK_RSC_REQS — resource requirements linked to task types via TASK_TYPE_ID.
• JTF_TASK_AUDITS_B — audit trail referencing both NEW_TASK_TYPE_ID and OLD_TASK_TYPE_ID.
• CUG_TSK_TYP_ATTR_DEPS_B and CUG_TSK_TYP_ATTR_MAPS_B — attribute dependency and mapping definitions linked via TASK_TYPE_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for access control.

Together these relationships confirm JTF_TASK_TYPES_B as the central hub for task-type definition within CRM Foundation.