Results for “jtf_task_templates_b_u1”

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

Overview

JTF.JTF_TASK_TEMPLATES_B is a foundational Oracle E-Business Suite base table that stores task template definitions used throughout the Task Manager and resource management modules of EBS 12.1.1 and 12.2.2. The table resides in the JTF schema, carries VALID status in the ETRM repository, and is registered as FND Design Data JTF.JTF_TASK_TEMPLATES_B. It holds the mold from which concrete task instances are generated, containing the default attributes, scheduling parameters, notification and alarm settings, and control flags that govern how tasks are created, tracked, and closed.

Storage is allocated in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, while its indexes live in APPS_TS_TX_IDX. The table exposes 53 documented columns and is classified heuristically as satellite-leaning in Data Vault terms. This classification is offered as a modeling suggestion: the table’s dense descriptive attribute set, its standard WHO audit columns, and its dependence on external code tables for type, status, priority, and grouping are characteristic of a satellite attached to a task-template business key, rather than a hub of independent entities.

Key Information Stored

The surrogate primary key is TASK_TEMPLATE_ID (NUMBER), enforced via JTF_TASK_TEMPLATES_B_PK. The unique index JTF_TASK_TEMPLATES_B_U1 covers TASK_TEMPLATE_ID combined with ZD_EDITION_NAME, confirming that the documented business-key candidate is the template identifier scoped by edition. A non-unique index, JTF_TASK_TEMPLATES_B_N1, supports lookups by TASK_GROUP_ID.

The most significant descriptive columns include:

• TASK_GROUP_ID — foreign key to JTF_TASK_TEMP_GROUPS_B, grouping related templates.
• TASK_NUMBER — the VARCHAR2(30) business-facing template number.
• TASK_TYPE_ID — foreign key to JTF_TASK_TYPES_B, defining the kind of task.
• TASK_STATUS_ID — foreign key to JTF_TASK_STATUSES_B, the default status.
• TASK_PRIORITY_ID — foreign key to JTF_TASK_PRIORITIES_B.
• DURATION and DURATION_UOM — planned length plus its unit of measure.
• PLANNED_EFFORT and PLANNED_EFFORT_UOM — effort estimation.
• RECURRENCE_RULE_ID — foreign key to JTF_TASK_RECUR_RULES for repeating templates.
• PRIVATE_FLAG and PUBLISH_FLAG — visibility and publication controls.
• RESTRICT_CLOSURE_FLAG — whether completion is required before a source object is deemed complete.
• MILESTONE_FLAG, HOLIDAY_FLAG, and BILLABLE_FLAG — classification flags.
• NOTIFICATION_FLAG, NOTIFICATION_PERIOD, and NOTIFICATION_PERIOD_UOM — alert configuration.
• DELETED_FLAG, SECURITY_GROUP_ID, and TASK_CONFIRMATION_STATUS — lifecycle and access control.

Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support multi-user locking in HTML-based UIs. Fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide the customary DFF extension surface.

Common Use Cases and Queries

Typical scenarios include reporting on all active task templates, verifying notification configuration, auditing template reuse across programs, and diagnosing why generated tasks inherit specific defaults. A joined query against the code tables is common:

• Joining JTF_TASK_TEMPLATES_B to JTF_TASK_TYPES_B, JTF_TASK_STATUSES_B, and JTF_TASK_PRIORITIES_B via TASK_TYPE_ID, TASK_STATUS_ID, and TASK_PRIORITY_ID to render human-readable template reports.
• Filtering on TASK_GROUP_ID (backed by JTF_TASK_TEMPLATES_B_N1) to list templates for a given group.
• Selecting templates where RECURRENCE_RULE_ID is not null to audit recurring task setups.
• Checking PUBLISH_FLAG and PRIVATE_FLAG to validate template visibility before rollout.
• Querying by TASK_TEMPLATE_ID to trace a rendered task back to its template definition.

Related Objects

The table participates in a dense foreign-key network, both as a reference target and as a consumer of code-table lookups.

• JTF_TASK_TEMP_GROUPS_B — referenced via TASK_GROUP_ID; defines template groups.
• JTF_TASK_TYPES_B — referenced via TASK_TYPE_ID.
• JTF_TASK_STATUSES_B — referenced via TASK_STATUS_ID.
• JTF_TASK_PRIORITIES_B — referenced via TASK_PRIORITY_ID.
• JTF_TASK_RECUR_RULES — referenced via RECURRENCE_RULE_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
• JTF_TASK_DEPENDS — references this table twice, through TASK_ID and DEPENDENT_ON_TASK_ID, modeling template dependencies.
• JTF_TASK_RSC_REQS — references TASK_TEMPLATE_ID to define resource requirements per template.
• AMS_ACT_TYPE_TASK_TPLS and CSP_PRODUCT_TASKS — reference TASK_TEMPLATE_ID, tying templates to marketing activity types and product tasks.
• AS_SALES_METH_TASK_MAP — references TASK_TEMPLATE_ID, linking templates into sales methodology flows.