Results for “maximum_percent”

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

Overview

PN_INDEX_LEASE_CONSTRAINTS_ALL is a Property Manager (PN) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the constraints governing rent increases applied to indexed lease agreements. In lease administration, indexed leases tie periodic rent adjustments to an external index — commonly a consumer price index — and the clauses negotiated between landlord and tenant typically cap, floor, or otherwise bound the resulting escalation. This table is the repository for those negotiated boundaries at the individual index-lease level. Each row records the scope of a constraint together with its permitted minimum and maximum values expressed either as absolute monetary amounts or as percentages, allowing the rent escalation engine to apply guard rails during periodic index revaluation.

The ETRM documentation identifies the table as owned by the PN schema with VALID status and 29 documented columns. A heuristic Data Vault classification mined from the foreign-key structure suggests this object is satellite-leaning: it carries descriptive constraint attributes that describe a parent business entity rather than acting as a hub of independent business keys or a pure link between two hubs. In modeling terms, it is best treated as a dependent descriptor table whose grain is the individual index-lease constraint record.

Key Information Stored

The primary key of the table is PN_INDEX_LEASE_CONSTRAINTS_PK, defined on the surrogate column INDEX_CONSTRAINT_ID. A unique index, PN_INDEX_LEASE_CONSTRAINTS_U1, also exists on INDEX_CONSTRAINT_ID, making that column the documented business-key candidate for the row.

• INDEX_CONSTRAINT_ID — surrogate primary key uniquely identifying each constraint record.
• INDEX_LEASE_ID — foreign key to PN_INDEX_LEASES_ALL, linking the constraint to its parent indexed lease.
• SCOPE — indicates the scope or level at which the constraint applies.
• MINIMUM_AMOUNT and MAXIMUM_AMOUNT — absolute floor and ceiling values for the rent increase.
• MINIMUM_PERCENT and MAXIMUM_PERCENT — percentage-based floor and ceiling for the rent increase.
• ORG_ID — operating unit identifier supporting multi-org partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record provenance.

Common Use Cases and Queries

The principal use case is determining the effective bounds on a rent escalation. Lease administrators and billing processes query the constraints for a given index lease to decide whether a calculated index-based increase must be capped or floored. A representative query joins the constraint to its parent lease:

• SELECT c.INDEX_CONSTRAINT_ID, c.SCOPE, c.MINIMUM_PERCENT, c.MAXIMUM_PERCENT, c.MINIMUM_AMOUNT, c.MAXIMUM_AMOUNT FROM PN_INDEX_LEASE_CONSTRAINTS_ALL c WHERE c.INDEX_LEASE_ID = :lease_id AND c.ORG_ID = :org_id;
• Reporting on leases whose percentage ceiling falls below a threshold, to flag contracts requiring renegotiation.
• Audit extracts comparing minimum and maximum amounts against actual billed escalations to detect over- or under-charging.
• Flexfield-based reporting using ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for client-specific constraint classifications.

Because constraints are stored on the _ALL table, queries must always filter by ORG_ID to respect operating unit security.

Related Objects

The most significant related object is the parent lease table referenced by the documented foreign key:

• PN_INDEX_LEASES_ALL — joined via PN_INDEX_LEASE_CONSTRAINTS_ALL.INDEX_LEASE_ID = PN_INDEX_LEASES_ALL.INDEX_LEASE_ID; the parent indexed lease record.
• PN_INDEX_LEASE_CONSTRAINTS_PK — the primary key constraint enforcing row uniqueness on INDEX_CONSTRAINT_ID.
• PN_INDEX_LEASE_CONSTRAINTS_U1 — the unique index on INDEX_CONSTRAINT_ID serving as the business-key candidate.
• Property Manager index and escalation processing logic, which consumes these constraints during rent revaluation.
• Standard EBS multi-org views layered over the _ALL table for operating-unit-scoped access.

Together these objects form the lease-index constraint model, with PN_INDEX_LEASES_ALL as the parent entity and PN_INDEX_LEASE_CONSTRAINTS_ALL supplying the bound attributes applied to each rent increase.