Results for “jtf_task_templates_b_pk”

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

Overview

JTF_TASK_TEMPLATES_B is a CRM Foundation (JTF) base table that stores task template definitions used throughout Oracle E-Business Suite Release 12.1.1 and 12.2.2. Task templates serve as reusable blueprints for the tasks generated by CRM, sales methodology, and service workflows, allowing organizations to standardize duration, effort, priority, status, recurrence, notification, and alarm behavior across many generated tasks. The table is owned by the JTF schema and is documented as VALID, with 53 columns in the 12.2.2 ETRM physical schema.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries many descriptive and behavioral attributes (duration, notification, alarm, and flag columns) hanging off a single surrogate key, with relatively few outbound dependencies relative to the number of descriptive fields. This makes it a strong candidate for modeling as a satellite attached to a task-template hub keyed on TASK_TEMPLATE_ID.

Key Information Stored

The surrogate primary key is TASK_TEMPLATE_ID, enforced by JTF_TASK_TEMPLATES_B_PK. A second unique index, JTF_TASK_TEMPLATES_B_U1 (TASK_TEMPLATE_ID, ZD_EDITION_NAME), is the business-key candidate; the ZD_EDITION_NAME column supports edition-based redefinition in 12.2.x. The most operationally significant columns include:

• TASK_NUMBER — the user-facing template identifier.
• TASK_GROUP_ID — FK to JTF_TASK_TEMP_GROUPS_B, grouping related templates.
• TASK_TYPE_ID, TASK_STATUS_ID, TASK_PRIORITY_ID — FKs to JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, and JTF_TASK_PRIORITIES_B, respectively, classifying the template.
• DURATION and DURATION_UOM — default task length and unit of measure.
• PLANNED_EFFORT and PLANNED_EFFORT_UOM — default effort estimate.
• RECURRENCE_RULE_ID — FK to JTF_TASK_RECUR_RULES defining repeat behavior.
• NOTIFICATION_FLAG, NOTIFICATION_PERIOD, NOTIFICATION_PERIOD_UOM — lead-time notification configuration.
• ALARM_START, ALARM_START_UOM, ALARM_ON, ALARM_COUNT, ALARM_INTERVAL, ALARM_INTERVAL_UOM — alarm scheduling attributes.
• PRIVATE_FLAG, PUBLISH_FLAG, RESTRICT_CLOSURE_FLAG, MULTI_BOOKED_FLAG, MILESTONE_FLAG, HOLIDAY_FLAG, BILLABLE_FLAG, DELETED_FLAG — behavioral control flags.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS for multi-org security.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS flexfield/descriptive attribute set.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and TASK_CONFIRMATION_STATUS.

Common Use Cases and Queries

Typical reporting scenarios include listing active, billable templates by type and priority, auditing recurrence and notification setup, and identifying templates consumed by sales methodology or product-task maps.

• Joining to lookup tables for readable values: query JTF_TASK_TEMPLATES_B joined to JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, and JTF_TASK_PRIORITIES_B on TASK_TYPE_ID, TASK_STATUS_ID, and TASK_PRIORITY_ID.
• Recurrence reporting: join to JTF_TASK_RECUR_RULES on RECURRENCE_RULE_ID to inspect repeat rules.
• Where-used analysis: query AS_SALES_METH_TASK_MAP or CSP_PRODUCT_TASKS on TASK_TEMPLATE_ID to find templates referenced by sales methods or product tasks.
• Filter clause: WHERE DELETED_FLAG = 'N' AND NVL(PUBLISH_FLAG,'N') = 'Y' to return published, non-deleted templates.
• Dependency inspection: join JTF_TASK_DEPENDS on TASK_ID and DEPENDENT_ON_TASK_ID to map template predecessor/successor relationships.

Related Objects

JTF_TASK_TEMPLATES_B participates in a rich FK network. Referenced (parent) tables include JTF_TASK_TEMP_GROUPS_B (TASK_GROUP_ID), JTF_TASK_TYPES_B (TASK_TYPE_ID), JTF_TASK_STATUSES_B (TASK_STATUS_ID), JTF_TASK_PRIORITIES_B (TASK_PRIORITY_ID), JTF_TASK_RECUR_RULES (RECURRENCE_RULE_ID), and FND_SECURITY_GROUPS (SECURITY_GROUP_ID). Tables that reference this table (children) include AS_SALES_METH_TASK_MAP.TASK_TEMPLATE_ID, CSP_PRODUCT_TASKS.TASK_TEMPLATE_ID, AMS_ACT_TYPE_TASK_TPLS.TASK_TEMPLATE_ID, JTF_TASK_RSC_REQS.TASK_TEMPLATE_ID, and JTF_TASK_DEPENDS via both TASK_ID and DEPENDENT_ON_TASK_ID. The _B suffix indicates this is the base (non-translated) table, with translation typically held in a companion _TL table.