Search Results cs_sr_account_merge_pkg




Overview

CS_SR_ACCOUNT_MERGE_PKG is an Oracle EBS service (TeleService / Customer Care) PL/SQL package owned by the APPS schema. Its business purpose is to support the merging of Oracle Trading Community Architecture (TCA) customer accounts in a Service Request (SR) context — that is, when two or more duplicate customer accounts, parties, or customer identifiers must be consolidated into a single surviving account, the package performs the Service-side work required to repoint SR and related customer references to the merged entity. In release 12.1.1 and 12.2.2, this package is a legacy (pre-12.x "noship") utility that pre-dates the more centralized TCA merge APIs, but it remains part of the delivered Service code base and is referenced by the standard customer merge flow. It is declared AUTHID CURRENT_USER, meaning execution privileges are determined by the calling user; the package owner is APPS.

Key Procedures and Functions

The package exposes two documented public procedures:

  • CS_MERGE_CUST_ACCOUNT_ID — The primary entry point for merging a customer account identifier in the Service/TCA context. It is designed to be invoked as part of the customer merge process and coordinates the update of Service Request records (and related log entries) so that the deprecated or "from" customer account ID is replaced by the surviving "to" account ID.
  • MERGE_CUST_ACCOUNTS — A companion procedure that performs the actual account-to-account merge logic. It is the lower-level routine that, given the merge identifiers, applies the account mapping and writes the corresponding customer merge log records.

Both procedures accept a request identifier, a merge set number, and a process mode parameter (as shown in the documented signature). The process_mode value typically distinguishes a validation/preview pass from an actual execution pass, allowing callers to dry-run the merge before committing. No other public functions are documented.

Tables Accessed

The package reads and writes the following documented objects, accessed through APPS synonyms:

  • CS_INCIDENTS_ALL_B — the base Service Request (incident) table; updated to repoint SRs from the merged-from account to the surviving account.
  • HZ_CUST_ACCOUNTS and HZ_PARTIES — the TCA customer account and party tables; read (and in some flows updated) to resolve the merge and its surviving entity.
  • RA_CUSTOMER_MERGERS and RA_CUSTOMER_MERGE_HEADERS — the Receivables/order-management customer merge staging and header tables that hold the merge definition and its batch context.
  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the TCA customer merge log (and its sequence) used to record each merge action for audit and reversibility.
  • PLITBLM — a PL/SQL index-by table used internally by the package for in-memory processing of merge rows.

Usage Notes

CS_SR_ACCOUNT_MERGE_PKG is not intended to be called by end users directly. It is typically invoked from the Oracle EBS Customer Merge concurrent program and from Service/TCA merge forms that need to include SR data in the account consolidation. Customizations and integrations that perform account merges may call the package as a wrapper, passing the request ID, merge set number, and process mode. Because it carries a legacy "noship" header and no dependencies are registered as referencing it from other delivered packages (0 referencing packages per the ETRM metadata), it should be treated as an internal, non-public API. When migrating to 12.2.2, engineers should confirm via the ETRM that the package has not been superseded by the standard HZ merge APIs, and should not rely on undocumented internal behavior or parameter semantics beyond the documented signature.