Search Results hz_matched_cpts_gt




Overview
Explore in AI Chat

Overview

APPS.HZ_DQM_CS_CPT_V is a database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model that supports the Customer Data Quality Management (DQM) matching and deduplication infrastructure. It presents contact point records associated with party sites, joined optionally to the global temporary table HZ_MATCHED_CPTS_GT, which holds intermediate match results generated during a data quality matching run. The view's purpose is to expose a consolidated, purpose-ready result set for contact points—email addresses, phone numbers, telex numbers, and web URLs—together with their match scores, ordered from highest to lowest relevance.

In reporting and integration contexts, this view acts as a read-only projection layer over the base contact point and party site entities. It is a typical dependency of the object HZ_MATCHED_CPTS_GT, which was the user's original search term; the view is the primary consumer that reads matched results and presents them in a business-usable form. Administrators and developers inspecting DQM match output use it to verify which contact points matched for a given party site and to understand match ranking through the score column and its ORDER BY clause.

Underlying Base Objects

The documented referenced base objects are:

  • HZ_PARTY_SITES (SYNONYM) — supplies the party site identifier used as the owner of each contact point.
  • HZ_CONTACT_POINTS (SYNONYM) — the primary source of contact point attributes, filtered to owner_table_name = 'HZ_PARTY_SITES'.
  • HZ_MATCHED_CPTS_GT (SYNONYM) — the global temporary table containing match results, including score and search context, joined via an outer join.
  • ARH_DQM_TREE_HELPER (PACKAGE) — provides the CTXMAX constant used to constrain the search context identifier.

The view joins HZ_CONTACT_POINTS to HZ_PARTY_SITES on owner_table_id = party_site_id, and outer-joins HZ_MATCHED_CPTS_GT on contact_point_id with an additional outer-join predicate restricting search_context_id to ARH_DQM_TREE_HELPER.CTXMAX. Because the match table is a global temporary table, the view returns meaningful matched results only within the session that populated that table during a DQM match operation.

Key Columns

The view exposes seven aliased columns, all prefixed with DQ to denote their data quality role:

The view does not project the match score as a named column; score is used exclusively in the ORDER BY clause via DECODE(g.score, NULL, -1, g.score) DESC, placing non-matched (NULL) rows last.

Common Use Cases and Queries

Typical use cases include auditing DQM match results, validating contact point resolution by type, and integrating clean contact data into downstream reporting.

Retrieving all matched contact points for a party site:

  • SELECT dqcontact_point_id, dqcontact_point_type, dqcontact_info, dqstatus FROM apps.hz_dqm_cs_cpt_v WHERE dqparty_site_id = :party_site_id;

Filtering to a specific contact type with primary designation:

  • SELECT dqparty_site_id, dqcontact_info FROM apps.hz_dqm_cs_cpt_v WHERE dqcontact_point_type = 'EMAIL' AND dqprimary_flag = 'Y';

Because results are pre-ordered by descending match score, consumers may rely on the view's ordering in direct fetches. Note that meaningful match scores depend on HZ_MATCHED_CPTS_GT being populated in the current session by the DQM matching process; otherwise only base contact point rows are returned.