Search Results pn_rec_agreements

Overview

PNP_CMERGE is an Oracle E-Business Suite PL/SQL package body in the APPS schema that supports customer merge processing within the Oracle Property Manager (PN) module. Property Manager manages real estate leases, tenancies, payment terms, and receivables-related billing for leased and owned properties. When a customer or party record in Oracle Receivables or Oracle Trading Community Architecture (TCA) is merged into another customer record, all dependent transactional and reference data owned by the old (source) customer must be repointed to the new (target) customer. PNP_CMERGE exists to perform that repointing for Property Manager's lease, tenancy, payment, and receivables-interface data.

The package is classified as an "OTHER" API in the ETRM 12.2.2 metadata, meaning it is invoked internally by the customer merge framework rather than being a published, customer-facing API. Its dependencies on ARP_STANDARD, ARP_MESSAGE, HZ_ACCT_MERGE_UTIL, HZ_UTILITY_PUB, FND_PROFILE, and the RA_CUSTOMER_MERGE_* tables confirm that it participates in the standard Receivables/TCA customer merge and party merge flows.

Key Procedures and Functions

The package exposes twelve documented program units. The primary entry point is MERGE, which orchestrates the overall customer merge for Property Manager data. It is supported by a series of targeted update procedures, each responsible for repointing a specific category of Property Manager records:

• MERGE — The main driver procedure. It coordinates the invocation of the individual UPDATE_* routines that follow.
• UPDATE_LEASES — Repoints lease records (PN_LEASES) from the source customer to the target customer.
• UPDATE_TENANCIES — Updates active tenancy records (PN_TENANCIES) to reflect the surviving customer.
• UPDATE_TENANCIES_HISTORY — Applies the same customer reassignment to historical tenancy rows (PN_TENANCIES_HISTORY).
• UPDATE_TERM_TEMPLATES — Reassigns term template records (PN_TERM_TEMPLATES) tied to the merging customer.
• UPDATE_PAYMENT_TERMS — Updates payment term definitions (PN_PAYMENT_TERMS).
• UPDATE_PAYMENT_ITEMS — Updates payment item records (PN_PAYMENT_ITEMS).
• UPDATE_REC_AGREEMENTS — Repoints receivable agreements (PN_REC_AGREEMENTS).
• UPDATE_REC_ARCL_DTLN — Updates receivables clearing detail lines (PN_REC_ARCL_DTLLN).
• UPDATE_REC_EXPCL_DTLN — Updates receivables expense clearing detail lines (PN_REC_EXPCL_DTLLN).
• UPDATE_REC_PERIOD_LINES — Updates receivables period lines (PN_REC_PERIOD_LINES), the object most commonly surfaced in searches for "pn_rec_period_lines."
• UPDATE_SPACE_ASSIGN_CUST — Reassigns customer space assignment records (PN_SPACE_ASSIGN_CUST).

Tables Accessed

The documented tables fall into three groups. The transactional Property Manager tables — 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 — hold the records whose customer identifiers are repointed during a merge. The receivables merge framework tables RA_CUSTOMER_MERGES and RA_CUSTOMER_MERGE_HEADERS provide the merge request identifiers and source/target customer context. The TCA logging tables HZ_CUSTOMER_MERGE_LOG and HZ_CUSTOMER_MERGE_LOG_S capture the merge audit trail. The package also references PLITBLM, the standard PL/SQL table-handling utility package in SYS.

Usage Notes

PNP_CMERGE is not intended for direct invocation by end users or custom code. It is called programmatically by the Oracle Receivables/TCA customer merge framework when Property Manager data must be reconciled as part of a customer or party merge. The merge framework determines which package handles which product's tables, then calls the appropriate MERGE entry point. Because PNP_CMERGE is referenced by zero other database objects, it is a leaf-level consumer invoked dynamically rather than a reusable dependency. Developers investigating a specific table such as PN_REC_PERIOD_LINES should trace the corresponding UPDATE_REC_PERIOD_LINES procedure, which is the documented unit responsible for that table.