Results for “pn_adjustment_summaries_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_RETRO_ADJUSTMENT_PKG is a PL/SQL package body owned by the APPS schema that supports the retroactive adjustment processing within the Oracle E-Business Suite Property Manager (PN) module. Its principal business function is to evaluate lease payment schedules, identify the impact of lease changes, and generate the retroactive adjustment records required to reconcile payment terms after an amendment, escalation, or term modification has been applied. The package therefore sits at the intersection of lease change management and payment schedule recalculation, ensuring that amounts previously billed or scheduled under superseded terms are corrected in accordance with the revised lease agreement.

In the 12.1.1 and 12.2.2 releases, retroactive adjustment processing is essential for maintaining the accuracy of lease accounting and for feeding downstream receivables or payables activities with corrected amounts. The package operates against both base tables and their corresponding _ALL and _S (sequence-generated primary key) variants, reflecting the multi-org and surrogate-key architectures used throughout ETRM. The ETRM metadata classifies this package under API classification OTHER, indicating it is an internal processing package rather than a formally published public API, though it remains callable from concurrent processing and custom extensions.

Key Procedures and Functions

The documented package exposes four procedures or functions, each addressing a distinct phase of retroactive adjustment processing:

• CREATE_RETRO_ADJUSTMENTS — The primary driver that builds the retroactive adjustment records. It examines the relevant lease and payment schedule data and writes adjustment summaries and details reflecting the difference between original and revised terms.
• FIND_SCHEDULE — A lookup routine that locates the applicable payment schedule for a given lease or adjustment context, providing the reference point against which retroactive differences are computed.
• CREATE_VIRTUAL_SCHEDULES — Generates temporary, in-memory or transient schedule representations used to model what the schedule should have been under the amended terms, without prematurely committing persistent schedule rows.
• CLEANUP_SCHEDULES — Removes the virtual or transient schedule artifacts once the adjustment calculation is complete, preserving the integrity of the permanent schedule tables.

No parameter lists are reproduced here, as the ETRM metadata documents procedure names and purposes only. The sequence suggests a workflow of locate, model, create, and clean up.

Tables Accessed

The package references a comprehensive set of Property Manager tables via APPS synonyms. The adjustment output is written to PN_ADJUSTMENT_SUMMARIES and PN_ADJUSTMENT_DETAILS, with their _S variants used to obtain sequence-generated primary keys. The source lease context is drawn from PN_LEASES, PN_LEASES_ALL, and PN_LEASE_CHANGES, which record the amendments triggering retroactive processing. Payment data is read from PN_PAYMENT_SCHEDULES, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_ITEMS, PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_ITEMS_S, PN_PAYMENT_TERMS, PN_PAYMENT_TERMS_ALL, and PN_PAYMENT_TERMS_HISTORY. The package also depends on PNT_PAYMENT_SCHEDULES_PKG, PN_SCHEDULES_ITEMS, PN_MO_CACHE_UTILS, PNP_DEBUG_PKG, FND_CURRENCY, and FND_GLOBAL for schedule logic, multi-org caching, debugging, currency conversion, and session context.

Usage Notes

This package is typically invoked indirectly through Property Manager concurrent programs and forms that manage lease changes and payment term revisions, rather than being called directly by end users. Because it is not a formally published API and is not referenced by any other database object, Oracle does not guarantee its interface across releases; custom code should avoid calling it directly. Where adjustments must be reprocessed, the package is re-executed by the standard retroactive adjustment flow, which internally sequences FIND_SCHEDULE, CREATE_VIRTUAL_SCHEDULES, CREATE_RETRO_ADJUSTMENTS, and CLEANUP_SCHEDULES. The presence of PNP_DEBUG_PKG dependency permits diagnostic tracing during troubleshooting.