Search Results cp_cmerge_bb4

Overview

APPS.CSP_CMERGE_BB4 is a concurrent-program support package body belonging to the Oracle Customer Relationship Management and Trade Management (CSP) module. Its function is to perform the block-four merge step against the CS_TEMPLATES_INTERFACE staging table, resolving the site-use and customer identifiers that appear in the template interface rows once a source customer has been merged into a target customer. It is a utility package used by the customer merge process and is documented with the API classification OTHER, indicating that it is not a public, supported business API but an internal worker invoked by the merge framework.

A search for "cs_templates_interface" surfaces this object because the package is the component that reconciles template interface records with a customer merge. The header comment preserved in the source states explicitly that the procedure handles the merge process for CS_TEMPLATES_INTERFACE, calling five separate procedures to complete the task. The package therefore occupies a narrow but critical position: it ensures that service template records, which carry site-use identifiers and a customer identifier, remain internally consistent and correctly re-pointed after merge processing changes the customer master.

Key Procedures and Functions

The documented interface exposes a single public entry point, MERGE.

• MERGE — the main entry point. It accepts a concurrent request identifier, a set number, and a process mode, and orchestrates the full update of CS_TEMPLATES_INTERFACE. It writes a report header line to the log ("CP_CMERGE_BB4.MERGE()+") and, when the process mode is LOCK, writes a locking-table message using ARP_MESSAGE with the token set to CS_TEMPLATES_INTERFACE. MERGE does not perform the updates itself but delegates to five internal procedures defined in the specification: CS_MERGE_SYS_INSTALL_SITE_ID, CS_MERGE_SYS_SHIP_SITE_ID, CS_MERGE_CP_INSTALL_SITE_ID, CS_MERGE_CP_SHIP_SITE_ID, and CS_MERGE_CUSTOMER_ID. A further local procedure, CS_CHECK_MERGE_DATA, is declared for data validation. These local procedures are not part of the documented interface and are listed here only to describe the MERGE design.

Tables Accessed

• CS_TEMPLATES_INTERFACE — the primary target of the merge. The package updates the system_ship_to_site_use_id, system_install_site_use_id, cp_ship_to_site_use_id, cp_install_site_use_id, and customer_id columns to reflect the surviving customer and its site uses.
• RA_CUSTOMER_MERGES — the receivables customer merge audit table, referenced to identify the source and target customers associated with the merge, and to drive the identifier translations applied to the interface rows.

Usage Notes

CSP_CMERGE_BB4 is normally invoked by the customer merge concurrent program rather than called directly. During a merge, the framework passes the request identifier, set number, and process mode to MERGE, which logs progress through ARP_MESSAGE and updates the staged template interface rows. The referenced-by metadata shows one dependent package, confirming it is a subordinate component of a larger merge chain. Because the API is classified OTHER, direct calls from forms or custom code are not recommended; implementations should use the standard customer merge flow so that locking, set numbering, and logging are handled correctly. In both Oracle EBS 12.1.1 and 12.2.2 the behavior is identical, as the package logic is driven by the merge request rather than release-specific features.