Results for “grp_date_id”

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

Overview

PN_VAR_RENT_DETAILS_V is a form-driven database view owned by the APPS schema in Oracle EBS Property Manager (PN). It is documented as "Form view for viewing variable rent details by line item and group date." The view presents variable (percentage or turnover) rent calculation results at the granularity of a line item and a group date, exposing both the transactional amounts computed by the variable rent engine and the accounting flexfield context used to post those amounts. Because it is a UNION ALL of two underlying views — PN_FOR_RENT_DETAILS_V (forecasted rent) and PN_ACT_RENT_DETAILS_V (actual rent) — it provides a single consolidated read surface for both forecasted and actual variable rent lines.

Its principal role is to support the Variable Rent Details form/window and any downstream reporting or integration that must display or extract variable rent by line item and period. The inclusion of ACTUAL_EXP_CODE, FORECASTED_EXP_CODE, and VARIANCE_EXP_CODE makes it especially relevant to users searching for the forecasted_exp_code attribute, since that column appears directly in the view's projection and identifies the accounting expense code associated with forecasted rent amounts.

Underlying Base Objects

The documented base objects underlying this view are:

• PN_VAR_BKPTS_DET_ALL (synonym) — variable rent breakpoint detail records, supplying breakpoint volume boundaries and rates.
• PN_VAR_GRP_DATES_ALL (synonym) — group date definitions used to bucket variable rent calculations per line item.
• PN_VAR_RENTS (synonym) — the stored variable rent amounts and related volume/rate columns.
• PN_VAR_RENT_CALC_PKG (package) — the calculation package that computes variable rent, breakpoint application, and cumulative rent logic.
• PN_VAR_TRX_DETAILS_ALL (synonym) — variable rent transaction detail lines.
• PN_VAR_TRX_HEADERS_ALL (synonym) — variable rent transaction headers.

The view itself does not directly join these tables; those objects participate through the two unioned component views PN_FOR_RENT_DETAILS_V and PN_ACT_RENT_DETAILS_V, with PN_VAR_RENT_CALC_PKG supplying the breakpoint and cumulative calculation semantics reflected in the columns (TOT_VOL, BKPT_VOL_START, BKPT_VOL_END, VOL_APPL, BKPT_RATE, VAR_RENT, CUMULATIVE_RENT).

Key Columns

• GROUP_DATE — the group date bucket to which the variable rent line belongs.
• INVOICE_DATE — invoice date associated with the rent line.
• LINE_ITEM_ID — the variable rent line item identifier; also the partition key for the cumulative rent window.
• TOT_VOL — total volume for the line item.
• BKPT_VOL_START / BKPT_VOL_END — breakpoint volume range boundaries applied to the line.
• VOL_APPL — volume applied within the breakpoint range.
• BKPT_RATE — breakpoint rate applied to the applied volume.
• VAR_RENT — variable rent amount for the row.
• CUMULATIVE_RENT — running total of VAR_RENT partitioned by LINE_ITEM_ID and ordered by LINE_ITEM_ID, GROUP_DATE, BKPT_VOL_START (unbounded preceding).
• ACTUAL_EXP_CODE — expense/account code for actual rent amounts.
• FORECASTED_EXP_CODE — expense/account code for forecasted rent amounts (the attribute referenced by the user search).
• VARIANCE_EXP_CODE — expense/account code for variance amounts.
• VAR_RENT_TYPE — discriminator for the variable rent type.
• ORG_ID — operating unit / organization identifier, supporting Multi-Org access.

Common Use Cases and Queries

Typical uses include variable rent inquiry by line item and group date, reconciliation of forecasted versus actual rent with variance, and extraction of expense code mappings for downstream accounting. The following query retrieves forecasted and actual rent with variance codes for a specific line item:

• SELECT line_item_id, group_date, tot_vol, vol_appl, bkpt_rate, var_rent, cumulative_rent, actual_exp_code, forecasted_exp_code, variance_exp_code FROM apps.pn_var_rent_details_v WHERE line_item_id = :line_item_id AND org_id = :org_id ORDER BY group_date, bkpt_vol_start;

To isolate forecasted rent rows and their associated expense code:

• SELECT group_date, line_item_id, var_rent, forecasted_exp_code FROM apps.pn_var_rent_details_v WHERE forecasted_exp_code IS NOT NULL AND org_id = :org_id;

Because the underlying definition is a UNION ALL with an analytic cumulative sum, queries should always constrain by ORG_ID and LINE_ITEM_ID (or GROUP_DATE range) to avoid full scans and to preserve the intended partitioning of CUMULATIVE_RENT.