Search Results dqpostal_code




Overview
Explore in AI Chat

Overview

HZ_DQM_P_PS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the Receivables (AR) product family. Its name follows the Data Quality Management (DQM) naming convention used by Oracle's party and party site de-duplication and matching infrastructure: the "P_PS" segment denotes "Party / Party Site," which reflects the object's purpose of exposing party site address records specifically shaped for DQM processing. The view consolidates address, location, and territory information from the TCA (Trading Community Architecture) model into a flat, denormalized result set whose columns are prefixed with DQ to signal their role as input to matching and merge routines.

Because it is a view rather than a table, HZ_DQM_P_PS_V stores no data of its own. It projects the joining logic required by the DQM match engine, including ordering by a match score when the caller supplies a search context. This makes it the delivery vehicle for candidate party site records presented during interactive de-duplication, bulk matching, and merge confirmation flows within Receivables and shared TCA components.

Underlying Base Objects

The view is defined over a fixed set of documented base objects:

  • HZ_PARTY_SITES (synonym) — the primary TCA table of party site records, supplying PARTY_SITE_ID, PARTY_ID, identifying address flag, and status.
  • HZ_LOCATIONS (synonym) — the address repository joined on LOCATION_ID, providing address lines, city, state, province, county, and postal code.
  • FND_TERRITORIES_VL (view) — the territory/ country lookup, joined on the location's country code, with an outer join in the definition.
  • HZ_MATCHED_PARTY_SITES_GT (synonym) — a global temporary table populated by the matching process, outer-joined on PARTY_ID and PARTY_SITE_ID, filtered against the current search context.
  • ARH_DQM_TREE_HELPER (package) — supplies CTXMAX, the active search context identifier used to constrain the matched set.
  • ARPT_SQL_FUNC_UTIL (package) — supplies GET_LOOKUP_MEANING, used to translate the registry status code into a display meaning.

The view also filters out records whose status equals 'M' (merged), and sorts results by the match score in descending order, treating a null score as -1 so unmatched rows sort last.

Key Columns

  • DQPARTY_ID — the party identifier (PS.PARTY_ID). This is the column users commonly search for under the term "dqparty_id"; it links the view to the owning party record in HZ_PARTIES.
  • DQPARTY_SITE_ID — the underlying party site identifier, the primary key of the candidate record.
  • DQADDRESS — concatenation of ADDRESS1 and ADDRESS2 (hyphen-separated), the formatted street address.
  • DQCOUNTRY — territory short name from FND_TERRITORIES_VL.
  • DQCITY, DQSTATE, DQPROVINCE, DQPOSTAL_CODE, DQCOUNTY — the remaining location components used for match scoring and display.
  • DQIDEN_FLAG — the identifying address indicator.
  • DQSTATUS — the raw status code; DQSTATUSM — the decoded lookup meaning from the REGISTRY_STATUS lookup type, falling back to the raw code.

Common Use Cases and Queries

The most frequent usage is retrieving candidate party site rows for a given party during matching or review. A typical query is:

SELECT dqparty_id, dqparty_site_id, dqaddress, dqcity, dqstate, dqstatusm FROM hz_dqm_p_ps_v WHERE dqparty_id = :p_party_id ORDER BY dqparty_site_id;

Analysts also use the view to audit identifying addresses or to reconcile site statuses for a party before a merge. Because the matched temporary table is only populated within an active DQM search context, rows returned without that context represent the full, unfiltered party site population. Queries should therefore be restricted by DQPARTY_ID to keep result sets predictable, and the view should never be used for DML.