Search Results hz_contact_points




Overview
Explore in AI Chat

Overview

The HZ_CONTACT_POINTS table is a core component of the Oracle Trading Community Architecture (TCA) within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central repository for storing all electronic communication methods associated with parties, party sites, and other entities in the system. As defined in the ETRM, its primary role is to manage "Electronic methods of communicating with parties." This table enables the standardized storage of diverse contact point types—such as phone numbers, email addresses, fax numbers, and web addresses—for customers, suppliers, partners, and other parties, providing a unified model for contact information across all EBS modules.

Key Information Stored

The table's primary key is CONTACT_POINT_ID, which uniquely identifies each contact record. A critical design aspect is the OWNER_TABLE_ID and OWNER_TABLE_NAME columns, which implement a polymorphic foreign key relationship. This allows a contact point to be owned by various entities, most commonly a party (HZ_PARTIES) or a party site (HZ_PARTY_SITES), as indicated by the documented foreign keys. Key columns include CONTACT_POINT_TYPE (e.g., 'PHONE', 'EMAIL', 'FAX'), PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, EMAIL_ADDRESS, and URL. The STATUS column indicates if the contact point is 'A'ctive or 'I'nactive, and the PRIMARY_FLAG designates the preferred contact method of its type. The table also links to HZ_TIMEZONES via the TIMEZONE_ID foreign key for proper time zone management.

Common Use Cases and Queries

A primary use case is retrieving all active contact points for a specific customer party. This is essential for customer communications, support interactions, and marketing. Another common scenario involves identifying the primary phone or email for a bill-to or ship-to location (party site) for order fulfillment or shipping notifications. Developers often query this table to populate contact information in custom reports or interfaces.

Sample SQL to fetch phone contacts for a party:

  • SELECT cp.phone_country_code, cp.phone_area_code, cp.phone_number, cp.primary_flag
  • FROM hz_contact_points cp
  • WHERE cp.owner_table_name = 'HZ_PARTIES'
  • AND cp.owner_table_id = :p_party_id
  • AND cp.contact_point_type = 'PHONE'
  • AND cp.status = 'A'
  • ORDER BY cp.primary_flag DESC, cp.last_update_date DESC;

Integration points, as shown in the metadata, are extensive, including Service Requests (CS_INCIDENTS_ALL_B), Sales Leads (AS_SALES_LEADS), and Order Management interfaces (OE_HEADERS_IFACE_ALL).

Related Objects

HZ_CONTACT_POINTS is deeply integrated into the TCA model and numerous application modules. Its primary relationships, as documented, are with the HZ_PARTIES and HZ_PARTY_SITES tables, which are the most common owners of contact points. The HZ_TIMEZONES table is a direct foreign key reference. Crucially, the ETRM metadata lists over a dozen foreign key relationships from application tables, demonstrating its enterprise-wide usage. Key referencing objects include AR_CUSTOMER_CALLS_ALL (for call logging), CS_INCIDENTS_ALL_B (for service request customer contact info), AS_SALES_LEADS (for lead contact details), and JTF_TASK_PHONES (for task management). This wide integration underscores that HZ_CONTACT_POINTS is the definitive source for electronic contact data across Oracle EBS.