Search Results pap_cmerge_bb2




Overview
Explore in AI Chat

Overview

PAP_CMERGE_BB2 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under API type OTHER. It belongs to the Oracle Projects (PA) module family and serves as a supporting component of Oracle's customer merge infrastructure. Its primary business purpose is to consolidate and reconcile project contact records when two customer (or trading partner) records are merged through the standard Oracle customer merge process.

When an organization performs a customer merge — for example, when duplicate customer records exist because a trading partner was created in multiple operating units, or when one customer record is deemed a duplicate of another — the merge utility must cascade updates to every dependent entity that references the obsolete customer. Project contacts defined in Oracle Projects reference customer records and therefore must be reassigned to the surviving (target) customer. PAP_CMERGE_BB2 provides that reassignment logic for the Projects application.

The package is compiled with AUTHID CURRENT_USER, meaning its unqualified object references resolve according to the privileges of the invoking session rather than the package owner. This is consistent with other Oracle Projects merge helper packages and supports execution in contexts where the APPS schema owns the underlying objects while the merge driver runs under a controlled privilege set.

Key Procedures and Functions

The package exposes a single documented procedure, MERGE_PA_PROJECT_CONTACTS. Its declared signature accepts a request identifier (req_id) and a set number (set_no), reflecting the standard Oracle customer merge architecture in which the merge is decomposed into multiple scheduled sets, each processed in a separate concurrent request. The req_id ties the invocation to a specific merge request row, and set_no identifies which batch of dependent entities is handled by this pass.

The procedure's purpose is to update PA_PROJECT_CONTACTS rows so that contacts associated with the merge source customer are redirected to the surviving merge target. No additional procedures or functions are documented in the ETRM metadata for this package.

Tables Accessed

ETRM metadata lists five tables referenced through APPS synonyms:

  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the customer merge log tables in Oracle Trading Community Architecture (TCA). These track the merge request header information, including source and target party or customer identifiers, and are read to determine the mapping applied during the merge.
  • RA_CUSTOMER_MERGES — the legacy Receivables customer merge staging table, which records the source-to-target customer relationship and merge request key.
  • PA_PROJECT_CONTACTS — the principal table operated upon. Rows pointing at the merge source customer are updated or reassigned to the surviving customer.
  • PA_PROJECTS — referenced to validate the project context of the affected contact records and to ensure updates respect project-level integrity.

Usage Notes

PAP_CMERGE_BB2 is not a general-purpose user-facing API. It is invoked programmatically by the Oracle customer merge framework during the processing of a customer merge request, typically as each merge set is executed by a concurrent request submitted by the merge manager. It is not exposed through a standard Oracle EBS form or directly scheduled concurrent program owned by Oracle Projects; rather, it is called by the merge orchestration layer along with other "BB" merge helper packages from adjacent modules.

Because the package is referenced by one other package in the documented dependency graph, the caller is responsible for supplying a valid req_id and set_no derived from the originating merge request. Customizations should not call MERGE_PA_PROJECT_CONTACTS directly unless the calling code faithfully reproduces the merge framework's request and set semantics; misuse can leave PA_PROJECT_CONTACTS rows orphaned or inconsistent with the merge log. In 12.1.1 and 12.2.2 environments, administrators investigating contact discrepancies after a customer merge should review the concurrent request log for the corresponding merge set, as failure within this package aborts processing for the affected set.