Results for “cust_account_site_id”

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

Overview

HZ_CUST_CONTACT_POINTS is a table owned by the AR (Receivables) schema in Oracle E-Business Suite, present and marked VALID in both release 12.1.1 and 12.2.2. Despite its VALID status, the ETRM metadata explicitly states that "this table is no longer used." This designation reflects the broader migration of customer contact information into the Oracle Trading Community Architecture (TCA) model, where contact points are now managed centrally through the HZ_CONTACT_POINTS and related HZ entity relationship tables rather than through a customer-specific contact point table. The object therefore persists primarily as a legacy artifact retained for backward compatibility, historical data retention, and referential integrity, but it is not part of the current functional flow for capturing or maintaining customer contacts.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This is a modeling suggestion: the table's three foreign keys connect a customer account, an account site, and an account role to a contact point, which is the classic pattern of a link (association) table resolving relationships between hubs. The table does not hold a large volume of descriptive attributes, consistent with the link classification.

Key Information Stored

HZ_CUST_CONTACT_POINTS contains 15 documented columns. The most important are summarized below.

• CUST_CONTACT_POINT_ID — the surrogate primary key, enforced by the unique index HZ_CUST_CONTACT_POINTS_U1 and the constraint HZ_CUST_CONTACT_POINTS_PK. This is the single documented unique business-key candidate and should be treated as the stable identifier for a row.
• CUST_ACCOUNT_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the customer account to which the contact point applies.
• CUST_ACCOUNT_SITE_ID — foreign key to HZ_CUST_ACCT_SITES_ALL, scoping the contact point to a specific customer account site.
• CUST_ACCOUNT_ROLE_ID — foreign key to HZ_CUST_ACCOUNT_ROLES, associating the contact point with a customer account role.
• CONTACT_POINT_ID — reference to the underlying TCA contact point record (e.g., phone, email, web, fax), linking the customer-side association to the centralized contact point definition. Note that no foreign key to HZ_CONTACT_POINTS is documented in ETRM.
• STATUS — a status indicator controlling the active/inactive state of the row.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide the standard "WHO" audit trail.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE track the concurrent request that last touched the row.

Common Use Cases and Queries

Because the table is documented as no longer used, practical activity is limited to legacy reporting, data migration validation, and historical reconciliation. Typical patterns include confirming whether historical contact-point associations still exist for a given account, and tracing which underlying TCA contact points were once attached to a customer role or site.

• Historical contact lookup by account: SELECT cust_contact_point_id, cust_account_id, cust_account_site_id, contact_point_id, status FROM hz_cust_contact_points WHERE cust_account_id = :p_account_id;
• Role-based filtering: join to HZ_CUST_ACCOUNT_ROLES to identify contact points previously held by specific roles.
• Migration gap analysis: compare surviving rows against current TCA contact point data to identify records requiring archival or mapping.
• Audit and lineage: use REQUEST_ID, PROGRAM_ID, and the CREATED/LAST_UPDATE columns to attribute historical changes.

Consumers should generally not build new integrations on this table; the modern equivalent should be sourced from TCA contact point structures.

Related Objects

• HZ_CUST_ACCOUNTS — joined via HZ_CUST_CONTACT_POINTS.CUST_ACCOUNT_ID; the customer account hub.
• HZ_CUST_ACCT_SITES_ALL — joined via HZ_CUST_CONTACT_POINTS.CUST_ACCOUNT_SITE_ID; the account site.
• HZ_CUST_ACCOUNT_ROLES — joined via HZ_CUST_CONTACT_POINTS.CUST_ACCOUNT_ROLE_ID; the account role association.
• HZ_CONTACT_POINTS — the centralized TCA contact point definition referenced by CONTACT_POINT_ID; the functional successor for contact data.
• HZ_CUST_CONTACT_POINTS_PK / HZ_CUST_CONTACT_POINTS_U1 — the primary key constraint and unique index defined on CUST_CONTACT_POINT_ID.

These relationships reflect the documented foreign key and index metadata and should be validated against the target instance before use in production reporting.