Results for “jtf_contact_points_v”

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

Overview

JTF_CONTACT_POINTS_V is a CRM Foundation (JTF) view owned by the APPS schema that presents the contact details of each party, such as telephone numbers, e-mail addresses, and web URLs. It is defined as a simple join between HZ_PARTIES and HZ_CONTACT_POINTS and provides a denormalized, reporting-friendly projection of party identity attributes alongside the underlying contact point records. Because the view exposes descriptive party columns (party number, party name, person first and last name, party type) together with the full set of contact point attributes, it is frequently used in EBS 12.1.1 and 12.2.2 as a single-source query surface for party communication data.

For users searching on telephone_type, this view is directly relevant: it exposes the TELEPHONE_TYPE column from HZ_CONTACT_POINTS, which classifies phone records (for example, home, work, mobile, fax) and is commonly used to filter a party's contact list to a specific phone category.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms: HZ_CONTACT_POINTS and HZ_PARTIES. The join is an outer join from parties to contact points:

• CONT_POINT.OWNER_TABLE_ID (+) = PARTY.PARTY_ID
• CONT_POINT.OWNER_TABLE_NAME (+) = 'HZ_PARTIES'

Because the contact point side of the join is outer-joined, every party in HZ_PARTIES is returned even when no matching contact point exists; in that case the contact-related columns are null. Only contact points whose owner table name is 'HZ_PARTIES' are associated with a party, which scopes the view to party-owned contact points and excludes contact points owned by other entities (such as organizations or locations that use a different OWNER_TABLE_NAME). The view is read-only with respect to the party record and is used exclusively for query and reporting purposes.

Key Columns

The view exposes party identity columns and the complete set of HZ_CONTACT_POINTS columns, including:

• PARTY_ID, PARTY_NUMBER, PARTY_NAME, PARTY_TYPE – identity and classification of the party.
• PERSON_FIRST_NAME, PERSON_LAST_NAME – name components for person parties.
• CONTACT_POINT_ID – primary key of the underlying contact point.
• CONTACT_POINT_TYPE – the contact method category (for example, PHONE, EMAIL, URL).
• TELEPHONE_TYPE – the classification of a phone contact point, the attribute most often used to isolate a specific phone category.
• PHONE_NUMBER, PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_EXTENSION, PHONE_LINE_TYPE – telephony details.
• EMAIL_ADDRESS, EMAIL_FORMAT, URL, WEB_TYPE – electronic contact details.
• PRIMARY_FLAG, STATUS – whether the contact point is the party's primary method and its active status.
• ORIG_SYSTEM_REFERENCE, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID – provenance and concurrent program audit information.
• TIME_ZONE, BEST_TIME_TO_CONTACT_START, BEST_TIME_TO_CONTACT_END – contact timing preferences.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – the standard EBS descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY – audit columns.

Common Use Cases and Queries

The view is typically used to list every phone, e-mail, or web address for a party, to identify the primary contact method, or to filter by TELEPHONE_TYPE. Two representative queries follow.

Retrieve all phone contact points for a party, filtered by telephone type:

• SELECT party_id, party_name, contact_point_id, telephone_type, phone_country_code, phone_area_code, phone_number, primary_flag FROM jtf_contact_points_v WHERE party_id = :p_party_id AND contact_point_type = 'PHONE' AND telephone_type = 'MOBILE' ORDER BY primary_flag DESC;

List the primary e-mail address for each person party:

• SELECT party_number, person_first_name, person_last_name, email_address FROM jtf_contact_points_v WHERE contact_point_type = 'EMAIL' AND primary_flag = 'Y' AND status = 'A';

Because the outer join returns parties without contact points, reports that require an existing contact should include a predicate such as contact_point_id IS NOT NULL to suppress rows where the party has no matching contact record. Standard partitioning and indexing of HZ_CONTACT_POINTS on OWNER_TABLE_ID, OWNER_TABLE_NAME, and CONTACT_POINT_TYPE governs the performance characteristics of queries against this view.