Search Results map_contact_rec

Overview

HZ_MATCH_RULE_51 is a PL/SQL package in the Oracle E-Business Suite (EBS) Trading Community Architecture (TCA) / Customer Data Management (CDM) module. It is one of a family of generated "match rule" packages (HZ_MATCH_RULE_<n>) that perform party, party site, contact, and contact point matching as part of the Oracle Data Quality Management (DQM) duplicate identification and merge process. Each package encapsulates a specific matching rule configuration, enabling the DQM engine to score and compare candidate records against a set of search criteria and determine whether records are potential duplicates.

Declared with AUTHID CURRENT_USER, the package executes with the privileges of the invoking user rather than its owner. It exposes both "map" procedures, which transform entered search criteria into staged scoring records, and "get"/"find" procedures, which retrieve and evaluate candidate records. The package operates on the TCA entity hierarchy — parties, party sites, org contacts, and contact points — and is referenced by one other package within the application, reflecting its role as a pluggable matching rule implementation invoked by higher-level DQM orchestration code.

Key Procedures and Functions

The package exposes 29 documented procedures and functions. The principal ones include:

• MAP_PARTY_REC, MAP_PARTY_SITE_REC, MAP_CONTACT_REC, and MAP_CONTACT_POINT_REC — map a search context and search list (or individual search record) into staged scoring structures, returning the maximum entered score. MAP_CONTACT_REC is the specific entry point surfaced by the "map_contact_rec" search, handling the HZ_PARTY_SEARCH.contact_list input and HZ_PARTY_STAGE.contact_stage_list output.
• GET_PARTY_REC, GET_PARTY_SITE_REC, GET_CONTACT_REC, and GET_CONTACT_POINT_REC — retrieve fully populated search records for a given party, party site, contact, or contact point identifier set.
• CHECK_PRIM_COND, CHECK_PARTY_SITE_COND, CHECK_CONTACT_COND, and CHECK_CONTACT_POINT_COND — evaluate primary and secondary matching conditions against the supplied lists, returning Boolean results used to gate candidate acceptance.
• FIND_PARTIES, FIND_PERSONS, FIND_PARTY_DETAILS, FIND_DUPLICATE_PARTIES, FIND_DUPLICATE_PARTY_SITES, FIND_DUPLICATE_CONTACTS, and FIND_DUPLICATE_CONTACT_POINTS — execute the actual duplicate searches and return matching candidates.
• GET_MATCHING_PARTY_SITES — return party sites that match a given search criterion.

Tables Accessed

The package reads and writes TCA and DQM tables via APPS synonyms. Source entities include HZ_PARTIES, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_LOCATIONS, and HZ_ORGANIZATION_PROFILES. Matching and scoring logic references HZ_MATCH_RULES_B (rule definitions), and staged/result sets are held in global temporary tables such as HZ_DQM_PARTIES_GT, HZ_MATCHED_PARTIES_GT, HZ_MATCHED_PARTY_SITES_GT, HZ_MATCHED_CONTACTS_GT, HZ_MATCHED_CPTS_GT, and HZ_PARTY_SCORE_DTLS_GT. Duplicate set persistence uses HZ_DUP_SETS, HZ_DUP_SET_PARTIES, and HZ_MERGE_BATCH_S.

Usage Notes

HZ_MATCH_RULE_51 is not typically called directly by end users. It is invoked by the DQM matching engine and by higher-level packages (it is referenced by one other package), which pass search context and staged records through the map/find/check procedures. It is exercised during duplicate identification, party search, and merge batch processing initiated from TCA administration forms and concurrent programs. Custom code should treat it as an internal, generated implementation whose behavior is driven by the underlying match rule configuration in HZ_MATCH_RULES_B, and should avoid direct dependency where a supported API exists.