Search Results dqrole_type

Overview

APPS.HZ_DQM_ORG_CONTACT_INFO_V is a supplementary database view in the Oracle E-Business Suite Applications (APPS) schema, registered under FND Design Data as AR.HZ_DQM_ORG_CONTACT_INFO_V. Oracle classifies it explicitly as a supplementary view used to simplify forms coding, meaning it exists primarily to support the Oracle Forms-based user interface of the Data Quality Management (DQM) functionality within the Trading Community Architecture (TCA). The "DQM" naming prefix, combined with the column prefix "DQ", signals that the view is tailored for data quality and duplicate-identification processing rather than general-purpose contact reporting.

The view carries a documented Oracle warning: it is not recommended for direct query or data manipulation, as its definition may change dramatically in subsequent minor or major releases. In Oracle EBS 12.1.1 and 12.2.2 the object is VALID and is not referenced by any other database object, confirming its role as a leaf-level, presentation-oriented view. The user query term "dqpty_id" corresponds to the DQPTY_ID column, a party identifier that is central to correlating contact records with TCA party entities during duplicate resolution.

Underlying Base Objects

The view is defined over a small set of TCA and lookup objects. The documented dependencies are:

• ARPT_SQL_FUNC_UTIL (PACKAGE) — used for SQL-level utility functions within the view's query text.
• AR_LOOKUPS (VIEW) — supplies meaning and lookup-derived values such as contact point purpose, role type, and status text.
• HZ_CONTACT_POINTS (SYNONYM) — the source of contact point details (phone, email, URL, etc.) via DQCONTACT_POINT_ID and DQCONTACT_INFO.
• HZ_CUST_ACCOUNT_ROLES (SYNONYM) — provides role context linking contacts to customer accounts and organizations.
• HZ_ORG_CONTACTS (SYNONYM) — the primary source of organization contact records and job title information.
• HZ_PARTIES (SYNONYM) — supplies party-level attributes and party identifiers.
• HZ_RELATIONSHIPS (SYNONYM) — defines the relationship structures that tie contacts, parties, and organizations together.

Because the view joins these objects, it effectively pre-assembles the organization-contact-contact-point data set that the DQM forms require without requiring the form to issue multiple joins.

Key Columns

• DQORG_CONTACT_ID (NUMBER 15) — the organization contact identifier, the principal key for a contact record.
• DQPTY_ID (NUMBER 15) — the party identifier searched by users; correlates the contact to a TCA party.
• DQPARTY_ID (NUMBER 15) — a second party identifier column, reflecting the distinct party references present in the underlying joins.
• DQTITLE (VARCHAR2 30) and DQJOB_TITLE (VARCHAR2 100) — contact title and job title.
• DQTITLE_NAME (VARCHAR2 360) — a concatenated or formatted title/name representation.
• DQROLE_TYPE, DQCONTACT_POINT_PURPOSE, DQMEANING, DQCONTACT_POINT_TYPE, DQSTATUS — lookup-coded attributes resolved through AR_LOOKUPS.
• DQSTATUSM (VARCHAR2 4000) — a status-related descriptive field.
• DQPRIMARY_FLAG, DQPRIMARY_BY_PURPOSE — flags indicating primary contact status, globally or per purpose.
• DQCONTACT_POINT_ID (NUMBER 15) and DQCONTACT_INFO (VARCHAR2 2000) — the contact point identifier and its rendered value.

Common Use Cases and Queries

The view is most relevant to DQM duplicate identification, contact quality assessment, and troubleshooting organization contact records. A representative query filtering by the searched column is:

SELECT dqorg_contact_id, dqpty_id, dqparty_id, dqtitle, dqjob_title, dqcontact_info
FROM apps.hz_dqm_org_contact_info_v
WHERE dqpty_id = :party_id;

Other practical scenarios include auditing contacts with multiple primary flags, reviewing contact points by purpose, and validating lookup decoding. As Oracle advises against direct queries, production use should be limited to diagnostics and analysis, with canonical data retrieved from the underlying HZ tables.