Results for “hz_staged_contact_points”

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

Overview

HZ_STAGED_CONTACT_POINTS is a staging table owned by the AR schema in Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its purpose, per the ETRM metadata, is to hold contact point information staged for Data Quality Management (DQM). In the Oracle Trading Community Architecture (TCA) model, contact points represent the individual communication channels — phone numbers, e-mail addresses, URLs, fax numbers, and similar entities — associated with a party, party site, or organization contact. Rather than writing directly to the production HZ_CONTACT_POINTS table, the DQM and bulk-import processes write records into HZ_STAGED_CONTACT_POINTS first, where cleansing, deduplication, and validation routines can inspect and transform the data before it is promoted to the base entity.

From a heuristic Data Vault perspective, the mined foreign-key structure classifies this table as a link. It associates an organization contact (ORG_CONTACT_ID) and a party site (PARTY_SITE_ID) with a contact point, operating as a transactional or batch staging structure rather than a pure reference hub or descriptive satellite. This classification is a modeling suggestion derived from the FK relationships, not an Oracle-declared attribute.

Key Information Stored

The documented physical schema contains 264 columns, an unusually wide footprint that reflects the generic column-slot design typical of TCA staging tables. The 10–15 most significant columns are:

• CONTACT_POINT_ID — The surrogate primary key, enforced by the unique index HZ_STAGED_CONTACT_POINTS_U1 and the only documented business-key candidate. It carries the identifier that will ultimately map to the contact point record.
• PARTY_ID — Identifies the party (person or organization) that owns the staged contact point.
• PERSON_PARTY_ID — Identifies the person party associated with the record, used where the contact point belongs to an individual rather than the organization.
• ORG_CONTACT_ID — Foreign key to HZ_ORG_CONTACTS, tying the contact point to a specific organizational contact role.
• PARTY_SITE_ID — Foreign key to HZ_PARTY_SITES, anchoring the contact point to a physical or logical party site.
• CONTACT_POINT_TYPE — Classifies the channel, for example phone, e-mail, or URL, and drives which attribute columns are meaningful.
• STATUS_FLAG — Indicates the processing state of the staged row (for example, active, inactive, or pending promotion).
• CONCAT_COL — A concatenated representation of the contact point, typically produced by DQM matching and deduplication logic.
• QKEY — A match or qualification key generated by DQM for identifying duplicate or related contact points.
• TX1 through TX255 — A large pool of generic text attribute slots. For a given CONTACT_POINT_TYPE, a defined subset of these columns holds the actual channel data (raw phone number, formatted e-mail address, and so on), while the remainder stay null.

Common Use Cases and Queries

Typical usage centers on monitoring the DQM staging pipeline, diagnosing records that fail to promote, and reconciling staged volumes against production contact points. A representative query lists unprocessed rows for a party:

• SELECT contact_point_id, contact_point_type, party_id, status_flag FROM hz_staged_contact_points WHERE party_id = :p_party_id AND status_flag = 'A';
• Joining to site and contact context: SELECT s.contact_point_id, s.party_site_id, s.org_contact_id, s.qkey FROM hz_staged_contact_points s, hz_party_sites ps WHERE s.party_site_id = ps.party_site_id;
• Counting staged rows by channel: SELECT contact_point_type, COUNT(*) FROM hz_staged_contact_points GROUP BY contact_point_type;

Reporting use cases include DQM batch throughput analysis, duplicate-detection audits based on QKEY and CONCAT_COL, and troubleshooting records orphaned by invalid party site or organization contact references.

Related Objects

The most significant related objects, grounded in the documented foreign keys and TCA dependencies, are:

• HZ_ORG_CONTACTS — Referenced via HZ_STAGED_CONTACT_POINTS.ORG_CONTACT_ID; supplies the organizational contact role context.
• HZ_PARTY_SITES — Referenced via HZ_STAGED_CONTACT_POINTS.PARTY_SITE_ID; supplies the site context for the staged contact point.
• HZ_CONTACT_POINTS — The production target to which validated staged rows are promoted.
• HZ_PARTIES — The party master, referenced indirectly through PARTY_ID and PERSON_PARTY_ID.
• HZ_PARTY_SITE_USES — Defines site usage context that governs how contact points are applied at a site.
• HZ_LOCATIONS — Provides the address detail underlying party sites associated with staged records.

These relationships confirm the table's role as a transient link within the TCA DQM staging flow rather than a persistent operational entity.