Search Results index_period_id




Overview
Explore in AI Chat

Overview

The PN_INDEX_LEASE_PERIODS_ALL table is a core data repository within the Oracle E-Business Suite Property Manager (PN) module. It is designed to store the complete transactional history and configuration for all rent increase periods associated with indexed leases. An indexed lease is a contractual agreement where the rental payments are periodically adjusted based on a predefined external index, such as the Consumer Price Index (CPI). This table is central to the automated calculation and tracking of these rent escalations over the life of a lease. As an "ALL" table, it is partitioned by the operating unit, enabling the support of multiple organizations within a single installation.

Key Information Stored

The table's primary purpose is to define the chronological periods for which a specific rent index adjustment is effective. Its structure links the lease, the index value, and the resulting financial terms. The most critical columns include INDEX_PERIOD_ID (the primary key), and INDEX_LEASE_ID, which foreign keys to PN_INDEX_LEASES_ALL to identify the parent indexed lease. The table tracks the specific index values used for calculations through CURRENT_INDEX_LINE_ID and PREVIOUS_INDEX_LINE_ID, which reference PN_INDEX_HISTORY_LINES. This allows the system to determine the percentage change between two index points. Additional columns typically store the effective start and end dates of the index period, the calculated rent adjustment percentage, and audit information such as creation date and last update date.

Common Use Cases and Queries

This table is essential for generating rent escalation invoices, historical lease analysis, and audit reports. A common business use case is reviewing all pending or future rent increases for a portfolio of properties. A typical query might join this table to the lease and index tables to list upcoming adjustments. For example:

  • SELECT ilp.index_lease_id, ilp.period_start_date, ilp.period_end_date, ihl.index_value FROM pn_index_lease_periods_all ilp, pn_index_history_lines ihl WHERE ilp.current_index_line_id = ihl.index_history_line_id AND ilp.period_start_date > SYSDATE ORDER BY ilp.period_start_date;

From a support perspective, troubleshooting a miscalculated rent charge often involves tracing the data flow from the index source through PN_INDEX_HISTORY_LINES to the period defined in this table, and finally to the generated term in PN_INDEX_LEASE_TERMS_ALL.

Related Objects

PN_INDEX_LEASE_PERIODS_ALL sits at the heart of the rent indexing subsystem. Its primary relationship is with PN_INDEX_LEASES_ALL, which defines the master indexed lease agreement. It is directly dependent on PN_INDEX_HISTORY_LINES for the source index values used in calculations. Crucially, it is the parent table for PN_INDEX_LEASE_TERMS_ALL, which stores the actual financial terms (e.g., revised rent amount) generated as a result of the index period's calculation. This table is also referenced by various Property Manager application programming interfaces (APIs) and key reports that manage the lease indexation lifecycle.