Search Results cs_inc_all_merge_cont_points

Overview

APPS.CS_SR_PARTY_MERGE_PKG is a PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema that supports the customer and party merge process within the Service (CSI/CS) product family. In EBS Release 12.1.1 and 12.2.2, party merge functionality is executed through the Oracle Trading Community Architecture (TCA) and Oracle Customer Data Management (CDM) "Party Merge" concurrent programs, which consolidate duplicate parties, accounts, and contacts into a single surviving record. Because the Service modules store references to parties, contacts, sites, and site uses across their own transactional tables, these references must be remapped or archived during a merge. CS_SR_PARTY_MERGE_PKG provides the Service-side implementation of that remapping logic.

The package is classified in the ETRM metadata as an "OTHER" API (not a formal public API), meaning it is intended to be called internally by the merge orchestration layer rather than directly by customer code. It is referenced by and references the sibling package CS_PARTYMERGE_PKG, which acts as the controlling gateway for Service-related merge processing. The package status is VALID, confirming it is compiled and available in the APPS schema.

Key Procedures and Functions

The documented package exposes seventeen procedures and functions, organized into three functional groups:

• Incremental processing routines (CS_INC_ALL_*): CS_INC_ALL_MERGE_PARTY, CS_INC_ALL_MERGE_BILL_TO_CONT, CS_INC_ALL_MERGE_SHIP_TO_CONT, CS_INC_ALL_MERGE_SITE_USES, CS_INC_ALL_MERGE_SHIP_SITE_USE, CS_INC_ALL_MERGE_SITE_ID, CS_INC_ALL_MERGE_CT_SITE_ID, CS_INC_ALL_MERGE_INST_SITE_USE, and CS_INC_ALL_MERGE_CONT_POINTS. These routines perform the bulk remapping of party, bill-to contact, ship-to contact, site use, site identifier, contact site identifier, install site use, and contact point references on Service transaction records. The "INC_ALL" prefix indicates that they operate over the complete set of affected rows rather than a single record.
• Audit routines (CS_AUDIT_*): CS_AUDIT_MERGE_PARTY, CS_AUDIT_MERGE_OLD_BILL_CONT, CS_AUDIT_MERGE_SHIP_TO_CONT, CS_AUDIT_MERGE_OLD_SHIP_CONT, CS_AUDIT_MERGE_SITE_ID, and CS_AUDIT_MERGE_OLD_SITE_ID. These procedures capture the pre-merge values of party, contact, and site identifiers so that the merge operation can be traced or reversed for auditing and reconciliation purposes.
• Contacts routines (CS_CONTACTS_*): CS_CONTACTS_MERGE_PARTY and CS_CONTACTS_MERGE_CONT_POINTS. These handle the remapping of contact-level and contact-point-level references specific to the Contacts module.

Tables Accessed

Per the ETRM metadata, the package reads and writes the following tables through APPS synonyms:

• CS_HZ_SR_CONTACT_POINTS: Stores service-request contact point associations; remapped by the contact point merge routines.
• CS_INCIDENTS_ALL_B: The base table for service incidents (service requests); party, contact, and site references are updated during merge.
• CS_INCIDENTS_AUDIT_B: The audit shadow of the incidents base table; used to record pre-merge values.
• HZ_MERGE_BATCH: The TCA merge batch table that identifies the parties and merge set being processed.
• PLITBLM: The standard Oracle PL/SQL table-of-rows mechanism used to pass batches of identifiers between the caller and the incremental merge routines.

Usage Notes

CS_SR_PARTY_MERGE_PKG is not invoked directly from a user interface. It is called by the Party Merge concurrent program through the TCA merge framework, which delegates Service-owned entities to CS_PARTYMERGE_PKG; that package in turn invokes the incremental and audit routines here. Customizations should not call this package directly, as its procedures assume the caller has already established the merge context (registry entries in HZ_MERGE_BATCH, active batch identifier, and commit scope). Because the incremental routines operate on all affected rows in a single pass, execution is typically performed during the merge validation and execution phases, with the audit routines ensuring that an undo record exists before the surviving party identifier is committed to the Service tables.