Search Results jtf_task_party_contacts_v




Overview
Explore in AI Chat

Overview

The JTF_TASK_PARTY_CONTACTS_V view is a reporting and integration object owned by the APPS schema within the JTF – CRM Foundation product. Its purpose is to expose contact information for both the subject and the object party of a relationship, using HZ_RELATIONSHIPS as the driving table. This design makes the view particularly relevant when parties on either side of a relationship must be presented together with their descriptive attributes, contact points, and phone details.

Because the view is defined in the CRM Foundation layer, it is commonly consumed by task management, resource and party resolution, and other CRM-facing components that need a unified contact listing. The view exposes data for the subject party and the object party, allowing a single query to return both sides of a relationship without requiring the caller to join HZ_PARTIES twice manually. The documented metadata notes that the view does not join with HZ_ORG_CONTACTS; however, the view text shows a reference to HZ_ORG_CONTACTS through the ORG_CONTACT alias. This distinction is important when assessing which contact attributes are reliably populated.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through synonyms in the APPS schema:

  • HZ_RELATIONSHIPS — the driving table, aliased REL, providing relationship identifiers, type, direction, start and end dates, and status.
  • HZ_PARTIES — referenced twice, once as PARTY_SUBJECT for the subject party and once as PARTY_REL for the object party.
  • HZ_CONTACT_POINTS — aliased HCP, supplying phone country code, area code, number, and extension.
  • HZ_ORG_CONTACTS — aliased ORG_CONTACT, supplying job title.
  • HZ_CODE_ASSIGNMENTS and HZ_RELATIONSHIP_TYPES — used in an EXISTS subquery to filter relationships by relationship type group, specifically the PAR class code.

The join predicates link REL.SUBJECT_ID to PARTY_SUBJECT.PARTY_ID and REL.PARTY_ID to PARTY_REL.PARTY_ID, with DIRECTIONAL_FLAG = 'F' and both subject and object table names constrained to HZ_PARTIES. The EXISTS clause restricts results to relationship types belonging to the configured relationship type group.

Key Columns

The view exposes a wide set of party and relationship columns. Subject party columns include SUBJECT_PARTY_ID, SUBJECT_PARTY_NUMBER, and SUBJECT_PARTY_NAME, alongside person name components such as PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_TITLE, and KNOWN_AS. Identification and tax attributes include PERSON_IDENTIFIER, JGZZ_FISCAL_CODE, TAX_NAME, and TAX_REFERENCE.

Relationship columns include RELATIONSHIP_ID, RELATIONSHIP_TYPE, SUBJECT_ID, OBJECT_ID, PARTY_ID, START_DATE, END_DATE, and STATUS. Contact columns include EMAIL_ADDRESS, address components (ADDRESS1 through ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY), and phone fields PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, and PHONE_EXTENSION. The JOB_TITLE column is supplied through the organization contact reference.

Common Use Cases and Queries

Typical scenarios include retrieving all contacts associated with a party for CRM tasks, resolving both sides of a relationship for display in a task or interaction form, and exporting contact details for downstream integration. A representative query follows:

  • SELECT SUBJECT_PARTY_ID, SUBJECT_PARTY_NAME, RELATIONSHIP_TYPE, EMAIL_ADDRESS, PHONE_NUMBER FROM JTF_TASK_PARTY_CONTACTS_V WHERE RELATIONSHIP_TYPE = :p_type;
  • SELECT SUBJECT_PARTY_NAME, PERSON_LAST_NAME, JOB_TITLE FROM JTF_TASK_PARTY_CONTACTS_V WHERE STATUS = 'A' AND START_DATE <= SYSDATE;

Because the view is not joined to HZ_ORG_CONTACTS in the documented description, consumers should validate population of JOB_TITLE and should not assume it is always returned. Queries should also account for the directional flag and relationship type group restrictions applied internally, which limit results to forward-direction relationships within the configured group.