Results for “jtf_task_phones_v”

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

Overview

JTF_TASK_PHONES_V is an APPS-owned view within the JTF – CRM Foundation product family. It is documented as an internal view for JTF_TASK_PHONES, exposing the association between tasks, task contacts, and phone records in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents task phone relationships, including the linking identifiers TASK_PHONE_ID, TASK_CONTACT_ID, and PHONE_ID, along with audit columns, descriptive attributes, and DFF (descriptive flexfield) columns.

Because the view is flagged as internal, it is not intended as a supported integration interface; however, it serves reporting and diagnostic queries that need to resolve phone numbers associated with task contacts. The presence of TASK_CONTACT_ID makes it directly relevant to users investigating task contact linkage, since JTF_TASK_PHONES records the phone numbers tied to a given task contact.

Underlying Base Objects

The view is defined over the base object JTF_TASK_PHONES, which appears as a SYNONYM in the documented metadata. The view performs a simple projection from this base table, selecting ROWID (aliased ROW_ID) and all listed columns without joins or filters. Consequently, the view is a thin wrapper: it does not aggregate, transform, or restrict data beyond the column list. Any DML restrictions, row-level security, or business rules originate in the base table or the application layer, not in the view itself.

Key Columns

• ROW_ID – The ROWID of the underlying JTF_TASK_PHONES row.
• TASK_PHONE_ID – Primary identifier for the task phone record.
• TASK_CONTACT_ID – The task contact to which the phone record is linked; central to searches involving task contacts.
• PHONE_ID – Reference to the phone number record.
• OWNER_TABLE_NAME – Indicates the owning entity for the phone association.
• PRIMARY_FLAG – Indicates whether the phone entry is the primary number.
• OBJECT_VERSION_NUMBER – Optimistic locking column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield context and segments.

Columns such as TASK_CONTACT_ID, PHONE_ID, PRIMARY_FLAG, and OWNER_TABLE_NAME are the most useful for reporting, since they expose the logical relationship between tasks, contacts, and phone numbers.

Common Use Cases and Queries

The most common scenario is retrieving all phone numbers associated with a specific task contact. For example:

SELECT task_phone_id, task_contact_id, phone_id, primary_flag FROM apps.jtf_task_phones_v WHERE task_contact_id = :task_contact_id;

To identify the primary phone for each task contact:

SELECT task_contact_id, phone_id FROM apps.jtf_task_phones_v WHERE primary_flag = 'Y';

To review audit and DFF data for reconciliation:

SELECT task_phone_id, task_contact_id, phone_id, created_by, creation_date, attribute_category FROM apps.jtf_task_phones_v ORDER BY creation_date DESC;

Because the view is a direct projection, filtering on TASK_CONTACT_ID or PRIMARY_FLAG leverages any indexes on the base table. Queries should generally join PHONE_ID to the phone number table to obtain the actual phone number, since the view itself exposes only the identifier.