Results for “pn_var_periods”

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

Overview

APPS.PN_VAR_PERIODS_V is a reporting and integration view within the Oracle E-Business Suite Property Manager (PN) module, which forms part of the ETRM (Enterprise Territory and Property Management) suite. The view exposes period-level variable rent records for leases and combines stored period definitions with calculated and aggregated variable rent amounts. Its primary role is to present, for each variable rent period, both the actual invoiced variable rent and the forecasted variable rent computed by the ETRM pricing engine, together with the variance between the two.

Because the view joins period master data to a package function that returns forecasted amounts, it shields reporting tools, concurrent programs, and integration interfaces from the complexity of calling PL/SQL directly. Consumers query a single relational structure rather than invoking PN_VAR_RENT_CALC_PKG themselves. This makes the view well suited to operational reporting, reconciliation of variable rent billing, and downstream data extraction on both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over several documented base objects, each referenced as a synonym owned by APPS:

• PN_VAR_PERIODS — supplies the driving period rows, including period identifiers, start and end dates, descriptive attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15), the organization identifier, and the period status.
• PN_VAR_PERIODS_ALL — the multi-organization variant of the period table, used in the aggregation subquery that sums invoiced amounts.
• PN_VAR_RENTS_ALL — the parent variable rent definition table, joined for validation so that only periods belonging to valid variable rent agreements are returned.
• PN_VAR_RENT_INV_ALL — the variable rent invoice line table, providing ACTUAL_INVOICED_AMOUNT values that are summed per period.
• PN_VAR_RENT_CALC_PKG — a PL/SQL package whose FORECASTED_VAR_RENT function is invoked in the inline aggregation subquery to derive the forecasted variable rent for each period.

The outer query selects from PN_VAR_PERIODS and joins an inline view (aliased summ) and PN_VAR_RENTS_ALL. All joins to the aggregation subquery use outer-join syntax ((+)), so periods with no invoices or no calculable forecast still appear, with null amounts where applicable.

Key Columns

• ROW_ID — the ROWID of the period row, enabling row-level identification.
• PERIOD_ID and PERIOD_NUM — unique identifier and sequence number of the variable rent period.
• VAR_RENT_ID — foreign key to the parent variable rent definition.
• START_DATE and END_DATE — the effective date range of the period.
• ACTUAL_VAR_RENT — sum of ACTUAL_INVOICED_AMOUNT across invoice lines for the period.
• FOR_VAR_RENT — forecasted variable rent returned by PN_VAR_RENT_CALC_PKG.forecasted_var_rent.
• DIFF_VAR_RENT — the difference (ACTUAL_VAR_RENT minus FOR_VAR_RENT), useful for variance analysis.
• ORG_ID — the operating unit, supporting multi-org security.
• STATUS — the period status flag.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical applications include reconciling forecasted variable rent against actual invoiced amounts, feeding property-level accrual reporting, and supplying period detail to integration or data-warehouse extracts.

A straightforward variance report for a given variable rent:

• SELECT period_num, start_date, end_date, actual_var_rent, for_var_rent, diff_var_rent FROM apps.pn_var_periods_v WHERE var_rent_id = :p_var_rent_id ORDER BY period_num;

Filtering to open periods for one operating unit:

• SELECT period_id, var_rent_id, actual_var_rent, for_var_rent FROM apps.pn_var_periods_v WHERE org_id = :p_org_id AND status = 'OPEN';

Aggregating total forecast versus actual across periods:

• SELECT var_rent_id, SUM(actual_var_rent), SUM(for_var_rent), SUM(diff_var_rent) FROM apps.pn_var_periods_v GROUP BY var_rent_id;

Because forecasted amounts are computed at query time by the calculation package, performance depends on the number of periods and the complexity of the variable rent formula; restricting by VAR_RENT_ID or ORG_ID is recommended for interactive reporting.