Search Results get_primary_phone

Overview

JTF_TASK_UWQ_PVT is a private PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Task Manager and Universal Work Queue (UWQ) infrastructure. Its name derives from the JTF (CRM Foundation) task schema, the UWQ component, and the "_PVT" suffix that designates an internal, non-public API classification. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the definer, so callers must themselves possess the necessary object grants on the underlying CRM and Trading Community (HZ) tables.

The package header header comment states that it is used by the database view JTF_TASK_UWQ_MYOWN_V ("my own tasks"). That view presents task records assigned to the current user within the Universal Work Queue, and the package supplies scalar attribute look-ups — specifically the primary telephone number and primary e-mail address associated with a task — that the view cannot resolve from the JTF_TASK tables alone. The source file, jtfvtkqs.pls, was created 10-Apr-2002 and carries an original version number of 115.1, reflecting its long-standing role in the CRM task stack.

Key Procedures and Functions

The documented interface consists of two public functions, both of which accept a single task identifier and return a VARCHAR2 value:

• GET_PRIMARY_PHONE — Returns the primary telephone number associated with a given task. It resolves the task's designated contact to the appropriate phone contact point, providing the UWQ and Task Manager user interfaces with a single, canonical phone value for display or dialing.
• GET_PRIMARY_EMAIL — Returns the primary e-mail address associated with a given task. It performs the equivalent resolution for electronic mail contact points, giving callers the preferred e-mail address linked to the task's contact.

Both functions are declared before the package's END statement and are declared read-only in nature: they retrieve data rather than mutating task, contact, or contact-point records. Their shared signature pattern — one numeric task identifier in, one character value out — makes them convenient for direct reference from SQL, including the columns of JTF_TASK_UWQ_MYOWN_V.

Tables Accessed

The package reads through three documented tables, accessed via APPS synonyms:

• JTF_TASK_CONTACTS — The association between a task and its contacts. This is the entry point for resolving which contact is relevant to a given task identifier, and it anchors the join to the remaining tables.
• HZ_CONTACT_POINTS — The Trading Community contact-point repository holding phone numbers, e-mail addresses, and other communication methods. The functions filter this table for the primary contact point of the appropriate contact-point type (telephone or e-mail).
• JTF_TASK_PHONES — Task-specific phone information, consulted as part of phone resolution alongside the HZ contact-point data.

No inserts, updates, or deletes are documented, consistent with the retrieval-only purpose of the two functions.

Usage Notes

JTF_TASK_UWQ_PVT is classified as PVT, indicating it is intended for internal consumption by Oracle's own CRM components rather than as a supported extension point for customer code. It is referenced by three other packages, and its principal documented consumer is the JTF_TASK_UWQ_MYOWN_V view. Application logic that queries that view, or the Universal Work Queue UI it feeds, triggers these functions implicitly.

Developers working in Oracle EBS 12.1.1 or 12.2.2 may encounter the package when troubleshooting missing phone or e-mail values in the Task Manager or UWQ regions. Because the functions take only a task identifier, they are easily invoked ad hoc from SQL*Plus for diagnostic purposes, for example by selecting GET_PRIMARY_PHONE for a specific task. Custom development should favor the public Task Manager APIs rather than calling this PVT package directly, since private interfaces are subject to change without notice across patch levels.