Search Results arp_cmerge_arcon




Overview
Explore in AI Chat

Overview

The APPS.ARP_CMERGE_ARCON package is a PL/SQL consolidation utility within the Oracle Receivables module of Oracle E-Business Suite. Its name derives from "AR" (Receivables), "CMERGE" (Customer Merge), and "ARCON" (AR Consolidation). The package provides the server-side consolidation logic invoked during the Oracle Receivables customer merge process, the operation in which two customer records (a "from" customer and a "to" customer) are combined into a single surviving record within the Trading Community Architecture (TCA) model.

When customers are merged in Oracle EBS, the merge is not a single transactional event; it is a multi-phase, batch-oriented operation executed through the Customer Merge concurrent programs. Each application module that holds customer-referenced data contributes its own merge logic. ARP_CMERGE_ARCON is the Receivables-side contributor responsible for reconciling Receivables consolidation data associated with the merged customer, ensuring that the surviving customer's Receivables records remain internally consistent after merge.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is typical of Oracle Applications public APIs and batch merge utilities that rely on the APPS schema synonyms at runtime.

Key Procedures and Functions

The package exposes a single documented procedure:

  • MERGE — The consolidation driver for the Receivables customer merge. It performs the Receivables-specific merge processing for a given batch. Its signature takes a request identifier, a set number, and a process mode. The request identifier associates the invocation with a concurrent request, the set number identifies the work set or batch being processed within the merge, and the process mode controls the phase or behavior of the merge execution (for example, whether the procedure is performing the actual data merge versus validation or reporting work). The procedure orchestrates the reads and writes required to synchronize Receivables consolidation tables with the surviving customer after the TCA-level merge has occurred. No additional procedures or functions are documented for this package.

Tables Accessed

The ETRM metadata documents the following tables, referenced through APPS synonyms, as the data touched by this package:

  • AR_CONS_INV — The Receivables consolidated invoice table. The merge procedure must reassign or consolidate consolidated billing invoice records from the obsolete customer to the surviving customer so that consolidated invoicing remains correct.
  • RA_CUSTOMER_MERGES — The primary Receivables customer merge staging/control table. It records the merge parties and drives which customers are being merged, and is the central table the procedure reads and updates.
  • RA_CUSTOMER_MERGE_HEADERS — The header-level merge control table describing the merge batch or run. The procedure references it to determine merge scope and status.
  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — The TCA customer merge log and its sequence. These record the history of merge operations across applications, and the procedure writes entries so that the Receivables merge activity is auditable and reversible.
  • PLITBLM — A PL/SQL index-by table used internally by Oracle Applications merge utilities, typically for holding collections of identifiers processed during the batch.

Usage Notes

ARP_CMERGE_ARCON is not intended to be called directly by end users. It is invoked programmatically as part of the Oracle Receivables customer merge concurrent process. To run it, users execute the Customer Merge concurrent program (or the master Customer Merge flow), which in turn calls each application's merge package in the correct sequence. The request identifier and set number parameters are supplied by the concurrent manager framework and by the parent merge driver; the process mode parameter enables the driver to invoke the procedure in different phases of the merge lifecycle.

Custom code should not call this package directly; the supported interface for merging customers is the standard TCA Customer Merge responsibility and its concurrent programs. The metadata notes that the package is referenced by one other package, confirming it operates as a subordinate module within a larger merge orchestration chain. Administrators diagnosing a failed customer merge should inspect the Receivables merge control tables and the HZ merge log populated by this procedure, and review the concurrent request log for the associated request identifier.