Results for “jtf_task_contacts”

50+ results




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

Overview

JTF_TASK_CONTACTS is a CRM Foundation table in the JTF schema that stores contact information associated with tasks in Oracle E-Business Suite. It acts as the association bridge between a task record and the party (contact) participating in that task, whether as an assignee, requester, or notification recipient. The table is owned by the JTF product, which underpins Oracle's CRM task management and escalation framework across releases 12.1.1 and 12.2.2, and it carries a status of VALID in the ETRM registry.

From a data modeling perspective, the heuristic classification derived from its foreign-key structure is satellite-leaning. The table is not a pure reference or hub entity; rather, it extends a parent task with descriptive contact detail, contact role, and escalation behavior flags. The parent object is JTF_TASKS_B, joined through TASK_ID, while the contact party is resolved through HZ_PARTIES via CONTACT_ID. A second reference to FND_SECURITY_GROUPS via SECURITY_GROUP_ID enforces multi-org and security-group access rules.

Key Information Stored

The primary surrogate key is TASK_CONTACT_ID, which is also the single-column unique index (JTF_TASK_CONTACTS_U1) and thus the documented business-key candidate. Every contact row is uniquely identified by this value. The two most significant foreign-key columns are TASK_ID, which links the row to its owning task, and CONTACT_ID, which points to the HZ_PARTIES record of the participating contact.

  • TASK_CONTACT_ID — surrogate primary key and unique business-key candidate.
  • TASK_ID — foreign key to JTF_TASKS_B, tying the contact to a specific task.
  • CONTACT_ID — foreign key to HZ_PARTIES, identifying the contact party.
  • CONTACT_TYPE_CODE — classifies the contact's role on the task (for example, owner, assignee, or requester).
  • PRIMARY_FLAG — indicates whether this contact is the principal contact for the task.
  • ESCALATION_NOTIFY_FLAG — controls whether the contact receives escalation notifications.
  • ESCALATION_REQUESTER_FLAG — identifies the contact as the escalation requester.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing access control.
  • OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and who-columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage for customer-specific extensions.

Common Use Cases and Queries

Typical reporting extracts the contacts belonging to a task, the tasks assigned to a given contact, or the set of escalation recipients. A common join pattern combines the table with JTF_TASKS_B and HZ_PARTIES:

  • SELECT c.TASK_CONTACT_ID, c.TASK_ID, c.CONTACT_ID, c.CONTACT_TYPE_CODE FROM JTF.JTF_TASK_CONTACTS c WHERE c.TASK_ID = :task_id;
  • Join to HZ_PARTIES on CONTACT_ID = PARTY_ID to resolve contact names and email for notification reporting.
  • Filter ESCALATION_NOTIFY_FLAG = 'Y' to produce escalation distribution lists.
  • Filter PRIMARY_FLAG = 'Y' to isolate the principal contact per task.
  • Use SECURITY_GROUP_ID predicates to constrain results to an operating unit or responsibility's permitted security groups.

Related Objects

  • JTF_TASKS_B — parent task table; joined on JTF_TASK_CONTACTS.TASK_ID = JTF_TASKS_B.TASK_ID.
  • HZ_PARTIES — contact party master; joined on JTF_TASK_CONTACTS.CONTACT_ID = HZ_PARTIES.PARTY_ID.
  • JTF_TASK_PHONES — child detail table; references this table via JTF_TASK_PHONES.TASK_CONTACT_ID = JTF_TASK_CONTACTS.TASK_CONTACT_ID.
  • FND_SECURITY_GROUPS — security reference; joined on SECURITY_GROUP_ID.
  • JTF_TASK_CONTACTS_PK and JTF_TASK_CONTACTS_U1 — primary-key and unique indexes enforcing row integrity on TASK_CONTACT_ID.