Search Results arp_cmerge_arcus




Overview

ARP_CMERGE_ARCUS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its role within the Oracle Receivables (AR) module is to support the customer merge process, the utility by which two duplicate customer records are consolidated into a single surviving record. In the Trading Community Architecture (TCA) data model used by Release 12, customer information is distributed across a large set of interrelated HZ and HZ_CUST tables, and a merge must reconcile accounts, sites, roles, profiles, relationships, and contact points while preserving referential integrity. The ARP_CMERGE_ARCUS package contributes to this effort by handling the customer-specific segments of that consolidation, providing the procedural logic that moves or deletes subordinate rows and records the results of each merge operation. The object is documented in the ETRM repository with a status of VALID and is classified as an OTHER API, meaning it is an internal, implementation-support package rather than a published integration interface.

Key Procedures and Functions

The package exposes five documented procedures that reflect the principal stages of a customer merge:

  • MERGE — The controlling routine that drives the customer consolidation logic for the records in scope, coordinating the work performed by the supporting procedures.
  • CREATE_SAME_SITES — Creates site records that are identical or equivalent between the source and target customers, ensuring site-level data is preserved or rationalized during consolidation.
  • CREATE_TEMPORARY_TABLE — Builds a temporary working structure used to stage the rows to be processed, a common pattern in large-scale merge operations that must batch their work.
  • DELETE_ROWS — Removes obsolete or superseded rows from the affected tables once their data has been migrated to the surviving customer.
  • MERGE_HISTORY — Maintains the history and audit trail of the merge, recording what was consolidated for later reporting and traceability.

The ETRM metadata does not document parameter lists for these procedures; parameter signatures should be confirmed by inspecting the package specification in the target instance.

Tables Accessed

The package references its tables through APPS synonyms, touching the core TCA customer entities. These include HZ_CUST_ACCOUNTS and its _M audit table, HZ_CUST_ACCT_SITES_ALL and _M, HZ_CUST_ACCT_RELATE_ALL and _M, HZ_CUST_ACCOUNT_ROLES and _M, and HZ_CUST_CONTACT_POINTS, all of which hold the accounts, sites, relationships, roles, and contact point assignments that must be reassigned to the surviving customer. HZ_CONTACT_POINTS and HZ_CUSTOMER_PROFILES with HZ_CUSTOMER_PROFILES_M supply contact and profile information. HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S provide the merge audit and history structures, which is consistent with the MERGE_HISTORY procedure. Access is read/write, with the package updating and deleting rows as part of consolidation.

Usage Notes

ARP_CMERGE_ARCUS is an internal utility invoked by the Oracle Receivables customer merge infrastructure rather than called directly by end users. The ETRM dependency data shows it is referenced by the package ARP_CMERGE_MASTER, which serves as the orchestrating layer for the merge process, confirming that ARP_CMERGE_ARCUS is a subordinate component within the merge framework. In practice it executes when a user runs the Customer Merge function from the Receivables or TCA user interface, or when the corresponding customer merge concurrent program is submitted. Customizations that extend or bypass the standard merge process should call the supported merge APIs in ARP_CMERGE_MASTER rather than this package, since ARP_CMERGE_ARCUS is an internal implementation object and its signature is not part of Oracle's published interface contract. Any direct invocation in custom code risks incompatibility across patches and upgrades.