Search Results account_merge

Overview

XDP_PARTY_MERGE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is classified under the ETRM API classification "OTHER," indicating that it is not part of the formally published public API set but instead functions as a supporting internal routine used by Oracle's party and account merge infrastructure. Its header declares AUTHID CURRENT_USER, meaning that the package executes with the privileges of the invoking schema rather than the definer, and it exposes a single documented global variable, G_COUNT, along with one public procedure, ACCOUNT_MERGE.

The package addresses the account merge process in Oracle EBS, which consolidates duplicate or redundant customer accounts and their associated parties and transactions into a single surviving entity. This is a critical data-cleansing activity in implementations where trading partners, customers, or ordering entities were entered multiple times. XDP_PARTY_MERGE operates specifically within the Order Capture/order management data domain (the XDP schema prefix relates to order capture and fulfillment), ensuring that order headers and order line items belonging to the merged (duplicate) account are re-pointed or otherwise handled consistently with the surviving account record.

Key Procedures and Functions

The package documents exactly one public procedure:

• ACCOUNT_MERGE — the primary entry point for performing an account merge operation. It accepts a request_id identifying the concurrent request or merge job, a set_number identifying the merge set or batch, and a process_mode that controls the behavior of the merge run (for example, validation versus execution). The procedure is responsible for orchestrating the merge of order-related records associated with the parties/accounts being consolidated. The metadata does not provide a full parameter signature beyond these names, and no other procedures or functions are exposed in the specification.

Tables Accessed

The package references the following tables through APPS synonyms:

• HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the customer merge logging tables. These record the progress and outcome of each merge operation and are the primary source of merge-membership information the procedure uses to determine which accounts are being combined.
• RA_CUSTOMER_MERGES and RA_CUSTOMER_MERGE_HEADERS — the Receivables customer merge transaction and header tables. These hold the merge definition, including the party/account IDs before and after the merge, and govern which records must be reassigned.
• XDP_ORDER_HEADERS and XDP_ORDER_LINE_ITEMS — the order capture order header and line item tables. The procedure updates or re-points these records so that orders previously associated with the duplicate account are attributed to the surviving account.
• PLITBLM — a standard Oracle EBS PL/SQL index-by table (a PL/SQL table type used for bulk operations), not a physical table; it is used for in-memory collection handling during processing.

Usage Notes

XDP_PARTY_MERGE is an internal companion routine invoked as part of the standard Oracle customer merge process, rather than a package designed for direct call by end users. It is typically called from the concurrent program that drives the Customer Merge (party merge) flow, after the merge request has been submitted and the merge set established in the Receivables merge tables. The request_id links the invocation to that concurrent request, while set_number identifies the specific batch of merge records to process.

Because it is classified as OTHER rather than a formal public API, Oracle does not guarantee its signature across releases, and it is absent from the documented list of packages that reference other packages. Customizations should not call it directly without careful validation; instead, the supported Customer Merge concurrent programs should be used so that all dependent objects (including XDP order capture data) are processed consistently. Any direct invocation carries upgrade risk, particularly given the header dates from a 2006 source label (XDPMERGS.pls 120.4) that remains common across 12.1.1 and 12.2.2 installations.