Search Results subject_party_number




Overview
Explore in AI Chat

Overview

APPS.JTF_TASK_PARTY_CONTACTS_V is a reporting and integration view in the Oracle E-Business Suite Trading Community Architecture (TCA) data model. It presents party-to-party contact relationship information, resolving a subject party (the party being contacted) together with the related party (the contact or object of the relationship) into a single, denormalized row. The view is owned by APPS and is defined over the HZ_PARTIES, HZ_RELATIONSHIPS, HZ_RELATIONSHIP_TYPES, HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, and HZ_CODE_ASSIGNMENTS tables.

The name of the view suggests it originally served the JTF (Sales/TeleSales foundation) task and activity model, where a task or interaction is associated with parties and their designated contacts. In Oracle EBS 12.1.1 and 12.2.2, the view remains a convenient object for retrieving contact details tied to a party relationship without writing the full multi-table join manually. Reports, custom concurrent programs, and outbound integrations that require a flattened party contact list typically query this view rather than the base TCA tables directly.

Underlying Base Objects

The view is defined over the following documented base objects, joined as follows:

  • HZ_RELATIONSHIPS (REL) — the driving table, restricted to rows where DIRECTIONAL_FLAG = 'F', SUBJECT_TABLE_NAME = 'HZ_PARTIES', and OBJECT_TABLE_NAME = 'HZ_PARTIES'. It supplies relationship identifiers, dates, status, and the subject/object party keys.
  • HZ_PARTIES (PARTY_SUBJECT) — aliased as the subject party; joined via REL.SUBJECT_ID = PARTY_SUBJECT.PARTY_ID. Returns party number, party name, and person name attributes.
  • HZ_PARTIES (PARTY_REL) — aliased as the related party; joined via REL.PARTY_ID = PARTY_REL.PARTY_ID. Supplies email and postal address attributes.
  • HZ_RELATIONSHIP_TYPES and HZ_CODE_ASSIGNMENTS — an EXISTS subquery restricts results to relationship types assigned to the relationship type group PARTY_REL_GRP_CONTACTS.
  • HZ_CONTACT_POINTS (HCP) — outer-joined to the related party for the primary phone contact point (CONTACT_POINT_TYPE = 'PHONE', PRIMARY_FLAG = 'Y').
  • HZ_ORG_CONTACTS — supplies job title for organizational contacts.

Key Columns

Common Use Cases and Queries

Typical scenarios include retrieving all contact relationships for a given subject party, populating an outbound contact list, and driving customer-facing reports where the contact phone, email, and address are needed in one row.

  • List all contacts for a specific subject party: 
    SELECT subject_party_name, person_first_name, person_last_name,
       email_address, phone_number, job_title
FROM   apps.jtf_task_party_contacts_v
WHERE  subject_party_id = :p_party_id;
  • Retrieve contact details by relationship type: 
    SELECT subject_party_number, relationship_type,
       party_id, phone_number, email_address
FROM   apps.jtf_task_party_contacts_v
WHERE  relationship_type = :p_rel_type;
  • Report active contacts as of a date: 
    SELECT subject_party_name, person_last_name, city, country
FROM   apps.jtf_task_party_contacts_v
WHERE  TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);

Because the view exposes the PARTY_SUBJECT alias columns and the underlying HZ_PARTIES columns, consumers should be aware that the primary phone and address columns originate from the related party (PARTY_REL) through outer joins, and may therefore be null when no primary phone or related party record exists.