Search Results pn_var_lines




Overview
Explore in AI Chat

Overview

APPS.PN_VAR_LINES_V is a reporting view within the Oracle E-Business Suite Property Manager (PN) module, which forms part of the ETRM (Enterprise Territory and Real estate Management) footprint used for managing leases, properties, and variable rent agreements. The view consolidates variable rent line definitions with aggregated rent summary figures, presenting both actual and forecasted variable rent amounts alongside descriptive lookup values and descriptive flexfield attributes. Its principal role is to simplify the retrieval of variable rent line data that would otherwise require joining multiple base tables, making it suitable for concurrent program reports, Oracle Forms LOV queries, and downstream integration extractions. The view is defined in the APPS schema, and the presence of the ORG_ID column indicates that it is an operating-unit (multi-org) aware object, enabling it to respect the MOAC (Multi-Org Access Control) security model during query execution.

Underlying Base Objects

The view is defined over several base objects documented in the 12.2.2 metadata. The primary line-level source is PN_VAR_LINES (exposed through the PN_VAR_LINES synonym), which holds individual variable rent line items keyed by LINE_ITEM_ID and PERIOD_ID. Aggregated rent figures are derived from PN_VAR_RENT_SUMM_ALL, aggregated in an inline subquery that sums actual and forecasted variable rent values per line item and period. Template information is joined from PN_VAR_TEMPLATES_ALL to resolve the AGREEMENT_TEMPLATE identifier to a descriptive template name. Two instances of the FND_LOOKUPS view (aliased look and look1) provide the translated MEANING values for the sales channel and item category codes. The FND_GLOBAL package is referenced in the object metadata, typically to return session context such as ORG_ID for operating-unit filtering. All joins to the lookup and summary subqueries use outer-join syntax, so lines without corresponding summary or lookup rows are still returned.

Key Columns

The view exposes a ROWID alias (row_id) plus the primary key LINE_ITEM_ID and the user-facing LINE_ITEM_NUM. Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Contextual identifiers include PERIOD_ID, LINE_TEMPLATE_ID, AGREEMENT_TEMPLATE_ID, LINE_DEFAULT_ID, and VAR_RENT_ID. The SALES_TYPE_CODE and ITEM_CATEGORY_CODE columns are translated into human-readable SALES_CHANNEL and ITEM_CATEGORY values via FND_LOOKUPS. Financial measures are the aggregated ACTUAL_RENT (computed as sum of ACT_VAR_RENT minus first-year rent plus true-up variable rent) and FORECASTED_RENT (sum of FOR_VAR_RENT), which corresponds directly to the search term forecasted_rent. The view also surfaces all fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY for descriptive flexfield support, and ORG_ID for operating-unit segregation.

Common Use Cases and Queries

Typical use cases include reporting forecasted versus actual variable rent by period, extracting variable rent line details for lease reconciliation, and populating custom interfaces that consume property rent data. Because forecasted_rent is a first-class column, a frequent query filters lines by period and operating unit, for example:

  • SELECT line_item_id, line_item_num, period_id, sales_channel, item_category, actual_rent, forecasted_rent, agreement_template FROM apps.pn_var_lines_v WHERE org_id = :p_org_id AND period_id = :p_period_id ORDER BY line_item_num;
  • Aggregating forecasts: SELECT period_id, SUM(forecasted_rent) forecasted_rent, SUM(actual_rent) actual_rent FROM apps.pn_var_lines_v GROUP BY period_id;
  • Variance analysis: SELECT line_item_id, forecasted_rent - actual_rent variance FROM apps.pn_var_lines_v WHERE forecasted_rent <> actual_rent;

Queries should always be scoped by ORG_ID to comply with MOAC, and callers should account for the outer joins, which may return NULL actual_rent or forecasted_rent values where no summary rows exist.