Search Results cs_systems




Overview
Explore in AI Chat

Overview

APPS.CSP_CMERGE_BB3 is a merge-processing package body used by Oracle E-Business Suite's Customer Merge infrastructure. Its documented purpose, drawn from its inline comments, is to handle the merge process for the CS_SYSTEMS table, which stores installed-base system records in Oracle's Service (CSI/CS) module. When two customer records are merged in Oracle EBS, installed-base systems associated with the duplicate ("from") customer must be reassigned to the surviving ("to") customer, and the subsystem site references within those records must be repointed accordingly. This package encapsulates that repointing logic for the CS_SYSTEMS entity.

The package is classified as OTHER in the ETRM metadata and exposes a single documented public procedure, MERGE. Internally it is organized around five local procedures declared in the package specification body header, which are invoked in sequence by MERGE to perform the individual update tasks.

Key Procedures and Functions

  • MERGE — The single documented entry point. It accepts the standard Customer Merge concurrent request context parameters (request ID, set number, and process mode) and serves as the driver for the CS_SYSTEMS merge. Its header output identifies the running block as "CP_CMERGE_BB3.MERGE()". When invoked in LOCK process mode, it emits the "AR_LOCKING_TABLE" message against CS_SYSTEMS and notes that locking is performed in block CSP_CMERGE_BB3; otherwise it emits AR_UPDATING_TABLE for the same table. Based on the source excerpt, MERGE delegates work to four separate update procedures, each targeting a distinct site-use or customer reference on CS_SYSTEMS.

The local procedures documented in the source excerpt are CS_MERGE_BILL_TO_SITE_ID, CS_MERGE_INSTALL_SITE_ID, CS_MERGE_SHIP_TO_SITE_ID, CS_MERGE_CUSTOMER_ID, and CS_CHECK_MERGE_DATA. Each takes the same merge context parameters (request ID, set number, process mode). Their names indicate the four update tasks described in the package comments: updating the bill-to site use, the install site use, the ship-to site use, and the customer identifier, with a fifth routine dedicated to validating merge data.

Tables Accessed

  • CS_SYSTEMS — The primary target of all update activity. The package locks this table in LOCK mode and updates its bill-to, install, ship-to, and customer reference columns during the merge.
  • RA_CUSTOMER_MERGES — The Customer Merge transaction table used by Oracle Receivables to record merge requests and their processing state. The package reads the merge context driven by this table's request records and, through the ARP_MESSAGE logging API, reports progress against the current merge set.

Usage Notes

CSP_CMERGE_BB3 is not intended to be called directly by end users. It is invoked as part of the Oracle EBS Customer Merge concurrent program flow, which orchestrates a series of block packages — each responsible for a subset of the dependent entities — against a submitted merge request. The order of operations across the overall merge is significant, and this package participates in the phase that repoints installed-base system records.

Invocation always supplies the request ID, set number, and process mode arguments, and the LOCK mode branch confirms that the framework first locks CS_SYSTEMS before performing updates. The ETRM metadata records one other package referencing this package, consistent with it being called from a merge coordinator rather than application forms or ad hoc code. Customizations involving CS_SYSTEMS merges should preserve this package's contract rather than bypassing it, because the Customer Merge framework depends on the standard lock-then-update pattern and on ARP_MESSAGE logging for progress and diagnostics. This object is present in both Oracle EBS 12.1.1 and 12.2.2, with the header revision string indicating a long-stable implementation.