Search Results check_party_site_cond

Overview

HZ_MATCH_RULE_51 is a PL/SQL package in the APPS schema that participates in the Oracle E-Business Suite Trading Community Architecture (TCA) matching engine. Its central role is to transform Oracle Receivables party search results into the staged record structures consumed by the duplicate identification and match scoring process. The package is declared AUTHID CURRENT_USER, so its unqualified references to HZ objects resolve through the calling user's schema, while the HZ table synonyms themselves remain owned by APPS.

In the context of the user search term map_party_rec, the package provides the mapping layer between a transient search request and the persistent real-time match structures. The map_party_rec procedure converts an HZ_PARTY_SEARCH.party_search_rec_type search input into a corresponding HZ_PARTY_STAGE.party_stage_rec_type record, returning the highest score entered by the user. This mapping is a prerequisite for duplicate party identification, party merge, and the Data Quality Management (DQM) workflows that depend on consistent staging of candidate records. The package is referenced by one other package, indicating it is invoked from within the matching framework rather than as a top-level entry point.

Key Procedures and Functions

The documented interface exposes 29 procedures and functions, organized into mapping, retrieval, condition-checking, and search operations.

• MAP_PARTY_REC, MAP_PARTY_SITE_REC, MAP_CONTACT_REC, MAP_CONTACT_POINT_REC — map search request records, site lists, contact lists, and contact point lists into the corresponding staging structures, each returning the entered maximum score.
• GET_PARTY_REC, GET_PARTY_SITE_REC, GET_CONTACT_REC, GET_CONTACT_POINT_REC — retrieve the search representation for a given party ID, party site ID list, contact ID list, or contact point ID list.
• CHECK_PRIM_COND, CHECK_PARTY_SITE_COND, CHECK_CONTACT_COND, CHECK_CONTACT_POINT_COND — evaluate primary and secondary match conditions across party, site, contact, and contact point inputs, returning a Boolean result.
• FIND_PARTIES, FIND_PERSONS, FIND_PARTY_DETAILS — execute party, person, and party detail searches against the match rule.
• FIND_DUPLICATE_PARTY_SITES, FIND_DUPLICATE_CONTACTS, FIND_DUPLICATE_CONTACT_POINTS, FIND_DUPLICATE_PARTIES — identify duplicates at each level of the party hierarchy.
• GET_MATCHING_PARTY_SITES — return party sites that satisfy the active match criteria.

Tables Accessed

• HZ_PARTIES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_LOCATIONS, HZ_ORGANIZATION_PROFILES — source entities read to populate search and staging records.
• HZ_MATCH_RULES_B, HZ_DUP_SETS, HZ_DUP_SET_PARTIES — define and store match rule configuration and duplicate set membership.
• HZ_DQM_PARTIES_GT, HZ_MATCHED_PARTIES_GT, HZ_MATCHED_CONTACTS_GT, HZ_MATCHED_CPTS_GT, HZ_MATCHED_PARTY_SITES_GT, HZ_PARTY_SCORE_DTLS_GT — global temporary tables holding scored matched records and score detail during a matching run.
• HZ_MERGE_BATCH_S — the merge batch sequence used when duplicate resolution results in a party merge.

Usage Notes

HZ_MATCH_RULE_51 is invoked from within the TCA matching framework rather than directly by end users. It is typically called by party match and duplicate identification logic triggered from the Oracle Receivables and TCA forms, including supplier and customer duplicate prevention, and from concurrent programs that batch-process party deduplication. Because the procedures operate on NOCOPY IN OUT staging parameters, callers must allocate and pass fully populated staging records; the global temporary tables must also be populated for the current session before the FIND_DUPLICATE and GET_MATCHING procedures return meaningful results. The behavior is common to both Oracle EBS 12.1.1 and 12.2.2, since the TCA matching packages retain the same signature across these releases. Custom code should not call this package in isolation; it should be reached through the documented matching APIs or the concurrent programs that the package was designed to serve. Name collisions with other HZ match rule packages underscore the importance of verifying the exact runtime package version in the target instance.