Search Results time_zone




Overview
Explore in AI Chat

Overview

HZ_CONTACT_POINTS is the TCA (Trading Community Architecture) hub table that stores the electronic methods of communicating with parties and party sites. It resides in the AR schema and is documented as VALID under the Receivables product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The table captures structured communication channels — phone numbers, e-mail addresses, URLs, telex numbers, and EDI/EFT routing attributes — that describe how an organization reaches a customer, supplier, contact, prospect, or physical location.

The table maintains a polymorphic ownership model. Rather than holding a single dedicated foreign key to one parent, it uses an OWNER_TABLE_NAME / OWNER_TABLE_ID pair to point back to HZ_PARTIES or HZ_PARTY_SITES, with TIMEZONE_ID resolving to HZ_TIMEZONES for time-zone normalization of phone contacts. Each row is uniquely identified by the primary key HZ_CONTACT_POINTS_PK on CONTACT_POINT_ID, and the unique index HZ_CONTACT_POINTS_U1 on the same column confirms it as the business-key candidate.

Following the heuristic Data Vault classification supplied with the metadata, HZ_CONTACT_POINTS is hub-leaning: it holds a durable, uniquely identifiable business key (CONTACT_POINT_ID) and is referenced by a broad fan of downstream transactional and CRM tables. In a Data Vault model it would typically be treated as a hub, with links attaching phone/email usage in calls, sales leads, service requests, order headers, and marketing lists.

Key Information Stored

The table contains 105 documented columns, but the majority of analytical and integration value concentrates in a focused subset:

Common Use Cases and Queries

Typical usage centers on retrieving the correct contact channel for a party or site — for customer communications, order-to-cash processing, and CRM/service activities. A common reporting pattern filters to active, primary contact points for a specific party:

  • Phone lookup for a party: join HZ_CONTACT_POINTS to HZ_PARTIES on OWNER_TABLE_ID = PARTY_ID, filtering OWNER_TABLE_NAME = 'HZ_PARTIES', STATUS = 'A', and CONTACT_POINT_TYPE = 'PHONE'.
  • E-mail extraction for campaigns: select EMAIL_ADDRESS where CONTACT_POINT_TYPE = 'EMAIL' and DO_NOT_USE_FLAG is null or 'N'.
  • Site-level contact resolution: join to HZ_PARTY_SITES where OWNER_TABLE_NAME = 'HZ_PARTY_SITES' to obtain the location-specific phone or address channel.
  • Data quality and de-duplication: query TRANSPOSED_PHONE_NUMBER and RAW_PHONE_NUMBER to identify duplicate phone numbers across owners.
  • Service request and call tracing: join CONTACT_POINT_ID to CS_INCIDENTS_ALL_B.CUSTOMER_PHONE_ID, AR_CUSTOMER_CALLS_ALL.PHONE_ID, or JTF_TASK_PHONES.PHONE_ID to reconstruct which number was used on an interaction.
  • EDI/EFT onboarding: select the EDI_* and EFT_* columns for trading partners being enabled for electronic transactions.

Because the table is a central TCA hub, queries frequently drive from HZ_PARTIES or HZ_PARTY_SITES outward and join on OWNER_TABLE_ID, always constraining OWNER_TABLE_NAME to disambiguate the polymorphic parent.

Related Objects

The reference topology of HZ_CONTACT_POINTS is broad, reflecting its role as a shared contact hub. The most significant related objects include:

These relationships establish HZ_CONTACT_POINTS as the canonical reference for communication channels across Receivables, Service, Order Management, Sales, and Marketing, which is why it must be treated as a governed core entity in any integration or reporting design.