Search Results get_party_merge_event_data




Overview
Explore in AI Chat

Overview

HZ_EXTRACT_MERGE_EVENT_PKG is a public PL/SQL package owned by APPS in the Oracle E-Business Suite, classified under the Oracle Trading Community Architecture (TCA) product family. Its documented purpose is to expose merge event details for parties and customer accounts, primarily through the "Get Merge Details API" and the "Get Account Merge Details API." These APIs retrieve the outcome of merge operations that have been performed against TCA entities, such as duplicate party records and duplicate customer accounts consolidated through Oracle Data Quality Management.

The package is declared with AUTHID CURRENT_USER and its header carries the version identifier ARHMEVTS.pls 120.3.12010000.2 (dated 2009/02/04). It is documented in the Oracle Trading Community Architecture Technical Implementation Guide (120hztig.pdf) under Data Quality Management Availability APIs. The package is intended for consumers who need programmatic visibility into which records were merged, the direction of the merge, and the resulting account or party structure.

Key Procedures and Functions

  • GET_OBJECT_TYPE — Returns the object type as a VARCHAR2 for a given table name and table identifier. This helper allows callers to determine the TCA entity classification associated with a merge event record.
  • GET_OPERATING_UNIT — Returns the operating unit name (as VARCHAR2) associated with a supplied organization identifier.
  • GET_ACCOUNT_MERGE_EVENT_DATA — The documented Get Account Merge Details API. It accepts a customer merge header ID, initializes the message list when requested, and populates an account merge object containing the customer merge ID, request ID, associated party information, merge-to account ID, account number, account name, and source system management mappings for all accounts involved in the merge. It returns standard API status, message count, and message data outputs.
  • GET_PARTY_MERGE_EVENT_DATA — The party-level counterpart, providing merge event details for party records rather than customer accounts.

All APIs follow the standard Oracle EBS PL/SQL API convention: an initialization flag (defaulting to FND_API.G_FALSE), input identifiers, structured output objects, and the x_return_status, x_msg_count, and x_msg_data output parameters.

Tables Accessed

The package references TCA base and interface tables through APPS synonyms. Merge control data is drawn from HZ_MERGE_BATCH, HZ_DUP_BATCH, HZ_DUP_SETS, and HZ_MERGE_DICTIONARY. Customer account information is read from HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_M, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_RELATE_ALL_M, HZ_CUST_ACCOUNT_ROLES, and HZ_CUST_ACCOUNT_ROLES_M. Supporting profile and contact data is obtained from HZ_CUSTOMER_PROFILES, HZ_CUSTOMER_PROFILES_M, HZ_CUST_PROFILE_AMTS, HZ_CUST_PROFILE_AMTS_M, and HZ_CONTACT_POINTS. The "_M" suffixed tables represent the merge (staging) versions used during consolidation, which explains why both transactional and merge variants are accessed.

Usage Notes

This package is typically invoked by custom code, integration programs, or diagnostics that need to interrogate the results of a customer or party merge after the merge batch has completed. Because it is a public, active API with no other packages referencing it, it is intended primarily for external consumption rather than internal dependency. Callers should supply a valid customer merge header ID, check x_return_status before consuming the returned merge object, and inspect x_msg_data when a single error message is present. Merge operations should be completed and committed before extraction, since the API reads the persisted merge batch and account structures.