Search Results hz_staged_contact_points

Overview

The HZ_STAGED_CONTACT_POINTS table is a core data staging object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Receivables (AR) module. It functions as a temporary holding area for contact point information that is being processed by the Data Quality Management (DQM) engine. DQM is a framework within Oracle Trading Community Architecture (TCA) responsible for cleansing, standardizing, and deduplicating customer and related data. This table's primary role is to decouple the data entry or import process from the complex validation and merging logic of DQM, allowing contact point details—such as phone numbers, email addresses, and web URLs—to be staged, evaluated, and then applied to the master TCA tables upon successful processing.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and foreign key relationships define its core structure. It holds transient records for various types of contact points. Key fields typically include a unique staged record identifier, the contact point type (e.g., PHONE, EMAIL, WEB), and the actual contact point value. Crucially, it stores foreign key references to link the staged data to its associated master records in the Trading Community Registry. The documented foreign keys highlight two critical linkage columns: ORG_CONTACT_ID, which references HZ_ORG_CONTACTS to associate the contact point with a specific organizational contact person, and PARTY_SITE_ID, which references HZ_PARTY_SITES to associate it with a specific party location. Other common columns would track the staging status, DQM processing flags, and error messages.

Common Use Cases and Queries

The primary use case involves batch operations where large volumes of customer contact data are created or updated via interfaces, such as CRM or legacy system migrations. Data is first inserted into this staging table. A typical operational query would identify records pending DQM processing or those that have failed validation. For example: SELECT staged_contact_point_id, contact_point_type, contact_point_value, status FROM hz_staged_contact_points WHERE status = 'PENDING'; Reporting use cases focus on auditing and monitoring the DQM workflow. Analysts may run queries to summarize staged contact points by type or to join with the related party site or org contact tables to see the full context of data awaiting integration into the operational TCA base tables (HZ_CONTACT_POINTS, HZ_PARTIES).

Related Objects

This table has defined foreign key relationships with two fundamental TCA master tables, as per the provided metadata:

• HZ_ORG_CONTACTS: The HZ_STAGED_CONTACT_POINTS.ORG_CONTACT_ID column references this table. This links staged contact points to a specific person contact within an organization.
• HZ_PARTY_SITES: The HZ_STAGED_CONTACT_POINTS.PARTY_SITE_ID column references this table. This links staged contact points to a specific physical or electronic address of a party.

Furthermore, HZ_STAGED_CONTACT_POINTS is intrinsically related to the core HZ_CONTACT_POINTS table, which is the ultimate destination for cleansed and approved contact point data. It is also managed by DQM-specific APIs and programs within the AR and TCA product suites.