Results for “pn_index_exclude_term_all”

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

Overview

The PN_INDEX_EXCLUDE_TERM_ALL table is a Property Manager (PN) module data object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the payment terms that must be excluded from the calculation of a rent increase (indexation) on a lease. When Oracle Property Manager performs index-based rent escalation, it evaluates the payment terms attached to a lease; any term recorded in this table is explicitly withheld from that calculation, allowing the escalation to be applied selectively rather than across the full rent schedule.

The table is owned by the PN schema and is reported as VALID in the ETRM dictionary, with a documented physical schema of 10 columns. Following the heuristic Data Vault classification derived from the foreign-key structure, the object is a link: it resolves a many-to-many association between index leases and payment terms, rather than acting as a descriptive hub or satellite. Tables of this type typically carry audit and multi-organization columns alongside the two foreign keys that define the relationship, and PN_INDEX_EXCLUDE_TERM_ALL follows that pattern.

Key Information Stored

The table is anchored by the surrogate primary key INDEX_EXCLUDE_TERM_ID, enforced through the constraint PN_INDEX_EXCLUDE_TERM_PK and mirrored by the unique index PN_INDEX_EXCLUDE_TERM_U1. Since the unique index covers the same column as the primary key, no separate business-key column is documented; the identifier functions as both the technical and the candidate key.

• INDEX_EXCLUDE_TERM_ID — Surrogate primary key for each exclusion record.
• INDEX_LEASE_ID — Foreign key to PN_INDEX_LEASES_ALL; identifies the index lease whose escalation calculation is affected.
• PAYMENT_TERM_ID — Foreign key to PN_PAYMENT_TERMS_ALL; identifies the payment term being excluded from the escalation.
• INCLUDE_EXCLUDE_FLAG — Control flag indicating whether the referenced term is included in or excluded from the index calculation.
• ORG_ID — Operating unit / organization identifier, enabling multi-org data partitioning and security.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row, when, and through which login session.

The pairing of INDEX_LEASE_ID and PAYMENT_TERM_ID is the functional core of the row: it states that for a given lease, a given payment term is to be treated according to the INCLUDE_EXCLUDE_FLAG during rent increase processing.

Common Use Cases and Queries

The primary use case is administration and verification of indexation exclusions. Property managers configure exclusions so that items such as CAM, tax, or one-off charges linked to payment terms are not escalated with the base rent. Reporting queries typically join the table back to its parents to present readable lease and term descriptions.

• Listing all exclusions for a lease:

  SELECT e.index_exclude_term_id, e.payment_term_id, e.include_exclude_flag
  FROM   pn_index_exclude_term_all e
  WHERE  e.index_lease_id = :lease_id
  AND    e.org_id = :org_id;

• Identifying which payment terms are withheld from escalation by joining to PN_PAYMENT_TERMS_ALL on PAYMENT_TERM_ID.
• Auditing configuration changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who modified exclusions.
• Reconciliation reporting across operating units using ORG_ID to compare exclusion policies between organizations.

Related Objects

Because the table is a link, its significance derives almost entirely from the objects it connects and the constraints that govern them.

• PN_INDEX_LEASES_ALL — Parent of the INDEX_LEASE_ID foreign key; holds the index lease definition whose rent increase calculation honors these exclusions.
• PN_PAYMENT_TERMS_ALL — Parent of the PAYMENT_TERM_ID foreign key; holds the payment terms available for exclusion.
• PN_INDEX_EXCLUDE_TERM_PK — Primary key constraint on INDEX_EXCLUDE_TERM_ID.
• PN_INDEX_EXCLUDE_TERM_U1 — Unique index on INDEX_EXCLUDE_TERM_ID.

Queries against this table should always be scoped by ORG_ID and joined to the parent lease and payment term tables to supply the descriptive context absent from the link itself. No additional views, APIs, or concurrent programs are documented in the supplied metadata; the practical dependency surface is therefore the two parent tables plus the key constraints listed above.