Search Results hz_audit_acct_merge




Overview
Explore in AI Chat

Overview

The APPS.XDP_PARTY_MERGE package body is a party-data remediation utility within the Oracle E-Business Suite, responsible for reconciling downstream Oracle Depot Repair (XDP) transactional data when two customer or party records are merged in Oracle Receivables / Trading Community Architecture. When a duplicate customer account or customer site is consolidated via the standard TCA customer merge process, references held in Depot Repair order headers and order line items may still point at the now-obsolete ("duplicate") account or site identifiers. XDP_PARTY_MERGE exists to redirect those stale foreign keys to the surviving ("master") identifiers, keeping repair orders consistent with the merged party.

The package is a server-side PL/SQL unit owned by APPS and is classified under the ETRM as an OTHER API. Its header comments indicate a last revision dating from the 12.0.x code line (XDPMERGB.pls 120.3), and the logic remains applicable to both 12.1.1 and 12.2.2, where the customer merge architecture (RA_CUSTOMER_MERGES and RA_CUSTOMER_MERGE_HEADERS) is unchanged.

Key Procedures and Functions

ETRM documents a single procedure for this package body:

  • ACCOUNT_MERGE — the sole documented entry point. Its purpose is to process the set of merge records that the Receivables customer merge concurrent program has staged but not yet flagged as processed, and to re-point affected Depot Repair entities to the surviving account or site. The procedure accepts the merge request context (request identifier, set number) and a processing mode indicator, and performs its work in a coordinated, chunked manner so that large merges do not exceed memory or transaction limits.

The declaration section reveals the implementation strategy: strongly typed PL/SQL collections (MERGE_HEADER_ID_LIST_TYPE, ORDER_ID_LIST_TYPE, CUST_ACCOUNT_ID_LIST_TYPE, LINE_ITEM_ID_LIST_TYPE, SITE_USE_ID_LIST_TYPE) bulk-collect the affected primary keys, while two driving cursors (merged_records and merged_records1) select distinct merge header, order, account, line item, and site-use identifiers for the given request and set where RA_CUSTOMER_MERGES.PROCESS_FLAG = 'N'. A process_mode = 'LOCK' branch allows a locking/no-op pass, and Oracle error messaging is initialized through ARP_MESSAGE.SET_NAME.

Tables Accessed

Per the documented metadata, the package touches the following APPS-synonymed tables:

  • RA_CUSTOMER_MERGES — the Receivables staging table of party/account merge transactions; read to identify duplicate and master account and site identifiers and to test the PROCESS_FLAG.
  • RA_CUSTOMER_MERGE_HEADERS — the merge header key source, used to associate each staged merge with its CUSTOMER_MERGE_HEADER_ID.
  • XDP_ORDER_HEADERS — Depot Repair order headers; read and updated to replace the obsolete CUST_ACCOUNT_ID with the surviving account.
  • XDP_ORDER_LINE_ITEMS — Depot Repair order lines; read and updated to replace the obsolete SITE_USE_ID with the surviving site-use reference.
  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the TCA merge history tables, providing the authoritative record of which identifiers were merged.
  • PLITBLM — the standard Oracle Applications temporary table used for indexed PL/SQL table lookups within the merge loop.

Usage Notes

XDP_PARTY_MERGE.ACCOUNT_MERGE is not an end-user-facing API; it is invoked programmatically as part of the customer merge workflow. In a typical deployment it is called by a concurrent program or a coordinating wrapper that first runs the standard Receivables/TCA merge, then calls this package to synchronize Depot Repair data, passing the concurrent request ID, the set number being processed, and the desired processing mode.

Because the package is referenced by zero other PL/SQL packages in the ETRM dependency map, it is effectively a leaf utility called from external drivers — most commonly a concurrent program registration or the customer merge form's post-processing logic. Customizations should not call ACCOUNT_MERGE directly against production data outside the merge framework, since it relies on rows staged in RA_CUSTOMER_MERGES with PROCESS_FLAG = 'N' and a matching request/set combination. The presence of the hz_audit_acct_merge search term alongside this package suggests it is frequently investigated during audits of merge-related data inconsistencies, particularly when Depot Repair orders retain references to accounts or sites that no longer exist after a merge. No documented public parameters are republished here, and the object carries no ETRM-documented function variants beyond ACCOUNT_MERGE.