Search Results call_api_dynamic_names

Overview

APPS.HZ_PARTY_SEARCH is the public Data Quality Management (DQM) API package within the Oracle Trading Community Architecture (TCA) schema. Its documented purpose, per the package header, is to contain the Data Quality Management search and duplicate identification APIs. The package is classified under product HZ, carries the display name "DQM Search and Duplicate Identification," and is designated with an active lifecycle. It is associated with the business entities HZ_PARTY, HZ_PERSON, HZ_ORGANIZATION, HZ_ADDRESS, HZ_CONTACT, and HZ_CONTACT_POINT, reflecting that search and duplicate resolution apply across the full range of TCA registry objects. The reference documentation cited in the header is the Data Quality Management Search and Duplicate Identification APIs chapter of the Oracle Trading Community Architecture Technical Implementation Guide (doccd 120hztig.pdf). The header revision metadata (120.12, dated 2006/10/05) indicates the package has been stable across the 11i and R12 code lines, and it remains present in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

ETRM documents 21 procedures and functions for this package. The most significant are listed below; parameter signatures are not reproduced here.

• FIND_PARTIES — the primary entry point for locating parties (persons and organizations) that match a set of search criteria. This is the procedure referenced by the user's search term "find_parties."
• FIND_PERSONS — a person-specific search variant restricted to the HZ_PERSON entity.
• FIND_PARTY_DETAILS — returns detailed attribute information for parties identified by a search.
• GET_PARTY_FOR_SEARCH — populates a party search record for use as search input.
• GET_SEARCH_CRITERIA — retrieves the configured search criteria, typically derived from match rule setup.
• GET_MATCHING_PARTY_SITES — returns party sites that match the search criteria.
• GET_MATCHING_CONTACTS — returns matching contact records.
• GET_MATCHING_CONTACT_POINTS — returns matching contact point (phone, e-mail, URL) records.
• GET_PARTY_SCORE_DETAILS and GET_SCORE_DETAILS — expose the match score and the component-level scoring detail generated by the match engine.
• FIND_DUPLICATE_PARTIES — identifies duplicate party records for a given party.
• FIND_DUPLICATE_PARTY_SITES, FIND_DUPLICATE_CONTACTS, and FIND_DUPLICATE_CONTACT_POINTS — entity-specific duplicate identification for sites, contacts, and contact points respectively.
• FIND_PARTIES_DYNAMIC and CALL_API_DYNAMIC / CALL_API_DYNAMIC_NAMES — dynamic invocation variants that allow the search or API call to be assembled at runtime.

The package also declares a public record type, party_search_rec_type, which exposes account names, account numbers, domain name, party source system reference, and custom attributes one through twenty-seven as search inputs. These CUSTOM elements map to the extensibility attributes of the TCA registry.

Tables Accessed

ETRM documents one referenced table accessed via an APPS synonym: HZ_TRANS_ATTRIBUTES_B. This is the base table storing translated (multi-language) attribute definitions used by the TCA attribute framework, and it is read to resolve the dynamic attribute names and values leveraged by the dynamic search and duplicate identification routines. In practice the package also operates against the HZ_PARTIES, HZ_PERSON_PROFILES, HZ_ORGANIZATION_PROFILES, HZ_PARTY_SITES, HZ_CONTACTS, HZ_CONTACT_POINTS, and HZ_MATCH_SCORE tables through the DQM matching engine, but the published ETRM metadata lists only HZ_TRANS_ATTRIBUTES_B explicitly.

Usage Notes

HZ_PARTY_SEARCH is not a user-facing program; it is invoked programmatically. Typical callers include the Party Search and Duplicate Identification pages in the Oracle Customers, Suppliers, and TCA administration HTML flows, the DQM concurrent programs that run bulk duplicate identification, and customer-written PL/SQL that needs to locate or de-duplicate TCA registry records. ETRM records that the package is referenced by 48 other packages, confirming its role as a foundational dependency of the TCA and Data Quality stack. Custom integrations should call the documented public procedures (FIND_PARTIES, FIND_PERSONS, FIND_DUPLICATE_PARTIES, and their site/contact/contact-point counterparts) rather than reimplementing match logic, since the package encapsulates the scoring rules configured through DQM match rules. Because the package header is stable across 12.1.1 and 12.2.2, code written against it generally requires no modification on upgrade, though the underlying matching engine and match rule setup must exist for results to be returned.