Search Results put_output

Overview

APPS.PN_INDEX_RENT_PERIODS_PKG is a PL/SQL package body within the Oracle Property Manager (PN) module of Oracle E-Business Suite, a component of the ETRM (Enterprise Asset and Transaction Management) family. Its stated purpose is to maintain index rent periods — the recurring rental periods generated for index-based leases where rent escalates according to an index (such as CPI). The package encapsulates the business logic that drives period generation, basis data maintenance, payment term amendment processing, and the handling of critical lease lifecycle events such as terminations, term date changes, and mark-to-market adjustments. Because it is tightly coupled to payment terms, payment schedules, and lease change records, it functions as the central programmatic engine behind index rent recalculation and regeneration in Oracle Property Manager. The package body header identifies a long maintenance history beginning in 2001, reflecting its role as a foundational utility for lease financial calculations.

Key Procedures and Functions

The package exposes eleven documented procedures and functions covering the full lifecycle of index rent periods:

• GENERATE_PERIODS_BATCH — Generates index rent periods in bulk for a specified index lease, historically invoked from concurrent processing.
• GENERATE_PERIODS — Generates the index rent periods for a single lease context.
• PRINT_BASIS_PERIODS — Produces output of the basis periods, supporting the "put_output" style reporting used to review generated basis data.
• UNDO_PERIODS — Reverses previously generated index rent periods, allowing recalculation after corrections.
• PROCESS_NEW_TERMINATION_DATE — Adjusts index rent periods when a lease termination date is introduced or changed.
• GENERATE_BASIS_DATA_CHECK — Validates whether basis data exists or is current before generation proceeds.
• PROCESS_MAIN_LEASE_TERM_DATE — Handles changes to the main lease term date, including profile-option-driven logic that governs whether an index rent term is extended.
• DELETE_PERIODS — Removes index rent periods, including associated rows in lease terms, with an 'ALL' condition added for broader deletion.
• PROCESS_PAYMENT_TERM_AMENDMENT — Processes amendments to payment terms, honoring the retain_initial_basis_flag so that the initial basis is overwritten only when the flag is not set.
• HANDLE_MTM_ACT — Manages mark-to-market (MTM) activity affecting index rent periods.
• HANDLE_TERM_DATE_CHANGE — Responds to term date changes and re-drives period recalculations accordingly.

Tables Accessed

The package reads and writes a broad set of Property Manager tables through APPS synonyms:

• PN_INDEX_LEASE_PERIODS_ALL, PN_INDEX_LEASE_TERMS_ALL, PN_INDEX_EXCLUDE_TERM_ALL — the core index rent period and term records created, updated, and deleted by generation and undo logic.
• PN_INDEX_LEASES, PN_INDEX_LEASES_ALL, PN_INDEX_LEASE_CONSTRAINTS_ALL — lease header and constraint data governing period generation.
• PN_PAYMENT_TERMS, PN_PAYMENT_TERMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_ITEMS_ALL — payment term and schedule records amended and recalculated by PROCESS_PAYMENT_TERM_AMENDMENT.
• PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_LEASE_DETAILS_HISTORY, PN_LEASE_CHANGES_ALL — lease details, historical snapshots, and change tracking used during term date and termination processing.
• PN_DISTRIBUTIONS_ALL — distribution records referenced when validating or recalculating financial impact.

Usage Notes

PN_INDEX_RENT_PERIODS_PKG is typically invoked indirectly rather than called by end users. It is referenced by three other packages, and its procedures are triggered from Oracle Property Manager forms (such as lease and payment term maintenance) and from concurrent programs that batch-generate index rent periods. Custom extensions should treat it as an internal, non-public API and avoid direct modification of the underlying tables, since the package enforces the basis-data and payment-term consistency rules. When diagnosing issues around period generation output, PRINT_BASIS_PERIODS and GENERATE_BASIS_DATA_CHECK are the preferred entry points for verifying basis data before regeneration, and UNDO_PERIODS should precede any corrective regeneration.