Search Results pn_index_lease_constraints_all




Overview
Explore in AI Chat

Overview

The table PN_INDEX_LEASE_CONSTRAINTS_ALL is a core data object within the Oracle E-Business Suite Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical function in the management of lease agreements by storing the detailed constraints that govern periodic rent increases. These increases are typically tied to an economic index or a predefined formula. The table operates at the set of books level, as indicated by the "_ALL" suffix, meaning it stores data partitioned by the operating unit, thereby supporting multi-organization architectures. Its primary role is to define the rules and limits, such as minimum or maximum percentage increases or fixed caps, that are applied during the automated or manual calculation of indexed rent adjustments, ensuring increases comply with contractual lease terms.

Key Information Stored

The table's structure is designed to capture the relationship between a lease's indexation clause and its specific limiting conditions. The primary key column, INDEX_CONSTRAINT_ID, uniquely identifies each constraint record. The most significant foreign key is INDEX_LEASE_ID, which links the constraint to its parent indexed lease definition in the PN_INDEX_LEASES_ALL table. While the provided metadata does not list all columns, typical columns in such a constraint table would include CONSTRAINT_TYPE (e.g., 'MAXIMUM', 'MINIMUM', 'CAP'), CONSTRAINT_VALUE (the numerical limit), and potentially EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to manage constraint periods. The table essentially holds the business rules that prevent a calculated index-based rent increase from exceeding or falling below agreed-upon thresholds.

Common Use Cases and Queries

The primary use case is during the rent review or escalation process. When the system calculates a new rent based on an index, it queries this table for applicable constraints to apply the final, compliant adjustment. Common reporting needs include listing all constraints for a specific lease or identifying leases with constraints that may be triggered by a significant index movement. A sample query to retrieve constraint details for a lease would be:

  • SELECT constraint_type, constraint_value
  • FROM pn_index_lease_constraints_all
  • WHERE index_lease_id = (SELECT index_lease_id FROM pn_index_leases_all WHERE lease_id = <lease_id>);

Another critical scenario is data validation, ensuring no lease has contradictory constraints (e.g., a minimum higher than a maximum) through integrity checks.

Related Objects

This table is centrally connected to other key Property Manager tables. Its most direct relationship is with PN_INDEX_LEASES_ALL, via the foreign key on INDEX_LEASE_ID, which defines the base indexed lease terms. The indexed lease itself is linked to a master lease header in PN_LEASES_ALL. Data from this table is likely consumed by the rent increase engine within the PN module, potentially through public APIs or key PL/SQL packages such as PN_INDEX_LEASE_PKG, which handles the creation and processing of indexed leases and their associated constraints. Reports on lease escalations and financial projections will inherently join through these related tables to present a complete picture of rent adjustment rules.