Search Results dqcontact_number




Overview
Explore in AI Chat

Overview

APPS.HZ_DQM_PS_C_V is a supplementary database view owned by the APPS schema within Oracle E-Business Suite, registered under FND Design Data as AR.HZ_DQM_PS_C_V. It is classified in the ETRM documentation as a "supplementary view used to simplify forms coding," meaning it exists primarily to present a denormalized, forms-friendly result set to the Oracle Forms-based Data Quality Management (DQM) user interface rather than to serve as a general-purpose reporting object. Oracle explicitly warns that querying or altering data through this view is not recommended, because its definition may change dramatically between minor or major releases. The view carries a VALID status in both 12.1.1 and 12.2.2 environments, and the metadata confirms it is not referenced by any other database object, so it sits at the top of its own dependency chain rather than acting as a building block for downstream objects.

Underlying Base Objects

The documented dependency list identifies the objects that HZ_DQM_PS_C_V is built upon. The primary data sources are the TCA (Trading Community Architecture) tables exposed through synonyms: HZ_ORG_CONTACTS, HZ_PARTIES, and HZ_RELATIONSHIPS, which supply organization contact, party, and relationship records respectively. The synonym HZ_MATCHED_CONTACTS_GT is a global temporary table used in the DQM matching process to hold transient matched-contact results, and AR_LOOKUPS is the Receivables lookup view used for decoding coded values. Two PL/SQL packages are also referenced: ARH_DQM_TREE_HELPER, which provides hierarchy and tree-handling logic for the DQM matching tree, and ARPT_SQL_FUNC_UTIL, a general SQL function utility package used for dynamic or shared SQL fragments. The presence of the matched-contacts global temporary table and the tree helper package indicates that the view is specifically shaped to feed the DQM party/contact matching form flow, joining persistent TCA data with in-session match results.

Key Columns

  • DQORG_CONTACT_ID (NUMBER) — Organization contact identifier, the primary key from HZ_ORG_CONTACTS.
  • DQPARTY_SITE_ID (NUMBER) — Party site identifier for the contact's location.
  • DQTITLE and DQJOB_TITLE (VARCHAR2) — Contact title and job title attributes.
  • DQSTATUS and DQSTATUSM (VARCHAR2) — Status code and its decoded/meaning form, the latter typically resolved through AR_LOOKUPS.
  • DQCONTACT_NUMBER (VARCHAR2) — Contact number reference.
  • DQRELATIONSHIP_CODE (VARCHAR2(30)) — The relationship code describing how the contact relates to the party; this is the column surfaced when searching for "dqrelationship_code".
  • DQRELATIONSHIP_ID (NUMBER) — Identifier of the underlying relationship record in HZ_RELATIONSHIPS.
  • DQPARTY_NAME (VARCHAR2(360)) — Party name for display.
  • DQPARTY_ID (NUMBER) — Party identifier from HZ_PARTIES.

Common Use Cases and Queries

The principal legitimate use of this view is diagnostic: inspecting which parties, contacts, and relationship codes the DQM matching form is presenting. Because it is not a supported reporting interface, queries should be treated as read-only investigation and not embedded in production integrations. A representative query filtering on the relationship code mirrors the documented select list:

  • SELECT DQORG_CONTACT_ID, DQPARTY_SITE_ID, DQCONTACT_NUMBER, DQRELATIONSHIP_CODE, DQRELATIONSHIP_ID, DQPARTY_NAME, DQPARTY_ID FROM APPS.HZ_DQM_PS_C_V WHERE DQRELATIONSHIP_CODE = :p_relationship_code;
  • Joining the returned DQRELATIONSHIP_ID back to HZ_RELATIONSHIPS to obtain the full relationship record, or DQPARTY_ID back to HZ_PARTIES for complete party attributes.
  • Comparing DQSTATUS against DQSTATUSM to verify lookup decoding behavior during DQM troubleshooting.

Given the documented warning, any requirement for stable reporting should be redirected to the underlying TCA tables rather than this forms-support view.