Search Results dqrelationship_code

Overview

The view APPS.HZ_DQM_RE_P_V is a reporting and integration object within the Oracle E-Business Suite Receivables (AR) module. Its name encodes its purpose: "DQM" refers to Data Quality Management, "RE" denotes relationships, and "P" indicates that party attributes are surfaced alongside the relationship context. The view presents a denormalized, reporting-ready projection of party relationships maintained in the Oracle Trading Community Architecture (TCA) data model, enriched with lookup-decoded meaning values and Data Quality Management matching scores. In EBS 12.1.1 and 12.2.2 the view is delivered in VALID status under the APPS schema and is treated as a query-only object; no DML should be issued against it.

Functionally, HZ_DQM_RE_P_V joins organizational contacts to their party relationships and resolves the coded lookup values for relationship type and party type into human-readable meaning strings. It is primarily consumed by the DQM deduplication and relationship-matching flows supported by ARH_DQM_TREE_HELPER, which supplies the active search context identifier. Because it filters on directional flag 'B' and on active (non-expired) relationships, the view exposes only bidirectional, currently effective relationships, making it suitable for real-time enquiry screens and extract programs rather than for historical auditing.

Underlying Base Objects

• HZ_RELATIONSHIPS — the primary driver, supplying relationship identifier, relationship code, start and end dates, and comments.
• HZ_PARTIES — provides party name and party type for the related party identified by OBJECT_ID.
• HZ_ORG_CONTACTS — supplies the organization contact identifier and links to the relationship record.
• HZ_MATCHED_CONTACTS_GT — an outer-joined global temporary table carrying DQM match scores and the search context identifier.
• AR_LOOKUPS — referenced twice (aliases H and H1) to decode PARTY_RELATIONS_TYPE and PARTY_TYPE into display meanings.
• ARH_DQM_TREE_HELPER — a package whose CTXMAX function supplies the current maximum search context used to constrain the matched-contacts temporary table.

The dependencies confirm that the view straddles both the TCA registry tables and the DQM matching infrastructure, with AR_LOOKUPS providing the presentation layer decoding.

Key Columns

• DQORG_CONTACT_ID — organization contact identifier from HZ_ORG_CONTACTS; the natural key for the contact row.
• DQSUBJECT_ID — subject identifier from HZ_RELATIONSHIPS, identifying the subject side of the relationship.
• DQRELATIONSHIP_CODE — the decoded meaning of the relationship type lookup, resolving the raw RELATIONSHIP_CODE the user searched for ("dqrelationship_code") into a readable value.
• DQSTART_DATE / DQEND_DATE — effective date range of the relationship; records with a past or null end date are retained by the NVL filter.
• DQCOMMENTS — free-text comments captured against the relationship.
• DQPARTY_NAME — the related party's name from HZ_PARTIES.
• DQPARTY_TYPE — decoded party type meaning, distinguishing person, organization, and group classifications.

Common Use Cases and Queries

Typical uses include relationship enquiry screens, DQM review reports, and extracts feeding customer master data quality assessments. A representative query retrieving all active relationships for a party is:

SELECT dqorg_contact_id, dqsubject_id, dqrelationship_code, dqparty_name, dqparty_type, dqstart_date, dqend_date FROM hz_dqm_re_p_v WHERE dqparty_name = :party_name ORDER BY dqrelationship_code;

To isolate a specific relationship category, filter on the decoded meaning, for example WHERE dqrelationship_code = 'Employee Of'. Because the view is ordered by match score descending at definition time, callers relying on that ordering should re-specify ORDER BY explicitly. Joins back to HZ_PARTIES or HZ_ORG_CONTACTS on the exposed identifiers are common when additional TCA attributes are required.