Search Results dqcontact_point_id




Overview
Explore in AI Chat

Overview

HZ_DQM_CS_CPT_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, catalogued under the Receivables (AR) product family. The object belongs to the Data Quality Management (DQM) subsystem, which supports Oracle's Customer Data Quality and duplicate-resolution facilities. The "CS_CPT" component of the name indicates that the view surfaces contact point data used within a matching or scoring context, while the trailing "_V" confirms its identity as a view rather than a stored table.

The view presents a flattened, denormalized projection of party site contact points, exposing the party site identifier, contact point type, primary indicators, status, and a decoded contact value in a single row per contact point. Its purpose is to give callers—typically PL/SQL matching routines, concurrent programs, and custom reports—a convenient access path to contact points without repeatedly joining the underlying contact point and party site entities. Because the view references a global temporary table and a helper package, it is intended for use within the DQM matching session rather than as a general-purpose reporting source.

Underlying Base Objects

The view is defined over three base objects and one package, all resolved through APPS synonyms in the documented metadata:

  • HZ_PARTY_SITES — the primary driving entity, supplying PARTY_SITE_ID. This is the party site record to which each contact point is attached.
  • HZ_CONTACT_POINTS — the source of contact point attributes, joined where OWNER_TABLE_NAME equals 'HZ_PARTY_SITES' and OWNER_TABLE_ID equals the party site identifier. Because OWNER_TABLE_ID is also compared to the matched-contact-points global temporary table, the join semantics are tightly scoped to the DQM matching session.
  • HZ_MATCHED_CPTS_GT — a global temporary table holding matched contact points for the current search context. It is outer-joined (denoted by the (+) markers) so that unmatched contact points are retained and scored as -1 via the DECODE expression in the ORDER BY.
  • ARH_DQM_TREE_HELPER — a helper package whose CTXMAX function supplies the active SEARCH_CONTEXT_ID, restricting the temporary table to the current matching context.

Key Columns

  • DQPARTY_SITE_ID — the party site identifier, aliased from HZ_PARTY_SITES.PARTY_SITE_ID. This is the value users reference when searching for "dqparty_site_id" and is the principal key linking the view to site-level entity data.
  • DQCONTACT_POINT_ID — the unique identifier of the contact point record within HZ_CONTACT_POINTS.
  • DQCONTACT_POINT_TYPE — the classification of the contact point, such as EMAIL, PHONE, TLX, or WEB.
  • DQPRIMARY_BY_PURPOSE and DQPRIMARY_FLAG — indicators identifying whether the contact point is primary for its purpose or flagged as primary overall.
  • DQSTATUS — the lifecycle status of the contact point record.
  • DQCONTACT_INFO — a decoded, human-readable contact value derived by DECODE on the contact point type, returning EMAIL_ADDRESS for EMAIL, RAW_PHONE_NUMBER for PHONE, TELEX_NUMBER for TLX, and URL for WEB.

Common Use Cases and Queries

The view is most frequently queried during duplicate identification and data cleansing exercises, where analysts need to inspect the contact points associated with a set of party sites. A typical retrieval filters on the party site identifier:

  • SELECT dqparty_site_id, dqcontact_point_type, dqcontact_info, dqstatus FROM hz_dqm_cs_cpt_v WHERE dqparty_site_id = :party_site_id;
  • SELECT dqparty_site_id, dqcontact_info FROM hz_dqm_cs_cpt_v WHERE dqcontact_point_type = 'EMAIL' AND dqprimary_flag = 'Y';
  • SELECT dqcontact_point_type, COUNT(*) FROM hz_dqm_cs_cpt_v GROUP BY dqcontact_point_type;

Because the result set is ordered by the matching score in descending order, the highest-confidence matches appear first, which is useful when reviewing candidate duplicates. Note that the SEARCH_CONTEXT_ID is obtained from ARH_DQM_TREE_HELPER.CTXMAX, so queries executed outside an active DQM matching context may return all contact points with a null score and therefore appear in arbitrary top-to-bottom ordering. For production matching logic, invoke the view from within the DQM process that establishes the context rather than from ad hoc SQL sessions.