Results for “recurrence_rule_id”

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

Overview

JTA_TASK_EXCLUSIONS is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual occurrences excluded from a repeating task or appointment series. When a recurrence rule defines a pattern such as a daily, weekly, or monthly series, this table records the specific dates on which the series does not generate an instance, allowing users to skip holidays, cancelled meetings, or other exception dates without terminating the entire recurring activity. The object is owned by the JTF schema and is marked VALID in the ETRM reference for 12.2.2, with ten documented columns.

Under a heuristic Data Vault classification mined from its foreign key structure, JTA_TASK_EXCLUSIONS is modeled as a standalone object. That is, it neither behaves as a classic hub (it holds no natural business key shared across many dependent links) nor as a pure satellite of an existing hub; it functions as an independent exception/association record keyed by its own surrogate identifier. This classification is a modeling suggestion only, derived from FK cardinality.

Key Information Stored

The table's primary key is the surrogate column TASK_EXCLUSION_ID, enforced by the constraint JTA_TASK_EXCLUSIONS_PK. This is the only documented unique identifier; no separate business-key unique index is recorded in the metadata, so uniqueness of an exclusion is guaranteed only through this surrogate.

• TASK_EXCLUSION_ID – Surrogate primary key; uniquely identifies each exclusion row.
• TASK_ID – The task or appointment whose recurring series is affected; the business reference to the parent activity.
• RECURRENCE_RULE_ID – Foreign key to JTF_TASK_RECUR_RULES, identifying the pattern from which the occurrence is removed.
• EXCLUSION_DATE – The specific date (or occurrence) excluded from the series; the core business attribute.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS; controls multi-tenant/group visibility of the record.
• CREATED_BY, CREATION_DATE – Standard WHO audit columns capturing row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns capturing the last modification and session context.

Common Use Cases and Queries

Typical usage involves resolving which occurrences of a recurrence should be suppressed. A common pattern joins exclusions to the recurrence rule and the parent task:

• Listing excluded dates for a given series: SELECT e.EXCLUSION_DATE FROM JTA_TASK_EXCLUSIONS e WHERE e.RECURRENCE_RULE_ID = :rule_id;
• Finding all exclusions for a task: SELECT * FROM JTA_TASK_EXCLUSIONS WHERE TASK_ID = :task_id ORDER BY EXCLUSION_DATE;
• Reporting recurring tasks with counts of skipped occurrences, grouped by RECURRENCE_RULE_ID.
• Auditing recently changed exclusions via LAST_UPDATE_DATE for integration or reconciliation.
• Filtering by SECURITY_GROUP_ID in multi-org or secured CRM deployments.

Because the row is a lightweight exception record, most reporting is read-only; inserts and deletes occur as users edit a series.

Related Objects

• JTF_TASK_RECUR_RULES – Referenced via RECURRENCE_RULE_ID; defines the parent recurrence pattern.
• FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID; governs record visibility.
• JTF_TASKS – Parent task/appointment identified by TASK_ID.
• JTA_TASK_EXCLUSIONS_PK – Primary key constraint on TASK_EXCLUSION_ID.
• JTF Task/Calendar APIs – Application-layer routines that create and consume exclusion rows when materializing series instances.

Together these objects let CRM scheduling logic compute effective occurrence sets by subtracting excluded dates from the recurrences generated by the rule.