Results for “aggregation_flag”

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

Overview

PN_INDEX_LEASES_V is a form view owned by the APPS schema in Oracle E-Business Suite, validated and active in both 12.1.1 and 12.2.2. It belongs to the PN – Property Manager product and functions as the presentation-layer view for the PN_INDEX_LEASES_ALL table. Its principal role is to supply the Oracle Forms data block underlying the Index Leases window, and it is equally serviceable for reporting and integration queries that require index-lease attributes joined with their parent lease, location, and index history information.

Because it is a view rather than a table, it carries no storage of its own; all data is resolved at query time from the synonyms and views on which it is defined. This makes it a convenient read-only access point that hides the multi-table join logic from report writers and interface developers. The view is a critical object for the user search term base_year, since BASE_YEAR is one of the columns it directly exposes from PN_INDEX_LEASES_ALL.

Underlying Base Objects

The documented referenced objects are FND_GLOBAL (package), FND_LOOKUPS (view), FND_USER (synonym), PN_INDEX_HISTORY_HEADERS (synonym), PN_INDEX_LEASES (synonym), PN_LEASES_ALL (synonym), PN_LEASE_DETAILS_ALL (synonym), and PN_LOCATIONS (synonym). The view is built primarily over PN_INDEX_LEASES_ALL (aliased PIL in the view text), joined to PN_LEASES_ALL (PL) for lease identity, PN_LEASE_DETAILS_ALL (PLD) for commencement and termination dates, PN_INDEX_HISTORY_HEADERS (PIHH) for the index type name, and PN_LOCATIONS (PLO) through a scalar subquery that returns a single LOCATION_CODE using a ROWNUM = 1 restriction. FND_USER (FU) supplies the user name and ID of the person who abstracted the index lease, while FND_LOOKUPS (PTLOOK) translates the INCREASE_ON code into its MEANING. FND_GLOBAL is referenced for session context, typically ORG_ID, supporting Multi-Org security.

Key Columns

• ROW_ID – the ROWID of the PN_INDEX_LEASES_ALL row, used by Oracle Forms for row identification and locking.
• ORG_ID – operating unit identifier, enabling Multi-Org filtering.
• LEASE_ID, LEASE_NAME, LEASE_NUM – parent lease keys and descriptive identifiers from PN_LEASES_ALL.
• INDEX_LEASE_ID, INDEX_LEASE_NUMBER – the index lease primary key and user-facing number.
• INDEX_ID, INDEX_TYPE – index history header key and its name.
• BASE_YEAR – the base reference year used in index escalation calculations; central to the user's search.
• BASE_INDEX, INITIAL_BASIS, BASIS_PERCENT_DEFAULT, BASIS_TYPE, REFERENCE_PERIOD – parameters controlling how index adjustments are computed.
• ASSESSMENT_DATE, ASSESSMENT_INTERVAL, SPREAD_FREQUENCY, INCREASE_ON, INCREASE_ON_TYPE – scheduling and lookup-decoded escalation behavior.
• INDEX_COMMENCEMENT_DATE, INDEX_TERMINATION_DATE – validity window of the index lease term.
• LEASED_AREA, ROUNDING_FLAG, AGGREGATION_FLAG, GROSS_FLAG, NEGATIVE_RENT_TYPE, CARRY_FORWARD_FLAG – calculation and rounding controls.
• CURRENCY_CODE, LOCATION_ID, LOCATION_CODE, TERM_TEMPLATE_ID – currency and location context.
• USER_RESPONSIBLE, ABSTRACTED_BY – audit attribution via FND_USER.
• ATTRIBUTE1–15, AGREEMENT_ATTRIBUTE1–15, AGREEMENT_CATEGORY – descriptive flexfield and agreement flexfield segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting all index leases that reference a specific base year, reconciling index escalation terms against lease dates, and extracting index lease data for integration into external rent-forecasting systems.

SELECT lease_num,
       lease_name,
       index_lease_number,
       index_type,
       base_year,
       base_index,
       assessment_date,
       index_commencement_date
FROM   apps.pn_index_leases_v
WHERE  base_year = :p_base_year
AND    org_id = :p_org_id;

To list index leases alongside their location and responsible user:

SELECT l.lease_num,
       l.index_lease_number,
       l.location_code,
       l.user_responsible,
       l.currency_code,
       l.increase_on_type
FROM   apps.pn_index_leases_v l
WHERE  l.lease_id = :p_lease_id;

Because the view applies an outer join for LOCATION_CODE and a lookup decode for INCREASE_ON_TYPE, queries should not assume a location always exists. All access should be read-only; any DML must target PN_INDEX_LEASES_ALL directly through the supported Property Manager APIs. Filtering by ORG_ID is recommended in Multi-Org environments to preserve operating unit security.