Results for “dqcust_account_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HZ_DQM_P_AC_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, documented against the Receivables (AR) product family and validated in releases 12.1.1 and 12.2.2. The name follows Oracle's Data Quality Management (DQM) naming convention: the "HZ_" prefix identifies it as a Trading Community Architecture (TCA) registry object, "DQM" identifies it as part of the Data Quality Management matching and de-duplication infrastructure, and the "P_AC" infix indicates that it projects party and customer account data. The view supplies the account-side result set for the DQM party/account search and match process, presenting one row for each customer account that satisfies the current match criteria.

Functionally, HZ_DQM_P_AC_V acts as a presentation layer over the intersection of customer accounts and party records, resolving coded values into their display meanings and ordering the output by match score. Its primary consumers are the DQM deduplication UI, the tree/merge helper logic, and any custom inquiry that needs a pre-joined, meaning-resolved view of accounts participating in a data quality search.

Underlying Base Objects

The view is defined over the following documented objects:

• HZ_CUST_ACCOUNTS (synonym) — the driving table, supplying account identifiers, account number, name, activation date, customer type, and status.
• HZ_PARTIES (synonym) — joined on PARTY_ID to supply party identifier, party type, and category code.
• AR_LOOKUPS (view) — joined three times as L, L1, and L2 (all outer joins) to translate CUSTOMER_TYPE, PARTY_TYPE, and CUSTOMER_CATEGORY_CODE into lookup meanings.
• HZ_MATCHED_PARTIES_GT (synonym) — a global temporary table holding the matched party set for the active search context, joined outer on the account identifier and filtered by the current search context.
• ARH_DQM_TREE_HELPER (package) — provides CTXMAX, the current maximum search context identifier used to restrict the match results.
• ARPT_SQL_FUNC_UTIL (package) — supplies GET_LOOKUP_MEANING, invoked to translate the REGISTRY_STATUS lookup.

The join chain anchors on HZ_CUST_ACCOUNTS, links to HZ_PARTIES on PARTY_ID, and optionally joins HZ_MATCHED_PARTIES_GT so unmatched accounts are retained with a null score. Records with a status of 'M' (merged) are explicitly excluded. The result set is ordered by the decoded match score in descending order.

Key Columns

• DQPARTY_ID — party identifier from HZ_PARTIES, the TCA primary key for the party.
• DQPARTY_TYPE — decoded meaning of the party type (for example, Person or Organization).
• DQCATEGORY_CODE — decoded customer category meaning.
• DQCUST_ACCOUNT_ID — customer account identifier from HZ_CUST_ACCOUNTS.
• DQACCOUNT_NUMBER — the account number presented to users.
• DQCUSTOMER_TYPE — decoded customer type meaning.
• DQNAME — the account name.
• DQACCOUNT_ACTIVATION_DATE — date the account became active.
• DQSTATUS — raw status code from the account record.
• DQSTATUSM — the status translated via the REGISTRY_STATUS lookup, falling back to the raw code when no meaning exists.

Common Use Cases and Queries

The view is typically queried to inspect the accounts currently returned by a DQM match, to resolve display meanings for a data quality review, or to reconcile accounts against the matched-party temporary table. A representative query retrieves all accounts for a party:

SELECT dqname, dqaccount_number, dqcustomer_type, dqparty_type, dqstatusm FROM hz_dqm_p_ac_v;

A filtered variant isolates accounts by status or type:

SELECT dqaccount_number, dqname FROM hz_dqm_p_ac_v WHERE dqstatusm = 'Active' AND dqcustomer_type = 'Organization';

Because the view depends on the global temporary table and the ARH_DQM_TREE_HELPER context, results reflect only the session's current search context; it should not be treated as a general-purpose account listing. For broader reporting, HZ_CUST_ACCOUNTS and HZ_PARTIES should be queried directly.