Search Results hz_dqm_ps_c_v




Overview
Explore in AI Chat

Overview

HZ_DQM_PS_C_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and registered under the Receivables (AR) product. Its name follows the Data Quality Management (DQM) naming convention used by Oracle's party and contact matching engine, where "PS" denotes the party site context and "C" denotes contact-oriented output. The view presents a denormalized, display-ready record set of organization contacts, enriched with relationship, party, and lookup-meaning attributes, and ranked by a match score produced during the DQM duplicate-detection process.

Functionally, the view sits in front of Oracle's customer and contact deduplication workflow. It joins the transactional contact records against the global temporary matched-contacts table populated by the DQM tree helper, so that only candidate matches belonging to the current search context are exposed. This makes it a presentation-layer object used by Receivables and Trading Community Architecture (TCA) screens and concurrent programs to display probable duplicate contacts to end users for review and resolution, rather than a base storage table. It is fully valid and shipped as part of the standard 12.1.1 and 12.2.2 file systems.

Underlying Base Objects

The documented definition of HZ_DQM_PS_C_V references the following objects:

  • HZ_ORG_CONTACTS — the driving table (aliased A), providing the contact identity, contact number, party site, title and job title codes, and status.
  • HZ_RELATIONSHIPS — the relationship table (aliased B), supplying the relationship ID and relationship code linking the contact to a party.
  • HZ_PARTIES — the party master (aliased P), supplying the party name and party ID.
  • AR_LOOKUPS — referenced twice (H and H1) to resolve the job title and contact title codes into their display meanings.
  • HZ_MATCHED_CONTACTS_GT — a global temporary synonym holding the DQM match candidates, joined by org contact ID and the current search context.
  • ARH_DQM_TREE_HELPER — package supplying CTXMAX, the active search context identifier used to scope the match results.
  • ARPT_SQL_FUNC_UTIL — package whose GET_LOOKUP_MEANING function translates the registry status code into a readable status meaning.

The view applies an outer join to the matched-contacts global temporary table and orders results by match score in descending order, so records without a score are pushed to the end.

Key Columns

  • DQORG_CONTACT_ID — primary identifier of the organization contact record.
  • DQPARTY_SITE_ID — the party site associated with the contact; records with a null party site are excluded from the view.
  • DQTITLE — the decoded contact title meaning from AR_LOOKUPS.
  • DQJOB_TITLE — the decoded responsibility/job title meaning from AR_LOOKUPS.
  • DQSTATUS — the raw contact status code; contacts with a status of "M" are filtered out.
  • DQSTATUSM — the human-readable registry status meaning, defaulting to the raw status when no lookup is found.
  • DQCONTACT_NUMBER — the system-assigned contact number.
  • DQRELATIONSHIP_CODE / DQRELATIONSHIP_ID — the relationship linking contact to party, restricted to the forward directional relationship.
  • DQPARTY_NAME / DQPARTY_ID — the name and identifier of the related party.

Common Use Cases and Queries

Typical uses include reviewing probable duplicate contacts before merge, driving contact deduplication review screens, and building custom reports on match candidates. A representative query is:

  • SELECT dqorg_contact_id, dqparty_name, dqcontact_number, dqtitle, dqstatusm FROM hz_dqm_ps_c_v WHERE dqparty_id = :p_party_id;
  • SELECT dqcontact_number, dqparty_name, dqrelationship_code FROM hz_dqm_ps_c_v ORDER BY dqparty_name;

Because the view depends on ARH_DQM_TREE_HELPER.CTXMAX and the HZ_MATCHED_CONTACTS_GT temporary table, meaningful results require an active DQM search context. Queries executed outside a running match process return unscored rows only.