Search Results csp_cmerge_bb7

Overview

APPS.CSP_CMERGE_BB7 is a PL/SQL package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that supports the customer merge process for Oracle Service (Service/TeleService) repair records. The package is declared with the AUTHID CURRENT_USER directive, meaning its SQL statements execute with the privileges of the invoking user rather than the package owner, which is standard for merge-related utilities operating under the merge request session.

The package serves as what the source comments describe as a "main block" for merging the CS_REPAIRS table. It is one of a series of merge "building block" packages (denoted by the BB7 suffix) that the customer merge framework invokes to propagate a surviving customer identifier across dependent transactional tables. When duplicate customer records are merged in Oracle Receivables, the merge engine calls such building-block packages to keep tables such as CS_REPAIRS consistent with the surviving party.

Key Procedures and Functions

The documented package metadata lists a single exposed program unit: MERGE. This procedure provides the single entry point through which the merge framework invokes the package. It is documented as accepting three parameters — a request ID (req_id), a set number (set_number), and a process mode (process_mode) — although the detailed parameter semantics are not elaborated in the ETRM excerpt and should be confirmed against the actual package specification.

The MERGE procedure is the orchestrating driver for the CS_REPAIRS table merge. Per the source comments, it calls an internal merge procedure that in turn invokes additional procedures responsible for performing the actual updates on CS_REPAIRS. The documented call sequence identifies the chain as CSP_CMERGE_BB7.MERGE (table CS_REPAIRS) flowing down into CS_MERGE_CUSTOMER_ID, which carries out the corrected customer identifier assignment. The package therefore acts as a thin, purpose-built wrapper whose design intent is to isolate the repair-table merge logic into a reusable, framework-callable unit.

Tables Accessed

The ETRM metadata documents one table referenced by this package through APPS synonyms: RA_CUSTOMER_MERGES. This is the central audit and control table for the Oracle Receivables customer merge process. It records the merge request, the source and target customer relationships, and the Set of Books or party context under which the merge executes. In this context, CSP_CMERGE_BB7 reads RA_CUSTOMER_MERGES to determine the merge parameters — particularly the customer identifiers and merge set — that govern how CS_REPAIRS rows should be updated. The underlying workhorse, CS_MERGE_CUSTOMER_ID, applies the resulting customer identifier to the repair records, consistent with the package's stated purpose of merging the CS_REPAIRS table.

Usage Notes

This package is not intended to be invoked directly by end users. It is registered with and launched by the Oracle customer merge concurrent program framework (the same framework that processes the Receivables Customer Merge). When a user submits a customer merge, the merge process discovers dependent tables and calls each registered building-block package, including CSP_CMERGE_BB7, passing the merge request identifier and set number through the MERGE signature.

Because it executes under AUTHID CURRENT_USER, database privileges for the session must permit access to CS_REPAIRS and RA_CUSTOMER_MERGES; the merge framework's session normally supplies these. Custom extensions should call the package only through the supported merge framework or via a deliberately isolated request, since the request and set identifiers must correspond to an active merge context. The metadata records that the package is referenced by one other package, reinforcing that it is an internally chained component of the merge call stack rather than a standalone utility. Administrators troubleshooting a merge should treat any failure here as a repair-table update issue tied to the merge in RA_CUSTOMER_MERGES. Given the package's provenance (header version 115.0), it is a long-standing component whose behavior is stable across both the 12.1.1 and 12.2.2 release trains.