Search Results arh_dqm_tree_helper




Overview
Explore in AI Chat

Overview

ARH_DQM_TREE_HELPER is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an OTHER API within the ETRM documentation set for releases 12.1.1 and 12.2.2. Its status is VALID in the documented environment. The package supports the Oracle Receivables and Oracle Trading Community Architecture Data Quality Management (DQM) feature set, specifically the duplicate prevention and party/contact matching logic that evaluates candidate records against existing master data before they are committed. It functions as a helper layer beneath ARH_DQM_PKG, providing the lower-level tree traversal and relationship interpretation routines that DQM needs in order to resolve hierarchies of parties, party sites, contacts, and contact points during matching.

The package is a dependency of ARH_DQM_PKG, which is referenced by eleven other packages and by a set of HZ_DQM database views, including HZ_DQM_AC_AS_V, HZ_DQM_AC_C_V, HZ_DQM_CS_CPT_V, HZ_DQM_CS_C_V, HZ_DQM_PARTY_CPT_V, HZ_DQM_PS_CPT_V, HZ_DQM_PS_C_V, HZ_DQM_P_AC_V, HZ_DQM_P_PS_V, and HZ_DQM_RE_P_V. This dependency pattern confirms that the package occupies a foundational position in the DQM stack rather than being a top-level entry point.

Key Procedures and Functions

ETRM documents seventeen procedures and functions, with the following named and summarized by purpose:

  • CTXMAX — Returns a maximum context value used to bound the DQM matching and tree evaluation scope.
  • CPT_IN_MATCH — Determines whether a contact point participates in a current match evaluation.
  • CONTACT_IN_MATCH — Determines whether a contact is part of the match set under consideration.
  • PARTY_SITE_IN_MATCH — Tests whether a party site is included in the active match construction.
  • PARTY_IN_MATCH — Tests whether a party record is included in the active match construction.
  • INSERT_ADD_PARTY_SITE — Inserts an additional party site into the match or candidate result set.
  • INSERT_ADD_CONTACT — Inserts an additional contact into the match or candidate result set.
  • INSERT_ADD_CPT — Inserts an additional contact point into the match or candidate result set.
  • CONTACT_ID_FROM_REL_ID — Resolves a contact identifier from a given relationship identifier.
  • PARTY_OR_SITE_FROM_CPT — Determines whether a contact point belongs to a party or to a party site and returns the corresponding identifier.
  • REL_ID_BETW_PER_TO_ORG — Retrieves the relationship identifier between a person and an organization.
  • IS_PTY_OBJECT_OF_REL — Tests whether a party is the object of a given relationship.
  • IS_SITE_OF_PTY — Tests whether a site belongs to a given party.
  • RELATIONSHIP_TREATMENT — Applies the DQM treatment rule for a relationship, determining how the related records should be considered during matching.
  • TREATMENT_PARTY_SITE — Applies the DQM treatment rule for a party site.
  • CPT_TREATMENT — Applies the DQM treatment rule for a contact point.
  • CONTACT_TREATMENT — Applies the DQM treatment rule for a contact.

Tables Accessed

The package operates against the TCA (Trading Community Architecture) model through APPS synonyms. It reads master party data from HZ_PARTIES and location data from HZ_PARTY_SITES, associates contacts through HZ_ORG_CONTACTS, and resolves contact points via HZ_CONTACT_POINTS. Relationship semantics, which drive the IS_PTY_OBJECT_OF_REL, IS_SITE_OF_PTY, and REL_ID_BETW_PER_TO_ORG routines, come from HZ_RELATIONSHIPS. Candidate and matched output sets are staged in the global temporary tables HZ_MATCHED_PARTIES_GT, HZ_MATCHED_PARTY_SITES_GT, HZ_MATCHED_CONTACTS_GT, and HZ_MATCHED_CPTS_GT. The INSERT_ADD_* routines write into these temporary structures, while the matching and treatment routines read from the base TCA tables to evaluate duplicates.

Usage Notes

ARH_DQM_TREE_HELPER is not intended for direct invocation by end users. It is called internally by ARH_DQM_PKG during duplicate identification and party/contact deduplication workflows, and it is also referenced by the HZ_DQM_* views that expose DQM candidate data. In practice it is exercised when users create or update parties, party sites, contacts, or contact points through EBS forms such as the Customer or Party maintenance forms, or when DQM-related concurrent programs and batch duplicate identification jobs execute. Customizations should avoid calling this package directly; a safer integration point is ARH_DQM_PKG or the HZ_DQM views. Because the package is a helper with no documented open API contract, its signature and behavior should be treated as internal and subject to change across EBS patch levels.