Search Results find_duplicate_contact_points

Overview

HZ_PARTY_SEARCH is the core runtime engine of Oracle's Data Quality Management (DQM) party matching framework within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Unlike most PL/SQL packages in the EBS schema, its source is not hand-authored: the package body header records that it is "Compiled by the HZ Match Rule Compiler," with a generation history entry dated 28-NOV-2012. The body is generated from match rules configured in the Trading Community Architecture (TCA) match rule setup, meaning the compiled code reflects the active rule configuration of the environment in which it was generated.

The package exists to support duplicate prevention and identification across the TCA registry. It exposes scoring, searching, and matching logic for parties (organizations and persons), party sites, contacts, and contact points. The HZ Match Rule Compiler translates declarative match rules into PL/SQL procedures, making this package the executable representation of those rules.

Key Procedures and Functions

The documented API surface comprises 21 procedures and functions. The principal entry points include:

• FIND_PARTIES — the primary search routine. It accepts a party search record, party site list, contact list, and contact point list, along with a rule identifier, a restrict SQL fragment, and a merged-search flag, returning a search context identifier, match count, and standard FND_API return status and message outputs.
• FIND_PERSONS — the person-specific counterpart to FIND_PARTIES.
• FIND_PARTY_DETAILS — the routine most directly associated with the user's search term; it returns detail-level match information for identified parties.
• FIND_DUPLICATE_PARTIES, FIND_DUPLICATE_PARTY_SITES, FIND_DUPLICATE_CONTACTS, and FIND_DUPLICATE_CONTACT_POINTS — duplicate-detection variants scoped to each entity type.
• GET_MATCHING_PARTY_SITES, GET_MATCHING_CONTACTS, and GET_MATCHING_CONTACT_POINTS — retrieval routines returning the child entities that match a given search context.
• GET_PARTY_SCORE_DETAILS and GET_SCORE_DETAILS — expose the per-attribute scoring breakdown produced by the match rules, enabling users to understand why a match scored as it did.
• GET_PARTY_FOR_SEARCH and GET_SEARCH_CRITERIA — supporting routines that assemble search inputs and rule criteria.
• FIND_PARTIES_DYNAMIC, CALL_API_DYNAMIC, and CALL_API_DYNAMIC_NAMES — dynamic invocation helpers used by the generated scoring logic to call APIs and resolve attribute names at runtime.

The body also declares private package state: g_debug_count, g_last_rule, and g_last_rule_valid, used to track rule evaluation across calls.

Tables Accessed

Per the documented metadata, the package references the APPS synonym for HZ_TRANS_ATTRIBUTES_B, the base table storing translated or flexible attribute definitions used in matching. The generated scoring logic relies on this table to resolve attribute metadata during search and score evaluation. Broader TCA access to party, party site, contact, and contact point tables is expected given the package's role, though the ETRM metadata lists only this table explicitly.

Usage Notes

HZ_PARTY_SEARCH is not typically called directly by end users. It is invoked by TCA-based forms and framework code — for example, the party entry and duplicate-prevention flows in Oracle Customers, Oracle Receivables, and other TCA-consuming applications — as well as by concurrent programs performing bulk duplicate identification. The metadata indicates the package is referenced by 48 other packages, confirming its role as a shared runtime dependency. Because the body is generated by the HZ Match Rule Compiler, any change to match rules requires recompilation; custom code should call the public procedures rather than embedding assumptions about the generated internals.