Search Results req_id

Overview

PNP_CMERGE is a PL/SQL package in the Oracle E-Business Suite Property Manager (PN) module that supports the customer merge process for property management data. In Oracle EBS, when two customer records are merged in Oracle Receivables through the Customer Merge concurrent program, related transactional and reference data across multiple modules must be reassigned from the duplicate (source) customer to the surviving (target) customer. PNP_CMERGE provides the property-specific portion of that merge logic. The package is defined with AUTHID CURRENT_USER and is owned by APPS, with a documented API classification of OTHER, indicating it is an internal (non-public) utility rather than a formally published open interface or public API. Its procedures collectively update the property management tables that carry a customer reference so that leases, tenancies, payment terms, payment items, receivables agreements, and related history records point to the correct customer after a merge.

Key Procedures and Functions

The package exposes twelve documented procedures, each accepting a request identifier, a set number, and a process mode parameter. The common signature reflects the fact that these are merge driver routines that operate within the scope of a single customer merge set.

• MERGE — The primary entry point that orchestrates the customer merge for property data. It coordinates the subordinate update procedures for a given request identifier and set number.
• UPDATE_LEASES — Reassigns lease records to the surviving customer.
• UPDATE_TENANCIES — Updates tenancy records affected by the merge.
• UPDATE_TENANCIES_HISTORY — Maintains historical tenancy rows so that audit trails remain consistent after reassignment.
• UPDATE_TERM_TEMPLATES — Adjusts term templates tied to the merged customer or set.
• UPDATE_PAYMENT_TERMS — Reassigns payment terms records.
• UPDATE_PAYMENT_ITEMS — Updates payment items associated with the affected customer.
• UPDATE_REC_AGREEMENTS — Reassigns receivables agreements.
• UPDATE_REC_ARCL_DTLN — Updates receivables accounting detail lines.
• UPDATE_REC_EXPCL_DTLN — Updates receivables expense detail lines.
• UPDATE_REC_PERIOD_LINES — Updates receivables period lines.
• UPDATE_SPACE_ASSIGN_CUST — Reassigns space assignment customer records.

Tables Accessed

The package operates on the core Property Manager transaction tables through APPS synonyms, including PN_LEASES, PN_TENANCIES, PN_TENANCIES_HISTORY, PN_TERM_TEMPLATES, PN_PAYMENT_TERMS, PN_PAYMENT_ITEMS, PN_REC_AGREEMENTS, PN_REC_ARCL_DTLLN, PN_REC_EXPCL_DTLLN, PN_REC_PERIOD_LINES, and PN_SPACE_ASSIGN_CUST. These are the tables the individual update procedures modify to reflect the merged customer. The package also references the shared customer merge infrastructure tables HZ_CUSTOMER_MERGE_LOG, HZ_CUSTOMER_MERGE_LOG_S, RA_CUSTOMER_MERGES, and RA_CUSTOMER_MERGE_HEADERS. The HZ and RA tables provide the merge request context and logging used to track which source and target customers are involved and to record merge status.

Usage Notes

PNP_CMERGE is not a public API and should not be called directly by custom code unless invoked as part of a supported merge workflow. It is typically driven by the Oracle Receivables Customer Merge process, which passes the request identifier and set number to the module-specific merge handlers. The process_mode parameter allows the routine to run in different modes (for example, a report or preview mode versus an actual update mode), enabling validation before committing changes. Because the package is owned by APPS and uses AUTHID CURRENT_USER, execution privileges and synonym resolution depend on the calling schema. Customizations should avoid modifying this package and instead integrate through the standard Customer Merge framework. The package is referenced by zero other documented packages, confirming its role as a leaf-level utility invoked by higher-level merge orchestration.