Search Results hz_profile_merge_pkg




Overview
Explore in AI Chat

Overview

The APPS.HZ_PROFILE_MERGE_PKG package body is a TCA (Trading Community Architecture) component responsible for merging customer profile data during party, account, and contact consolidation operations in Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, customer profiles store a wide range of attribute-level information — credit, collections, marketing, and preference data — attached to parties, customer accounts, and customer sites. When two entities are merged via the Trading Community Architecture merge process, the profile information held against the surviving record and the duplicate record must be reconciled rather than simply overwritten or discarded. This package encapsulates that reconciliation logic. Its status is documented as VALID in the APPS schema, and its API classification in ETRM is listed as OTHER, distinguishing it as an internal merge-support utility rather than a standalone public API. It depends on shared TCA infrastructure, specifically FND_API, FND_MESSAGE, FND_MSG_PUB, HZ_MERGE_PKG, and HZ_UTILITY_PUB, confirming that it participates in the broader merge framework and adheres to standard Oracle error-handling conventions.

Key Procedures and Functions

The package body documents a single procedure:

  • PROFILE_MERGE — The core routine that performs the profile-related portion of a merge. It is invoked by the TCA merge framework to move, consolidate, or reconcile customer profile records and their associated profile amounts from a source (duplicate) entity to the target (surviving) entity. It leverages HZ_MERGE_PKG for shared merge utilities and FND_API/FND_MSG_PUB for standardized return status and message stack handling.

Because the ETRM metadata documents only this single procedure, no additional functions or overloads should be assumed. No parameter lists are documented; parameter details must be confirmed against the deployed package specification in the target environment.

Tables Accessed

Per the ETRM dependency listing, the package references the following tables through APPS synonyms:

  • HZ_CUSTOMER_PROFILES — Stores the profile header and attribute records associated with a party or customer. The merge procedure reads source and target profile rows and writes the reconciled result to the surviving entity.
  • HZ_CUST_PROFILE_AMTS — Stores profile amount information (for example, monetary profile attribute values). These rows are migrated or consolidated in step with their parent profile records to maintain referential integrity.

Both tables are central to the TCA profile model; the merge procedure must keep their contents consistent so that downstream profile-driven logic (credit, collections, marketing segmentation) reflects a single, deduplicated entity.

Usage Notes

HZ_PROFILE_MERGE_PKG is not referenced by any other database object according to the ETRM metadata, and it is not a public-facing API. It is invoked internally by the TCA merge orchestrator — typically triggered through the Customer/Party Merge user interface (the Merge Parties and Merge Accounts forms) or the related concurrent programs in Oracle EBS. In practice, it fires automatically as part of a merge transaction and requires no direct call from custom code. Because it depends on FND_MSG_PUB, any errors surface through the standard message stack, and callers should check the API return status. Customizations that extend or bypass the TCA merge process should not call this package directly; instead they should route through the supported merge framework to preserve data integrity. As with all APPS-owned packages, it should never be modified, and behavior may differ subtly between 12.1.1 and 12.2.2 depending on the applied patch level.