Search Results hz_dqm_cs_c_v




Overview
Explore in AI Chat

Overview

HZ_DQM_CS_C_V is a read-only view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Receivables (AR) product family and is part of the Data Quality Management (DQM) infrastructure used by the Customer/Contact search and duplicate-prevention framework. The view joins customer account roles, party relationships, organization contacts, and lookup meanings to present a flattened, denormalized result set of contact candidates. Notably, the view text is ordered by the match score produced by the HZ_MATCHED_CONTACTS_GT global temporary table, applied through a DECODE on the SCORE column in descending order so that the closest matches surface first. Several columns carry a DQ prefix, which identifies them as attributes consumed directly by DQM search pages and merge/duplicate resolution logic rather than as ordinary transactional data columns.

Underlying Base Objects

The view is defined over the following documented objects:

  • HZ_CUST_ACCOUNT_ROLES (synonym) — principal source of customer account role and site identifiers; the driving table in the FROM clause.
  • HZ_PARTIES (synonym) — joined twice: once as party B for the relationship-type party and once as party D for the related party name. The alias D supplies DQPARTY_NAME.
  • HZ_RELATIONSHIPS (synonym) — links the relationship party to its directional, subject-table-qualified relationship record; restricted to DIRECTIONAL_FLAG = 'F' and SUBJECT_TABLE_NAME = 'HZ_PARTIES'.
  • HZ_ORG_CONTACTS (synonym) — provides organization contact identifiers, contact numbers, job title codes, and title codes.
  • AR_LOOKUPS (view) — joined twice to translate RESPONSIBILITY and CONTACT_TITLE lookup codes into their meanings.
  • HZ_MATCHED_CONTACTS_GT (synonym) — a global temporary table holding scored match results; the outer join on ORG_CONTACT_ID and SEARCH_CONTEXT_ID carries the score used for ordering.
  • ARH_DQM_TREE_HELPER (package) — supplies the CTXMAX package variable used to bind the current search context.
  • ARPT_SQL_FUNC_UTIL (package) — its GET_LOOKUP_MEANING function resolves the REGISTRY_STATUS lookup for the STATUS column.

Key Columns

  • DQCUST_ACCOUNT_ID — customer account identifier from HZ_CUST_ACCOUNT_ROLES.
  • DQCUST_ACCOUNT_ROLE_ID — customer account role identifier; also joined against the match table.
  • DQCUST_ACCT_SITE_ID — customer account site identifier; rows are excluded when this is null.
  • DQRELATIONSHIP_ID — relationship identifier linking the party to the contact.
  • DQORG_CONTACT_ID — organization contact identifier used in match scoring.
  • DQPARTY_NAME — name of the related party from HZ_PARTIES alias D.
  • DQTITLE / DQJOB_TITLE — lookup meanings for CONTACT_TITLE and RESPONSIBILITY respectively.
  • DQCONTACT_NUMBER — contact number from HZ_ORG_CONTACTS.
  • DQSTATUS / DQSTATUSM — raw status code and its REGISTRY_STATUS lookup meaning, defaulting to the raw value when no meaning exists.

Common Use Cases and Queries

The view is typically queried during duplicate customer/contact review, merge candidate selection, and DQM tree searches. A representative query retrieves scored candidates for the active search context:

SELECT DQPARTY_NAME, DQCONTACT_NUMBER, DQTITLE, DQJOB_TITLE, DQSTATUSM FROM APPS.HZ_DQM_CS_C_V WHERE DQCUST_ACCOUNT_ID = :p_account_id;

Because results are pre-ordered by match score descending, consumers can apply ROWNUM or FETCH FIRST limits to return only the strongest matches. Typical applications include the Customer Merge workbench, contact deduplication reports, and custom extracts feeding data-quality dashboards. As the view depends on session-scoped package state and a global temporary table, queries must execute within the same session and context in which the DQM search was initiated.