Search Results fin_report

Overview

APPS.HZ_EXTRACT_MERGE_EVENT_PKG is a PL/SQL package body in the Oracle E-Business Suite Trading Community Architecture (TCA) and Receivables (AR) module. Its purpose is to extract and consolidate the details of customer merge events so that those details can be processed by downstream merge and de-duplication logic. In Oracle EBS, the merge process is used to combine duplicate parties, customer accounts, and related entities into a single surviving record. This package supplies the event payload for those operations, resolving the parent object type of a given source table and assembling the merge event data for both party-level and account-level merges. The header reference (ARHMEVTB.pls 120.3) confirms placement in the AR product family, while the naming and managed table list confirm its role in the TCA customer data model.

Key Procedures and Functions

• GET_OBJECT_TYPE — Determines the logical object type for a given source table and primary key. It first delegates to HZ_EXTRACT_BO_UTIL_PVT.GET_PARENT_OBJECT_TYPE; if that returns null, it maps specific TCA tables to a type code. Notably, a row in HZ_CUSTOMER_PROFILES maps to the type CUST_PROFILE, while HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, HZ_FINANCIAL_REPORTS, and HZ_EMPLOYMENT_HISTORY map to CP type, ORG_CONTACT, FIN_REPORT, and EMP_HIST respectively. Any unrecognized table is returned unchanged.
• GET_OPERATING_UNIT — Returns the operating unit name for a supplied organization identifier by querying HR_OPERATING_UNITS. This provides the organizational context stamped onto extracted merge events.
• GET_ACCOUNT_MERGE_EVENT_DATA — Extracts the details of an account merge, given an initialization message list flag and a customer merge header identifier, and returns an account merge object along with return status and message information.
• GET_PARTY_MERGE_EVENT_DATA — Extracts the corresponding details for a party-level merge event.

The two event-data procedures are the principal entry points; the two functions are supporting utilities for type resolution and organizational attribution.

Tables Accessed

The package reads from a broad set of TCA tables. HZ_CUSTOMER_PROFILES and its _M (multi-org) counterpart, together with HZ_CUST_PROFILE_AMTS and HZ_CUST_PROFILE_AMTS_M, supply customer profile and profile-amount information. HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_CUST_ACCT_RELATE_ALL, along with their _M variants, provide account, role, and account-relationship data required to build the merge payload. HZ_CONTACT_POINTS contributes contact-point type resolution. Merge orchestration and classification data come from HZ_MERGE_BATCH, HZ_MERGE_DICTIONARY, HZ_DUP_BATCH, and HZ_DUP_SETS, which identify the merge batch and the duplicate sets being consolidated. Because merge extraction spans both base and multi-org tables, the package is sensitive to operating-unit context, which explains the inclusion of GET_OPERATING_UNIT.

Usage Notes

The package is not documented as being referenced by any other package, indicating it is invoked directly rather than through a shared API layer. It is typically called by the customer merge and de-duplication flows, either from the TCA merge user interface (for example, the customer merge forms), from concurrent programs that process merge batches such as HZ_MERGE_BATCH and HZ_DUP_BATCH, or from custom extensions that need to capture merge event details. When extending or debugging merge behavior, note that GET_OBJECT_TYPE is the mechanism that translates HZ_CUSTOMER_PROFILES rows into the CUST_PROFILE type, so any custom profile-driven logic must account for that mapping. Because the API classification is OTHER rather than PUBLIC, it should be treated as an internal implementation detail; oracle-supported entry points for merge operations remain the documented TCA merge APIs, and direct calls to this package should be made only with awareness of its internal-use status.