Search Results hz_thin_st_cpts




Overview
Explore in AI Chat

Overview

The HZ_THIN_ST_CPTS table is a Receivables (AR) schema object that forms part of the Oracle E-Business Suite Trading Community and contact point data model. In Oracle EBS 12.1.1 and 12.2.2, "HZ" designates objects belonging to the Trading Community Architecture (TCA) registry, and this table participates in the thin (denormalized) representation of contact points associated with parties, party sites, and persons. It supplies a lightweight, indexed access path to contact point relationships without requiring traversal of the full contact-point hierarchy used by the broader TCA model.

The ETRM metadata classifies this object, using a heuristic mined from its foreign-key structure, as a standalone model rather than a hub, link, or satellite. This classification should be treated as a modeling suggestion: the table does not behave as a pure reference or junction table, but instead carries its own business-key uniqueness constraints and row-level attributes. It is best understood as a denormalized convenience structure within the AR subledger, not as a canonical Data Vault component.

Key Information Stored

The documented physical schema comprises ten columns. The most significant are the identifiers that constitute the business keys and the relationship references:

  • PARTY_ID — The trading community party identifier, the primary owner of the contact point relationship.
  • CONTACT_POINT_ID — The contact point (phone, email, fax, URL, etc.) being associated with the party.
  • PERSON_PARTY_ID — The person party identifier, used where the contact point is attributed to an individual rather than an organization.
  • PARTY_SITE_ID — The party site to which the contact point is linked.
  • PARTITION_ID — The partition reference, which the documented foreign key ties to JTF_FM_PARTITION_X_REQUEST. This supports partitioning strategy in large implementations.
  • QKEY — A qualifier key that distinguishes contact points of the same type or function for a given party or person.
  • ORG_CONTACT_ID — The organization contact identifier for organization-level contact points.
  • PARENT_ROWID — A rowid pointer to the parent record, supporting hierarchical navigation within the thin structure.
  • CONCAT_COL — A concatenated derived column, typically used for indexing or rapid lookup of combined key values.
  • STATUS_FLAG — Indicates the active/inactive state of the contact point association.

The surrogate primary key is not separately enumerated in the documented metadata; the business-key candidates are defined by two unique indexes. HZ_THIN_ST_CPTS_U1 covers (PARTY_ID, QKEY, CONTACT_POINT_ID), and HZ_THIN_ST_CPTS_U2 covers (PERSON_PARTY_ID, QKEY, CONTACT_POINT_ID). These indexes enforce uniqueness of a contact point per qualifier key for either a party or a person.

Common Use Cases and Queries

Typical uses include resolving all contact points for a customer or person quickly, filtering active contact points via STATUS_FLAG, and reporting on contact points by party site. A representative query joins the table to the party and contact point registries:

  • SELECT c.PARTY_ID, c.CONTACT_POINT_ID, c.QKEY, c.STATUS_FLAG FROM HZ_THIN_ST_CPTS c WHERE c.PARTY_ID = :p_party_id AND c.STATUS_FLAG = 'A';
  • Person-level lookups use the second unique index: WHERE PERSON_PARTY_ID = :p_person_id.
  • Partition-scoped extracts filter on PARTITION_ID against JTF_FM_PARTITION_X_REQUEST.

Because the table is denormalized, reports avoid deep joins to the full contact point model, improving performance for high-volume customer master extracts.

Related Objects

The documented foreign key links PARTITION_ID to JTF_FM_PARTITION_X_REQUEST, which governs partition assignment. Other commonly joined objects in this domain include HZ_PARTIES (on PARTY_ID), HZ_CONTACT_POINTS (on CONTACT_POINT_ID), HZ_PERSON_PROFILES or HZ_PARTY_SITES (on PERSON_PARTY_ID and PARTY_SITE_ID respectively), and HZ_ORG_CONTACTS (on ORG_CONTACT_ID). These relationships make HZ_THIN_ST_CPTS a supporting access structure within the TCA registry.