Search Results pap_cmerge_bb1




Overview
Explore in AI Chat

Overview

PAP_CMERGE_BB1 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name follows the concurrent manager merge naming convention used throughout the Oracle Applications codebase: the PAP prefix identifies it as belonging to the Oracle Projects (PA) product family, CMERGE denotes customer merge processing, and the BB1 suffix identifies it as one of the sequential processing units into which Oracle splits a larger bulk operation so that work can be parallelized across concurrent manager workers. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve under the privileges of the calling schema rather than the definer, which is the standard pattern for Oracle Applications worker packages invoked from a concurrent program.

The business function of PAP_CMERGE_BB1 is to support the customer merge process as it applies to Oracle Projects. When two customer or trading partner records are merged in Oracle Receivables or Oracle Receivables' shared trading community model, related project agreements must be repointed from the surviving (duplicate) customer to the surviving (target) customer. PAP_CMERGE_BB1 performs the Projects-side portion of that reconciliation for the subset of records assigned to it by the driving concurrent request.

The header comment shows a revision of 115.1 dated 99/07/16 with the porting ship designation, indicating the file has been carried forward with minimal change across many release levels and remains present, undocumented externally, in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes a single documented procedure:

  • MERGE_PA_AGREEMENTS — The worker entry point for merging project agreements. It is called by the customer merge driver, receiving a concurrent request identifier and a set number so that each invocation processes only its assigned slice of the affected agreements. Its purpose is to identify project agreements tied to the customer being merged away and update them to reference the surviving customer, thereby preserving agreement integrity after the merge.

No other procedures or functions are documented for this package. Parameter lists beyond the two documented arguments are not published in the metadata and should not be assumed.

Tables Accessed

The package references the following tables through APPS synonyms:

  • PA_AGREEMENTS — The principal table acted upon. Rows associated with the duplicate customer are located and updated so that the agreement(s) survive the merge under the correct customer reference.
  • RA_CUSTOMER_MERGES — The Receivables customer merge header table. It supplies and records the merge relationship between the duplicate and surviving customers and tracks merge request status.
  • HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — The Trading Community Architecture merge audit and its sequence. These record the party-level before-and-after identifiers created by the merge, giving PAP_CMERGE_BB1 the mapping it needs and providing an audit trail of the referral performed on the Projects side.

Usage Notes

PAP_CMERGE_BB1 is not intended for direct invocation by end users. It is normally called only from the Oracle Receivables customer merge concurrent program, which schedules worker packages such as this one to process the merge in parallel sets. The request identifier and set number passed to MERGE_PA_AGREEMENTS are supplied by that driver rather than entered manually.

Because it is an internal worker rather than a published API, no supported interface is documented, and customization should not call it directly. It is referenced by one other package in the ETRM repository, reflecting its role within the merge call graph. In 12.1.1 and 12.2.2 the package behaves the same way: it is invoked during customer merge processing when project agreements exist for the customer being merged, and its activity is visible through the TCA merge logs and the resulting state of PA_AGREEMENTS.