Search Results party_reln_object_merge

Overview

HZ_MERGE_PKG is a core Oracle E-Business Suite PL/SQL package owned by the APPS schema that implements the registry-level merge logic for the Oracle Trading Community Architecture (TCA). Its principal business function is to consolidate two party records — typically a duplicate party and a surviving (master) party — into a single unified entity, transferring or repointing all dependent data such as relationships, profiles, customer accounts, contact points, and supplementary profile attributes. Because party merge touches virtually every table that carries a PARTY_ID foreign key, the package acts as the orchestration layer that individual TCA entity packages call during a merge operation initiated from the Oracle Customer Data Management (CDM) or Data Quality Management (DQM) merge user interface.

The package is classified as an internal "OTHER" API rather than a public Oracle API. It is validated in both EBS 12.1.1 and 12.2.2, and depends on FND_API for the standard API return-status conventions (X_RETURN_STATUS, X_MSG_COUNT, X_MSG_DATA).

Key Procedures and Functions

The ETRM metadata documents 41 procedures and functions. The principal entry points include:

• PARTY_MERGE — the master driver that merges the core HZ_PARTIES row from the duplicate into the surviving party, updating the party record and associated identifiers.
• PARTY_RELATIONSHIP_MERGE, PARTY_RELN_OBJECT_MERGE, PARTY_RELN_SUBJECT_MERGE — handle relationships where the merged party appears as either the subject or object of a relationship, repointing or deduplicating HZ_RELATIONSHIPS and related intersection rows.
• ORG_PROFILE_MERGE, PER_PROFILE_MERGE — merge organization and person profile attributes held in the party profile tables.
• ORG_CONTACT_MERGE, ORG_CONTACT_MERGE2 — consolidate contact associations for organizations.
• CUST_ACCOUNT_MERGE, CUST_ACCOUNT_ROLE_MERGE, CUST_ACCOUNT_SITE_MERGE — migrate customer accounts, account roles, and account sites between the surviving and duplicate party.
• CONTACT_POINT_MERGE, CONTACT_POINT_MERGE2, PARTY_SITE_MERGE, PARTY_SITE_USE_MERGE — repoint contact points, party sites, and site uses, resolving duplicates where possible.
• CONTACT_PREFERENCE_MERGE — merge contact preferences.
• FINANCIAL_PROFILE_MERGE, CREDIT_RATINGS_MERGE, CERTIFICATION_MERGE, REFERENCES_MERGE — consolidate supplementary profile attributes such as financial profiles, credit ratings, certifications, and references.

Additional documented procedures include PARTY_MERGE and the merge routines for citizenship, education, employment history, and code assignments, each applying the same deduplicate-or-repoint pattern.

Tables Accessed

The package reads and writes the principal TCA tables, including HZ_CERTIFICATIONS, HZ_CITIZENSHIP, HZ_CLASS_CATEGORIES, HZ_CODE_ASSIGNMENTS, HZ_CONTACT_POINTS, HZ_CONTACT_PREFERENCES, HZ_CREDIT_RATINGS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_EDUCATION, and HZ_EMPLOYMENT_HISTORY. It also references HZ_DNB_REQUEST_LOG, HZ_DNB_REQUEST_LOG_S, and HZ_DQM_SYNC_INTERFACE, which support the DQM synchronization workflow that drives merge processing. Each table is accessed through APPS synonyms and updated to repoint the duplicate party's foreign keys to the surviving party, or to delete redundant rows where the surviving party already holds equivalent data.

Usage Notes

HZ_MERGE_PKG is invoked indirectly rather than directly by end users. In standard EBS, merge requests are submitted through the Oracle Customer Data Management / DQM concurrent programs and forms, which call HZ_MERGE_PKG and its sibling package HZ_PROFILE_MERGE_PKG to execute the merge. Customizations that need to trigger a party merge programmatically should call the DQM merge APIs rather than HZ_MERGE_PKG directly, since the package assumes a controlled transaction context and merge-bookkeeping state. Because the package is an internal API, Oracle does not guarantee signature stability across patches, so custom code should avoid direct references where possible.