Search Results arh_dqm_pkg




Overview
Explore in AI Chat

Overview

ARH_DQM_PKG is a PL/SQL package body owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The "ARH" prefix places it in the Oracle Receivables and Trading Community (HZ) family of database objects, while the "DQM" component refers to Data Quality Management. The package supports the Data Quality Management infrastructure used by Oracle Customers Online, Oracle Trading Community Architecture (TCA), and related party/contact deduplication features.

Its principal business function is to orchestrate the execution of Data Quality Management matching and cleansing rules against party, contact, and contact point records stored in the TCA registry. Client extensions and Oracle-supplied DQM adapters register their matching logic, and ARH_DQM_PKG acts as the runtime entry point that invokes those adapters, logs execution results, and returns the matched entity identifiers to the calling application. The package is classified as OTHER in the ETRM API registry, indicating it is an internal implementation utility rather than a published public API. Status is VALID in the documented environment, and the metadata records that no other database object references it directly, confirming its role as a leaf-level execution engine consumed at runtime rather than a dependency of other compiled code.

Key Procedures and Functions

The documented package exposes the following procedures and functions:

  • ADDLIST — A utility routine that appends an element to an in-memory list structure, used internally to accumulate identifiers, match results, or error entries during DQM processing.
  • ISNULL — A helper function that evaluates whether a supplied value is null, providing a consistent null test across the numerous optional DQM parameters.
  • EXEC_DQM_API — The primary execution entry point. Invokes the Data Quality Management processing for a given entity or request, driving the configured matching or cleansing rules and returning control to the caller once execution completes.
  • EXEC_DQM_DUP_API — A variant entry point dedicated to duplicate detection. It executes the DQM rules specifically configured for identifying duplicate parties, contacts, or contact points.
  • GET_DQM_EXEC_DETAILS — A retrieval function that returns the details of a prior DQM execution, allowing callers to inspect status, timestamps, and execution metadata.

The metadata records eight documented subprograms in total; the five above are those named in the ETRM excerpt. Parameter lists are not documented and are deliberately omitted here.

Tables Accessed

The package reads and writes a set of TCA (HZ) tables and global temporary tables. The global temporary tables HZ_MATCHED_PARTIES_GT, HZ_MATCHED_CONTACTS_GT, and HZ_MATCHED_CPTS_GT hold match results for parties, contacts, and contact points respectively during a DQM run. HZ_PARTY_SITES, HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS provide the source data against which matching and deduplication logic is applied. PLITBLM is a standard Oracle PL/SQL table-of-varchar2 type used for passing collections in and out of the DQM APIs. The package also depends on the helper packages ARH_DQM_CUST_HELPER, ARH_DQM_TREE_HELPER, HZ_PARTY_SEARCH, and on FND_API and FND_MSG_PUB for the standard EBS API error-handling and message-stack conventions.

Usage Notes

ARH_DQM_PKG is intended for internal invocation. It is typically called from Oracle Customers Online pages, TCA party and contact maintenance forms, and from concurrent programs that perform bulk duplicate identification across the party registry. Because it is a dependent, non-referenced package, customers should not call its procedures directly from custom code; supported integration points are the public TCA and DQM APIs that wrap this package. When extending DQM behavior, developers register adapters through the supported DQM framework, which ARH_DQM_PKG then invokes at runtime via EXEC_DQM_API or EXEC_DQM_DUP_API. Reliance on the undocumented ADDLIST and ISNULL helpers is not recommended, as their signatures may change between patch levels.