Search Results hz_customer_merge_log_s




Overview
Explore in AI Chat

Overview

The APPS.PAP_CMERGE_BB1 package body is a component of the Oracle E-Business Suite customer merge infrastructure, specifically oriented toward the Projects (PA) application. Its designated role is to handle the post-merge processing of project-related agreements when two customer or party records are consolidated through the standard Oracle Customer Merge (Trading Community Architecture / HZ) framework. In Oracle EBS 12.1.1 and 12.2.2, customer merge operations span many schemas, and each application contributes a Business Event or "BB" package (the _BB suffix) that reacts to the merge to reconcile its own transactional data. PAP_CMERGE_BB1 is the Projects-side handler that ensures project agreements linked to the losing ("from") customer are updated, reassigned, or invalidated so they correctly reference the surviving ("to") customer after the merge completes. Within the ETRM metadata it is classified as an OTHER API and is validated and valid in the APPS schema.

Key Procedures and Functions

The documented package exposes a single procedure, MERGE_PA_AGREEMENTS. This procedure encapsulates the Projects application's logic for merging agreements. Its purpose is to process the set of project agreements affected by a customer merge, applying the merge outcome to each agreement so that agreement records are not left pointing at a discarded customer. It is invoked as part of the larger customer merge batch orchestration, driven through PAP_CMERGE, and it relies on shared utility routines from HZ_UTILITY_PUB for common merge bookkeeping. No explicit parameter list is documented in the ETRM metadata; the procedure should be treated as an internal, framework-invoked routine rather than a publicly supported API. It is not referenced by any other database object, reinforcing its role as a leaf-level handler called by the merge engine.

Tables Accessed

  • PA_AGREEMENTS — the primary Projects table holding project agreements. The package updates agreement rows so they are reassociated with the surviving customer after the merge.
  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — the TCA merge log and its sequence. These record the parties, merge identifiers, and request context that the package reads to determine which agreements to process and to log merge activity.
  • RA_CUSTOMER_MERGES — the Receivables customer merge control table. It holds the merge request header (request ID, status, from/to customer identifiers) that drives the processing of every participating application package.

The specific reference to HZ_CUSTOMER_MERGE_LOG_S in the search context indicates the package (or its dependency graph) touches the merge-log sequence to record its actions against the correct merge log record.

Usage Notes

PAP_CMERGE_BB1 is not intended to be invoked directly by end users or custom code. It is called by the customer merge concurrent program flow that the user initiates via the Customer Merge form or the Customer Merge concurrent request. When a merge is submitted, the framework invokes the relevant application BB packages — including this Projects package — to propagate the merge to each dependent module's data. An applications user or extension developer should never call MERGE_PA_AGREEMENTS outside of this orchestrated process, as doing so could violate merge consistency across TCA, Receivables, and Projects. For troubleshooting, DBAs inspect the HZ customer merge log and RA_CUSTOMER_MERGES to confirm whether the package executed and completed successfully for a given merge request.