Results for “jtf_task_phones”

50+ results




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

Overview

JTF_TASK_PHONES is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores pointers linking task contacts to telephone contact points. Its documented purpose is to hold the associations between a contact record on a task and the specific phone numbers recorded for that contact. The table is owned by the JTF schema and holds a VALID status within the E-Business Suite data dictionary.

From a Data Vault modeling perspective, the documented foreign key structure indicates that JTF_TASK_PHONES behaves as a link table. It resolves a many-to-many style relationship between task contacts and contact points, carrying its own surrogate identifier (TASK_PHONE_ID) while referencing both JTF_TASK_CONTACTS and HZ_CONTACT_POINTS. Because the table also carries descriptive and audit attributes — including PRIMARY_FLAG, OWNER_TABLE_NAME, and the ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns — it retains a degree of satellite-like descriptive content in addition to its linking role.

Key Information Stored

The table contains 28 documented columns. The most operationally significant are:

  • TASK_PHONE_ID — the surrogate primary key, defined by the JTF_TASK_PHONES_PK constraint and reinforced by the unique index JTF_TASK_PHONES_U1. This is the column targeted by the "jtf_task_phones_pk" search term and is the primary routing key for lookups on this table.
  • TASK_CONTACT_ID — foreign key to JTF_TASK_CONTACTS; identifies the contact to which the phone pointer belongs.
  • PHONE_ID — foreign key to HZ_CONTACT_POINTS; identifies the actual contact point (telephone) record.
  • PRIMARY_FLAG — indicates whether the referenced phone is the primary number for the associated contact. Because the only documented unique index is on TASK_PHONE_ID, PRIMARY_FLAG is enforced by application logic rather than a database constraint.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / data-security partitioning.
  • OWNER_TABLE_NAME — identifies the source or owning entity for the pointer, supporting polymorphic ownership.
  • OBJECT_VERSION_NUMBER — supports optimistic locking and concurrent update control in the OAF/ADF framework.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns for audit and change tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for customer-specific extensions.

Common Use Cases and Queries

Because JTF_TASK_PHONES is a link table, the most common access pattern is a join to resolve the phone numbers attached to a task's contacts. A typical query joins through JTF_TASK_CONTACTS and HZ_CONTACT_POINTS:

  • Retrieving all phone pointers for a given task contact: SELECT tp.task_phone_id, tp.phone_id, tp.primary_flag FROM jtf_task_phones tp WHERE tp.task_contact_id = :contact_id;
  • Resolving the actual phone details: join tp.phone_id to hz_contact_points.contact_point_id to return the phone number, area code, and contact point type.
  • Identifying the primary number for a contact: SELECT phone_id FROM jtf_task_phones WHERE task_contact_id = :contact_id AND primary_flag = 'Y';
  • Change-data / audit reporting: filter on last_update_date and last_updated_by to trace maintenance activity against the pointer records.
  • Security partitioning checks: filter on security_group_id when developing custom reports or data extracts.

Reporting use cases include CRM activity reports that list all communication channels associated with a task, contact-center dashboards that surface primary numbers, and data-quality audits that detect contacts with no phone pointers or multiple primary flags.

Related Objects

The following objects are directly referenced by or related to JTF_TASK_PHONES through the documented constraints and implementation data:

  • JTF_TASK_CONTACTS — referenced via JTF_TASK_PHONES.TASK_CONTACT_ID; the immediate parent of the pointer record.
  • HZ_CONTACT_POINTS — referenced via JTF_TASK_PHONES.PHONE_ID; supplies the actual telephone data (TCA model).
  • FND_SECURITY_GROUPS — referenced via JTF_TASK_PHONES.SECURITY_GROUP_ID; governs row-level access.
  • JTF_TASK_PHONES_PK and JTF_TASK_PHONES_U1 — the primary key constraint and unique index that enforce TASK_PHONE_ID uniqueness.
  • JTF_TASKS and JTF_TASK_ASSIGNMENTS — the task header and assignment entities that drive the CRM task model which contacts and phones decorate.

Together with JTF_TASK_CONTACTS and HZ_CONTACT_POINTS, JTF_TASK_PHONES completes the task-contact-telephone chain used throughout CRM Foundation and its dependent application modules.