Results for “task_contact_id”

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

Overview

The JTF_TASK_CONTACTS_V view is a CRM Foundation (JTF) object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified as an internal view defined over the base table JTF_TASK_CONTACTS, exposing the task-to-contact association records that link Oracle Tasks with the parties (contacts and resources) involved in those tasks. The view surfaces contact assignments, escalation notification attributes, and the standard Who columns used for auditing and concurrency control.

Because escalation behaviour in Oracle Tasks and Oracle Territory/CRM applications depends on per-contact flags, the ESCALATION_NOTIFY_FLAG column — the term the user searched on — is one of the most frequently referenced columns in this view. It indicates whether a given contact associated with a task should receive escalation notifications when the task becomes overdue or breaches a service level. In ETRM, escalation logic reads these contact-level flags to determine the routing of notification workflows, making the view a practical reporting and integration surface even though it is described as internal.

Underlying Base Objects

According to the ETRM metadata, the view is defined over a single referenced base object: JTF_TASK_CONTACTS, accessed through a synonym in the APPS schema. The view is deliberately thin — its view text is a straight projection of the base table columns rather than a join or aggregation, and the view definition does not introduce additional filtering or transformation.

Because the view maps one-to-one to its base table, row counts and cardinality are identical: each row represents one contact assignment for one task. This means any filter or join applied to the view is effectively pushed to JTF_TASK_CONTACTS, and the view can be used as a drop-in replacement for the base table when read-only access is required. The base table itself is expected to carry the usual CRM Foundation indexes on TASK_ID, CONTACT_ID, and related foreign keys, but the view adds no independent performance overhead beyond that of the underlying table.

Key Columns

• TASK_CONTACT_ID — Primary key of the association record; uniquely identifies a task-to-contact link.
• TASK_ID — Foreign key to the parent task; the primary join key when reporting on task assignments.
• CONTACT_ID — Identifier of the contact associated with the task.
• CONTACT_TYPE_CODE — Classifies the contact role on the task (for example, owner, assignee, or interested party).
• ESCALATION_NOTIFY_FLAG — Flags whether the contact receives escalation notifications for the task.
• ESCALATION_REQUESTER_FLAG — Flags whether the contact is treated as the escalation requester.
• PRIMARY_FLAG — Identifies the primary contact among the associations for a task.
• OBJECT_VERSION_NUMBER — Optimistic locking column for concurrent updates.
• ROW_ID — ROWID of the underlying row, exposed for identification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield (DFF) context and attribute segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit Who columns.

Common Use Cases and Queries

The view supports reporting on escalation recipients and contact assignments. Typical queries include:

• Listing all contacts flagged for escalation notification on a specific task:

SELECT TASK_ID, CONTACT_ID, CONTACT_TYPE_CODE
FROM   APPS.JTF_TASK_CONTACTS_V
WHERE  TASK_ID = :task_id
AND    ESCALATION_NOTIFY_FLAG = 'Y';

• Identifying escalation requesters across open tasks, joined to the task header for status and dates.
• Auditing which contact is the primary contact for each task using PRIMARY_FLAG.
• Extracting DFF attributes (ATTRIBUTE1–15) for integration into external workflow or CRM reporting layers.

Because the view is an unfiltered projection, all reads should be constrained by TASK_ID or CONTACT_ID to avoid full scans of the base table. In 12.1.1 and 12.2.2, this view remains part of the seeded CRM Foundation data model and should not be modified; personalizations belong in custom views layered over it.