Search Results cs_merge_sys_ship_use_id

Overview

APPS.CSP_CMERGE_BB4 is a member of the Customer Merge (CMERGE) block series within Oracle E-Business Suite, specifically the "BB" family of packages that handle the physical column-level remapping of child records when two customer or site entities are merged. In release 12.1.1 and 12.2.2, the Customer Merge process is orchestrated by RA_CUSTOMER_MERGES and executed through a numbered sequence of CSP_CMERGE_BB*n* packages, each of which owns a discrete slice of the merge workload.

The header comment embedded in the source identifies this package as the "main block for merging the cs_templates_interface table." Its single documented program unit, MERGE, calls a chain of subroutines that update the CS_TEMPLATES_INTERFACE staging table, replacing the surviving (target) entity's identifiers in place of the being-merged (source) entity's identifiers. Column names such as CS_MERGE_SYS_INSTALL_SITE_ID and the search term cs_merge_sys_ship_use_id correspond directly to identifier columns on CS_TEMPLATES_INTERFACE that carry a system install site or ship-to use identifier. These columns must be repointed whenever a site or use ID is consolidated into another during a customer merge.

Key Procedures and Functions

The package exposes exactly one documented procedure, MERGE. It takes the standard Customer Merge driving parameters — a request ID, a set number, and a process mode — which is consistent with the CSP_CMERGE_BB*n* family design, where the concurrent request parameters are passed down from the merge controller so that each block can identify its work set and log its activity against the request.

Internally, MERGE invokes a fixed call sequence that performs the actual column updates against CS_TEMPLATES_INTERFACE. The sequence documented in the header is:

• CSP_CMERGE_BB4.MERGE — entry point that owns the cs_templates_interface remap
• CS_MERGE_SYS_INSTALL_SITE_ID — remaps the system install site ID column
• CS_MERGE_SYS_SHIP_USE_ID — remaps the system ship-to use ID column (the term the user searched)
• CS_MERGE_CP_INSTALL_SITE_ID — remaps the counterparty install site ID column
• CS_MERGE_CP_SHIP_SITE_ID — remaps the counterparty ship site ID column
• CS_MERGE_CUSTOMER_ID — remaps the customer ID column
• CS_CHECK_MERGE_DATA — validates the rewritten rows after the column updates complete

Each of the CS_MERGE_* helpers is a private routine scoped to this block; only MERGE is documented as publicly callable. Their names describe the column each one rewrites, and CS_CHECK_MERGE_DATA acts as a post-update integrity check.

Tables Accessed

• CS_TEMPLATES_INTERFACE — the primary target of this block. MERGE and its helpers update the site, ship-use, and customer identifier columns on this staging table so that any template rows still pointing at the merged-away entity are repointed to the surviving entity.
• RA_CUSTOMER_MERGES — the Customer Merge control and audit table. The package reads merge context from here (source and target party/site IDs, request ID, set number, status) and writes progress or completion status back so the parent merge request can track which blocks have finished.

Both tables are accessed through APPS synonyms, reflecting the package's AUTHID CURRENT_USER declaration and its execution in the APPS schema.

Usage Notes

CSP_CMERGE_BB4 is not intended to be called directly by end users or custom code. It is invoked by the Oracle Customer Merge concurrent program as part of the block dispatch framework, which calls each CSP_CMERGE_BB*n* package in turn, passing req_id, set_number, and process_mode. In an EBS 12.1.1 or 12.2.2 environment, the practical trigger is submitted through the Customer Merge form or the "Customer Merge" concurrent request, after the standard merge validation and lock steps have completed.

Because AUTHID CURRENT_USER is declared, the package executes with the privileges of the calling session, which is expected to be APPS. Customizations should never modify or wrap this package; instead, any site-specific logic belongs in a separate, clearly named custom package. Diagnosing failures related to cs_merge_sys_ship_use_id typically involves inspecting RA_CUSTOMER_MERGES for the affected request and verifying that CS_TEMPLATES_INTERFACE rows were correctly updated, with the merge request log providing the block-level status recorded by MERGE.