Search Results pn_index_history_headers




Overview
Explore in AI Chat

Overview

The PN_INDEX_HISTORY_HEADERS table is a core data object within the Oracle E-Business Suite Property Manager (PN) module. It serves as the master repository for defining and storing inflation indexes, which are critical financial instruments used to adjust lease payments over time. Its primary role is to account for economic factors like inflation when calculating periodic rent escalations, ensuring lease agreements remain financially relevant. By maintaining a historical record of index definitions, this table provides the foundational data required for automated and accurate rent review calculations, a standard feature in commercial and long-term lease management.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is documented as INDEX_ID. This unique identifier is the anchor for all related index data. Based on its described purpose, the table likely stores header-level attributes for an inflation index, such as the index name, description, source (e.g., Consumer Price Index), frequency of publication, and the base period or value. It acts as the parent record, with detailed periodic values (like monthly or annual index figures) stored in the related child table, PN_INDEX_HISTORY_LINES. The integrity of the INDEX_ID is paramount, as it is referenced by multiple leasing entities to apply the correct inflation adjustments.

Common Use Cases and Queries

The primary use case is the configuration and maintenance of indexes for rent escalation clauses. Administrators create or update index headers here, which are then leveraged during lease abstraction or amendment to associate a specific index with a lease. Common reporting and validation queries involve joining this table to its dependent objects. For instance, to list all leases using a particular index, one would query: SELECT * FROM PN_INDEX_LEASES_ALL pil WHERE pil.INDEX_ID = &target_index_id. Another typical query audits index usage by joining to the lines table to verify historical data completeness: SELECT pihh.*, COUNT(pihl.period_name) FROM PN_INDEX_HISTORY_HEADERS pihh, PN_INDEX_HISTORY_LINES pihl WHERE pihh.INDEX_ID = pihl.INDEX_ID GROUP BY pihh.INDEX_ID, pihh.index_name.

Related Objects

The PN_INDEX_HISTORY_HEADERS table is central to the Property Manager's indexing functionality, with documented foreign key relationships to several key transactional tables. The INDEX_ID column is referenced as follows:

  • PN_INDEX_HISTORY_LINES: The INDEX_ID links to this child table, which stores the detailed time-series values (e.g., monthly figures) for each index header.
  • PN_INDEX_LEASES_ALL: The INDEX_ID in this table associates a specific inflation index with a lease, defining the index used for its rent review calculations.
  • PN_REC_AGR_LINCONST_ALL: The CPI_INDEX column in this table references INDEX_ID, linking index definitions to specific lease agreement line constraints for recovery or CPI-based adjustments.

These relationships ensure data integrity and enable the propagation of index definitions from the master header to all dependent lease and agreement structures.