Search Results hz_cust_contact_points




Overview
Explore in AI Chat

Overview

The HZ_CUST_CONTACT_POINTS table is a legacy data object within the Oracle E-Business Suite (EBS) Receivables (AR) module. As explicitly stated in the official ETRM documentation, this table is no longer used in the application's active architecture for versions 12.1.1 and 12.2.2. It historically served as part of the Trading Community Architecture (TCA) foundation, which manages customer and organization information. Its role was to store contact point information, such as phone numbers or email addresses, specifically associated with customer accounts, their sites, and the roles individuals played at those sites. In modern implementations, its functionality has been entirely superseded by other TCA tables, rendering it obsolete for current development or reporting.

Key Information Stored

While the table is deprecated, its structure reveals the historical data model for customer contacts. The primary key, CUST_CONTACT_POINT_ID, uniquely identified each contact point record. The table's foreign key relationships indicate it stored links to three core customer entities: a specific CUST_ACCOUNT_ID from HZ_CUST_ACCOUNTS, a physical location via CUST_ACCOUNT_SITE_ID from HZ_CUST_ACCT_SITES_ALL, and a person's function via CUST_ACCOUNT_ROLE_ID from HZ_CUST_ACCOUNT_ROLES. This design allowed a contact point (e.g., a billing telephone number) to be associated at the account level, site level, or a specific contact role level. The table likely contained columns for the actual contact data (phone, email, etc.) and status flags, though these are not detailed in the provided metadata.

Common Use Cases and Queries

Given its deprecated status, there are no supported use cases for the HZ_CUST_CONTACT_POINTS table in EBS 12.1.1 or 12.2.2. Direct queries against this table for reporting or integration are strongly discouraged, as the table is not maintained by the application and contains stale data. If historical data analysis is absolutely necessary, any query would be investigative and for legacy data cleanup purposes only. A sample pattern to identify remaining data would be:

  • SELECT cust_account_id, cust_account_site_id, cust_account_role_id, COUNT(*)
  • FROM ar.hz_cust_contact_points
  • GROUP BY cust_account_id, cust_account_site_id, cust_account_role_id;

For all operational and reporting needs, contemporary TCA tables like HZ_CONTACT_POINTS and HZ_PARTY_CONTACT_POINTS must be used instead.

Related Objects

The ETRM metadata documents three specific foreign key relationships from HZ_CUST_CONTACT_POINTS to active core TCA tables. These relationships highlight the entities to which a contact point was historically linked:

  • HZ_CUST_ACCOUNTS: Linked via the CUST_ACCOUNT_ID column. This associated the contact point with a customer account definition.
  • HZ_CUST_ACCT_SITES_ALL: Linked via the CUST_ACCOUNT_SITE_ID column. This associated the contact point with a specific customer site (e.g., a billing or shipping address).
  • HZ_CUST_ACCOUNT_ROLES: Linked via the CUST_ACCOUNT_ROLE_ID column. This associated the contact point with a specific individual's role (e.g., "Accounts Payable Contact") at a customer account or site.

These relationships confirm the table's former position within the customer hierarchy but do not imply current data flow or dependency.