Search Results cs_merge_sys_install_site_id

Overview

CSP_CMERGE is the master orchestration package for customer merge processing within the Oracle EBS Customer Service (Service) application, declared as AUTHID CURRENT_USER. Its documented purpose is to serve as the main process that calls all building blocks required to execute a customer merge against the Service database schema. Rather than performing field-level updates itself, CSP_CMERGE delegates the actual work to a series of subordinate building-block packages (CSP_CMERGE_BB1 through CSP_CMERGE_BB8 in the documented hierarchy), each of which is responsible for the complete merge of one Service table. This design isolates table-specific merge logic while providing a single entry point for the overall Service-side customer merge, ensuring that customer identifiers and the various site-use identifiers (install, ship-to, bill-to) are consistently repointed when two customer records are combined.

Key Procedures and Functions

The package exposes one documented procedure: MERGE. This procedure constitutes the main driver for the Service customer merge. It iterates across all Service tables requiring merge treatment and invokes the corresponding building-block package's own MERGE procedure for each. Each building block then calls local routines that merge the individual columns of its target table. The documented calling sequence shows MERGE dispatching sequentially to the building blocks for cs_access_control_templates (BB1), cs_customer_products (BB2), cs_systems (BB3), cs_templates_interface (BB4), cs_mass_notification_txns_temp (BB5), cs_mass_service_txns_temp (BB6), cs_repairs (BB7), and cs_incidents (BB8).

Tables Accessed

The merge scope documented for CSP_CMERGE covers the following Service tables, each handled by its own building block: cs_access_control_templates, cs_customer_products, cs_systems, cs_templates_interface, cs_mass_notification_txns_temp, cs_mass_service_txns_temp, cs_repairs, and cs_incidents. Within these blocks, local merge routines update the foreign-key style columns that reference customer and site-use entities — for example CS_MERGE_CUSTOMER_ID, CS_MERGE_SYS_INSTALL_SITE_ID, CS_MERGE_CP_INSTALL_SITE_ID, CS_MERGE_BILL_TO_SITE_ID, CS_MERGE_INSTALL_SITE_ID, and CS_MERGE_SHIP_TO_SITE_ID. The cs_repairs block operates on RMA_CUSTOMER_ID, while the cs_incidents block addresses CUSTOMER_ID along with ship-to and bill-to site-use identifiers. Notably, a CS_CHECK_MERGE_DATA routine appears in the BB1, BB3, and BB4 sequences, providing validation of merge data before those tables are committed.

Usage Notes

CSP_CMERGE is not a standalone utility; it is invoked as part of the Oracle EBS Customer Merge (Trading Community / Customer merge) process, which is driven from the standardized customer merge concurrent program flow. The Service application registers CSP_CMERGE.MERGE as its contribution to that cross-application merge, so it is ordinarily executed by the merge framework rather than called directly by users. Custom code should treat CSP_CMERGE as an integration point only when extending Service-side merge behavior, and any extension should follow the existing building-block pattern. Because the package was authored against the Service schema under AUTHID CURRENT_USER, execution requires the appropriate APPS-level privileges and an active customer merge session; it should never be run outside the sanctioned merge lifecycle.