Results for “jtf_task_recur_rules”

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

Overview

JTF_TASK_RECUR_RULES is a CRM Foundation (JTF) table that stores the recurrence rules used by Oracle E-Business Suite task and calendar functionality. Tasks, task templates, and task audits reference a recurrence rule to determine how a scheduled activity repeats — whether daily, weekly, monthly, or on a custom cadence. The table therefore acts as the definitional backbone for recurring task generation across Oracle Tasks, Oracle Calendar, and the resource scheduling components of CRM Foundation in both release 12.1.1 and 12.2.2.

The documented schema exposes 41 columns, a surrogate primary key RECURRENCE_RULE_ID (enforced by JTF_TASK_RECURRENCE_RULES_PK and by the unique index JTF_TASK_RECUR_RULES_U1), standard EBS WHO columns, a SECURITY_GROUP_ID foreign key to FND_SECURITY_GROUPS, and a descriptive flexfield (ATTRIBUTE_CATEGORY plus ATTRIBUTE1–15). Based on the foreign-key topology in the ETRM metadata, the table can be modeled heuristically as a hub-leaning entity: it is referenced by several surrounding objects rather than being an attribute satellite of a single parent, and it carries only a small outbound dependency (FND_SECURITY_GROUPS).

Key Information Stored

The most significant columns are the following:

• RECURRENCE_RULE_ID — the surrogate primary key and sole documented unique index column (JTF_TASK_RECUR_RULES_U1). All dependent tables join on this column.
• OCCURS_WHICH and OCCURS_EVERY / OCCURS_NUMBER / OCCURS_UOM — control recurrence frequency, interval value, and unit of measure (day, week, month, year).
• OCCURS_MONTH, DATE_OF_MONTH, and DAY_OF_WEEK — position the recurrence within a month, month-of-year, or week.
• START_DATE_ACTIVE and END_DATE_ACTIVE — bound the effective period during which the rule applies.
• SUNDAY through SATURDAY — seven day-selection flags used for weekly patterns.
• DATE_SELECTED — records the selected date anchor for the recurrence pattern.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-organization/security-group partitioning of rule data.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard concurrency and audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage for customer-specific extensions.

No business-key column beyond RECURRENCE_RULE_ID is documented as unique, so the surrogate key remains the authoritative identifier.

Common Use Cases and Queries

Typical scenarios include identifying recurring tasks, validating recurrence patterns before regeneration, and reporting rule usage across templates and live tasks. A common join retrieves tasks and their recurrence definition:

• SELECT t.task_id, t.task_number, r.recurrence_rule_id, r.occurs_which, r.occurs_every, r.occurs_uom FROM jtf_tasks_b t, jtf_task_recur_rules r WHERE t.recurrence_rule_id = r.recurrence_rule_id;
• Locate orphaned or unreferenced rules: SELECT r.recurrence_rule_id FROM jtf_task_recur_rules r WHERE NOT EXISTS (SELECT 1 FROM jtf_tasks_b t WHERE t.recurrence_rule_id = r.recurrence_rule_id);
• Filter active rules: ... WHERE sysdate BETWEEN r.start_date_active AND nvl(r.end_date_active, sysdate + 1);
• Audit trail of changes: join JTF_TASK_AUDITS_B on old_recurrence_rule_id or new_recurrence_rule_id to identify edits to recurrence definitions.
• Security-group reporting by joining FND_SECURITY_GROUPS on security_group_id.

Day flags (SUNDAY–SATURDAY) and DATE_SELECTED are frequently queried when diagnosing weekly or monthly task generation discrepancies.

Related Objects

The ETRM metadata documents the following key relationships:

• JTF_TASKS_B — references JTF_TASK_RECUR_RULES.RECURRENCE_RULE_ID via JTF_TASKS_B.RECURRENCE_RULE_ID; the primary consumer of recurrence definitions.
• JTF_TASK_TEMPLATES_B — references RECURRENCE_RULE_ID, applying rules to task templates.
• JTF_TASK_AUDITS_B — references both OLD_RECURRENCE_RULE_ID and NEW_RECURRENCE_RULE_ID, capturing before/after rule values during audits.
• JTA_TASK_EXCLUSIONS — references RECURRENCE_RULE_ID, excluding specific occurrences from a recurring series.
• FND_SECURITY_GROUPS — referenced by JTF_TASK_RECUR_RULES.SECURITY_GROUP_ID; governs data security partitioning.

These relationships confirm the table's role as a central, hub-leaning definition object in CRM Foundation task scheduling.