Results for “spread_frequency”

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

Overview

PN_INDEX_LEASES_ALL is a Property Manager (PN) transactional table in Oracle EBS 12.1.1 and 12.2.2 that stores all rent increases associated with an existing lease. Each row represents an indexing arrangement — an escalation, adjustment, or index-based rent increase — defined for a lease, capturing the parameters that govern how, when, and on what basis the rent is adjusted over the lease term. The table is populated and maintained through the Property Manager indexing workflows and supports recurring assessment of lease escalations, including percentage-based, index-based, and step-based increases.

In Data Vault modeling terms, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a surrogate primary key and multiple descriptive and attribute columns tied to a parent lease, which is consistent with a satellite attached to a lease hub rather than a true hub or link. This classification is heuristic and intended as a modeling suggestion, not a definitive architectural designation.

Key Information Stored

The table contains 74 documented columns. The most significant are:

• INDEX_LEASE_ID — surrogate primary key (constraint PN_INDEX_LEASES_PK), uniquely identifying each index lease record.
• INDEX_LEASE_NUMBER — the business-key candidate (unique index PN_INDEX_LEASES_U1), a user-facing reference for the indexing arrangement.
• LEASE_ID — foreign key to PN_LEASES_ALL, linking the escalation to its parent lease.
• INDEX_ID — foreign key to PN_INDEX_HISTORY_HEADERS, identifying the index history header governing the escalation.
• BASE_INDEX_LINE_ID — foreign key to PN_INDEX_HISTORY_LINES, identifying the base index line used for calculation.
• TERM_TEMPLATE_ID — foreign key to PN_TERM_TEMPLATES_ALL, referencing the term template applied.
• COMMENCEMENT_DATE / TERMINATION_DATE — the effective date window for the indexing arrangement.
• ASSESSMENT_DATE / ASSESSMENT_INTERVAL — when and how frequently the escalation is assessed.
• SPREAD_FREQUENCY, BASIS_TYPE, REFERENCE_PERIOD, BASE_YEAR — parameters defining the basis and reference used to compute the increase.
• INCREASE_ON, NEGATIVE_RENT_TYPE, ROUNDING_FLAG — controls governing escalation behavior.
• ORG_ID — the operating unit, supporting multi-org security.
• CURRENCY_CODE, INDEX_MULTIPLIER, AGGREGATION_FLAG, PRORATION_RULE — financial and proration controls.
• Descriptive flexfield columns (ATTRIBUTE1–15) and agreement flexfields (AGREEMENT_ATTRIBUTE1–15) for extensibility.

Common Use Cases and Queries

Typical uses include reporting upcoming rent escalations, auditing indexing terms, and reconciling lease schedules. A common query lists all indexing arrangements for a lease:

• SELECT index_lease_number, commencement_date, termination_date, assessment_interval, basis_type FROM pn_index_leases_all WHERE lease_id = :p_lease_id;
• Join to PN_LEASES_ALL to retrieve lease-level context: SELECT l.lease_number, i.index_lease_number, i.commencement_date FROM pn_index_leases_all i, pn_leases_all l WHERE i.lease_id = l.lease_id;
• Multi-org filtered reporting uses WHERE org_id = :p_org_id.
• Period-driven escalation reports join PN_INDEX_LEASE_PERIODS_ALL on index_lease_id.

Related Objects

The table participates in a well-defined FK network:

• PN_LEASES_ALL — parent lease (join on LEASE_ID).
• PN_INDEX_HISTORY_HEADERS — index headers (join on INDEX_ID).
• PN_INDEX_HISTORY_LINES — index lines (join on BASE_INDEX_LINE_ID).
• PN_TERM_TEMPLATES_ALL — term templates (join on TERM_TEMPLATE_ID).
• PN_INDEX_LEASE_TERMS_ALL — child terms (join on INDEX_LEASE_ID).
• PN_INDEX_LEASE_PERIODS_ALL — escalation periods (join on INDEX_LEASE_ID).
• PN_INDEX_LEASE_CONSTRAINTS_ALL — constraints (join on INDEX_LEASE_ID).
• PN_INDEX_EXCLUDE_TERM_ALL — excluded terms (join on INDEX_LEASE_ID).