Search Results pap_cmerge
Overview
PAP_CMERGE is an Oracle Applications (APPS) schema PL/SQL package that supports customer merge processing within the Projects (PA) module of Oracle E-Business Suite. In EBS, when two customer records are merged through the Oracle Receivables customer merge facility, any project-level data associated with the obsolete (duplicate) customer must be re-pointed to the surviving customer. PAP_CMERGE performs this project-side synchronization work.
The package is the Projects module's subscription handler for the customer merge event flow. Its core purpose is to update project and project-related records so that they reference the surviving customer after a merge. The package is documented in ETRM with object type PACKAGE, owner APPS, and status VALID. It is classified as an "OTHER" API, meaning it is not a published open interface or a standard public API, but an internal engine package supporting the merge workflow. The package contains a single documented procedure, MERGE, and it is referenced by two other packages, indicating it is invoked from higher-level merge orchestration logic.
Key Procedures and Functions
- MERGE — The single documented procedure in PAP_CMERGE. It carries out the customer merge operation for project-related entities. When the Receivables merge process advances to the Projects application, MERGE updates the project records that point to the from-customer so that they now point to the to-customer. It also updates related child records such as project contacts, agreements, and agreements-all records so that the merge result is consistent across PA. No parameter list is documented in the ETRM metadata, and none should be assumed; the procedure operates within the context of the merge session established by the calling merge packages.
The package's dependency listing shows that PAP_CMERGE is referenced by PAP_CMERGE itself (self-reference, consistent with a package body or internal call) and by the packages PAP_CMERGE_BB1 and PAP_CMERGE_BB2, which are the before/after branch body components of the package. The package is also referenced by two other packages in the documented metadata, confirming it is called as part of a larger merge chain rather than invoked directly by end users.
Tables Accessed
The package reads and writes the following objects, referenced through APPS synonyms:
- PA_PROJECT_CUSTOMERS — The primary project-to-customer assignment table; updated so projects are assigned to the surviving customer.
- RA_CUSTOMER_MERGES — The Receivables merge transaction table that defines the from/to customer mapping and merge identifier used to drive the updates.
- HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S — TCA merge audit log tables used to record party-level merge activity.
- PA_AGREEMENTS and PA_AGREEMENTS_ALL — Project agreements that reference customers; updated to preserve agreement integrity after the merge.
- PA_DRAFT_INVOICES and PA_DRAFT_INVOICE_ITEMS — Draft billing documents associated with the merged customer.
- PA_IMPLEMENTATIONS and PA_IMPLEMENTATIONS_ALL — Implementation records that point to customer entities.
- PA_PROJECTS — Project header records tied to the customer.
- PA_PROJECT_CONTACTS — Project contacts linked to the merged customer.
- PA_PROJ_RETN_BILL_RULES and PA_PROJ_RETN_RULES — Project retention billing and retention rules referencing the customer.
- PA_SUMMARY_PROJECT_RETN — Summary project retention records.
Usage Notes
PAP_CMERGE is not a user-invoked API. It is called internally during the Oracle Receivables customer merge concurrent process when the Projects application is among the applications selected for merge processing. In EBS 12.1.1 and 12.2.2, the merge is driven from the Trading Community Architecture (TCA) customer merge function; the Projects portion executes automatically via the merge subscription chain. Developers should not call PAP_CMERGE.MERGE directly from custom code, as the Receivables merge orchestration assumes responsibility for call ordering, validation, and commit boundaries. Customizations that must react to a customer merge in Projects should use standard supported integration points or the corresponding documented public APIs rather than the internal PAP_CMERGE package.
-
PACKAGE: APPS.PAP_CMERGE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE
12.1.1
-
PACKAGE: APPS.PAP_CMERGE
12.2.2
-
PACKAGE BODY: APPS.PAP_CMERGE
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE, status:VALID,
-
PACKAGE BODY: APPS.PAP_CMERGE
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE_BB2
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE_BB2, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE_BB1
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE_BB1, status:VALID,
-
SYNONYM: APPS.PA_PROJECT_CUSTOMERS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECT_CUSTOMERS, status:VALID,
-
SYNONYM: APPS.PA_PROJ_RETN_RULES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_PROJ_RETN_RULES, status:VALID,
-
SYNONYM: APPS.PA_PROJ_RETN_BILL_RULES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_PROJ_RETN_BILL_RULES, status:VALID,
-
PACKAGE BODY: APPS.PAP_CMERGE_BB2
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE_BB2, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE_BB1
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE_BB1, status:VALID,
-
PACKAGE: APPS.PAP_CMERGE_BB2
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PAP_CMERGE_BB2, status:VALID,
-
SYNONYM: APPS.PA_PROJECT_CUSTOMERS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECT_CUSTOMERS, status:VALID,
-
SYNONYM: APPS.PA_PROJ_RETN_BILL_RULES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_PROJ_RETN_BILL_RULES, status:VALID,
-
SYNONYM: APPS.PA_SUMMARY_PROJECT_RETN
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_SUMMARY_PROJECT_RETN, status:VALID,
-
PACKAGE: APPS.ARP_CMERGE_MASTER
12.1.1
owner:APPS, object_type:PACKAGE, object_name:ARP_CMERGE_MASTER, status:VALID,
-
PACKAGE: APPS.ARP_CMERGE_MASTER
12.2.2
owner:APPS, object_type:PACKAGE, object_name:ARP_CMERGE_MASTER, status:VALID,
-
SYNONYM: APPS.PA_SUMMARY_PROJECT_RETN
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_SUMMARY_PROJECT_RETN, status:VALID,
-
SYNONYM: APPS.PA_PROJ_RETN_RULES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_PROJ_RETN_RULES, status:VALID,
-
SYNONYM: APPS.RA_CUSTOMER_MERGES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:RA_CUSTOMER_MERGES, status:VALID,
-
PACKAGE BODY: APPS.PAP_CMERGE_BB1
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE_BB1, status:VALID,
-
PACKAGE BODY: APPS.PAP_CMERGE_BB2
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE_BB2, status:VALID,
-
PACKAGE BODY: APPS.PAP_CMERGE_BB1
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PAP_CMERGE_BB1, status:VALID,
-
SYNONYM: APPS.PA_AGREEMENTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_AGREEMENTS, status:VALID,
-
SYNONYM: APPS.PA_AGREEMENTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_AGREEMENTS, status:VALID,
-
SYNONYM: APPS.RA_CUSTOMER_MERGES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:RA_CUSTOMER_MERGES, status:VALID,
-
SYNONYM: APPS.PA_PROJECT_CONTACTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECT_CONTACTS, status:VALID,
-
SYNONYM: APPS.PA_PROJECT_CONTACTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECT_CONTACTS, status:VALID,
-
SYNONYM: APPS.PA_DRAFT_INVOICES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_DRAFT_INVOICES, status:VALID,
-
SYNONYM: APPS.PA_AGREEMENTS_ALL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_AGREEMENTS_ALL, status:VALID,
-
SYNONYM: APPS.HZ_CUSTOMER_MERGE_LOG_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:HZ_CUSTOMER_MERGE_LOG_S, status:VALID,
-
SYNONYM: APPS.HZ_CUSTOMER_MERGE_LOG_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:HZ_CUSTOMER_MERGE_LOG_S, status:VALID,
-
SYNONYM: APPS.PA_DRAFT_INVOICES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_DRAFT_INVOICES, status:VALID,
-
SYNONYM: APPS.PA_AGREEMENTS_ALL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_AGREEMENTS_ALL, status:VALID,
-
SYNONYM: APPS.HZ_CUSTOMER_MERGE_LOG
12.1.1
owner:APPS, object_type:SYNONYM, object_name:HZ_CUSTOMER_MERGE_LOG, status:VALID,
-
SYNONYM: APPS.HZ_CUSTOMER_MERGE_LOG
12.2.2
owner:APPS, object_type:SYNONYM, object_name:HZ_CUSTOMER_MERGE_LOG, status:VALID,
-
SYNONYM: APPS.PA_DRAFT_INVOICE_ITEMS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_DRAFT_INVOICE_ITEMS, status:VALID,
-
SYNONYM: APPS.PA_DRAFT_INVOICE_ITEMS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_DRAFT_INVOICE_ITEMS, status:VALID,
-
PACKAGE: APPS.ARP_MESSAGE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:ARP_MESSAGE, status:VALID,
-
PACKAGE: APPS.ARP_MESSAGE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:ARP_MESSAGE, status:VALID,
-
PACKAGE: APPS.HZ_UTILITY_PUB
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HZ_UTILITY_PUB, status:VALID,
-
PACKAGE: APPS.HZ_UTILITY_PUB
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HZ_UTILITY_PUB, status:VALID,
-
SYNONYM: APPS.PA_IMPLEMENTATIONS_ALL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_IMPLEMENTATIONS_ALL, status:VALID,
-
SYNONYM: APPS.PA_IMPLEMENTATIONS_ALL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_IMPLEMENTATIONS_ALL, status:VALID,
-
SYNONYM: APPS.PA_PROJECTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECTS, status:VALID,
-
SYNONYM: APPS.PA_PROJECTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_PROJECTS, status:VALID,
-
SYNONYM: APPS.PA_IMPLEMENTATIONS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PA_IMPLEMENTATIONS, status:VALID,
-
SYNONYM: APPS.PA_IMPLEMENTATIONS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PA_IMPLEMENTATIONS, status:VALID,