Results for “pn_var_rent_dates”

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

Overview

APPS.PN_VAR_RENT_DATES_V is a reporting view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes the variable rent date configuration records used by Oracle Property Manager / ETRM (Enterprise Territory and Real Estate Management). Variable rent arrangements allow lease administrators to define rent amounts that fluctuate over the lease term according to a calendar-driven schedule rather than a fixed escalation pattern. The view presents the date-generation parameters that drive those schedules, including frequency codes, day-of-month anchors, and offset days for reporting, invoicing, auditing, and reconciliation activities.

Functionally, the view is a pass-through projection over the base table, adding a ROWID alias and applying an NVL default to the USE_GL_CALENDAR flag. It is intended for query and reporting use; DML operations should be directed at the underlying table. Its principal role is to support date calculation logic and downstream reporting by presenting a stable, ordered set of columns that describe how each variable rent record's dates are derived.

Underlying Base Objects

The view is defined over a single base object: PN_VAR_RENT_DATES, referenced through a synonym in the APPS schema. The view does not join to GL calendars, period sets, or lease tables; it simply renames the source table alias and selects all business and descriptive columns. The relationship is therefore strictly one-to-one — every row in the view corresponds to exactly one row in PN_VAR_RENT_DATES, filtered only by the requesting user's access to the APPS synonym. Because the view includes ROWID (as ROW_ID), it can be used to identify specific rows in the base table for update or delete operations executed programmatically.

Key Columns

• VAR_RENT_DATE_ID — Primary key identifying each variable rent date definition.
• VAR_RENT_ID — Foreign key linking the date definition to its parent variable rent record.
• USE_GL_CALENDAR — Flag (defaulted to 'N' via NVL) indicating whether the GL calendar is used for date generation.
• GL_PERIOD_SET_NAME / PERIOD_TYPE — General Ledger period set and period type used when the GL calendar is referenced.
• YEAR_START_DATE — Anchor date from which periodic calculations begin.
• PERIOD_FREQ_CODE / REPTG_FREQ_CODE / INVG_FREQ_CODE / AUDIT_FREQ_CODE / RECON_FREQ_CODE — Frequency codes for period, reporting, invoicing, auditing, and reconciliation schedules respectively.
• REPTG_DAY_OF_MONTH, INVG_DAY_OF_MONTH, AUDIT_DAY_OF_MONTH, RECON_DAY_OF_MONTH — Day-of-month anchors for each schedule type.
• REPTG_DAYS_AFTER, INVG_DAYS_AFTER, AUDIT_DAYS_AFTER, RECON_DAYS_AFTER — Offset day counts applied relative to the anchor.
• INVG_SPREAD_CODE / INVG_TERM — Invoicing spread rule and term controlling how invoice amounts are distributed.
• VRG_REPTG_FREQ_CODE — Frequency code for variable rent group reporting.
• ORG_ID — Operating unit identifier supporting multi-org access control.
• COMMENTS — Free-form descriptive text.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield columns for client-specific extensions.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is most commonly queried to inspect or troubleshoot the date scheduling parameters behind variable rent records, and to reconcile generated schedules against their configuration. A typical query retrieving all date definitions for a given variable rent record is:

• SELECT var_rent_date_id, var_rent_id, use_gl_calendar, gl_period_set_name, period_freq_code, reptg_freq_code, invg_freq_code, invg_term FROM apps.pn_var_rent_dates_v WHERE var_rent_id = :p_var_rent_id;
• SELECT var_rent_id, COUNT(*) FROM apps.pn_var_rent_dates_v GROUP BY var_rent_id; — to identify variable rents with multiple date definitions.
• SELECT * FROM apps.pn_var_rent_dates_v WHERE org_id = :p_org_id AND use_gl_calendar = 'Y'; — to list definitions relying on the GL calendar within a specific operating unit.

Because the view is a thin projection, any joins to lease, property, or GL period tables must be performed by the calling query using VAR_RENT_ID or GL_PERIOD_SET_NAME as the linking key.