Results for “pn_var_rent_dates_v”

16 results




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

Overview

PN_VAR_RENT_DATES_V is a PL/SQL view owned by the APPS schema and defined within the Oracle Property Manager (PN) module of Oracle E-Business Suite. As documented in the ETRM metadata, its description is a "Form view for viewing variable rent dates details." The object holds a VALID status in both the 12.1.1 and 12.2.2 releases, indicating it is a supported, active dictionary object used by the Property Manager application forms layer.

The view serves as a reporting and integration surface over the variable rent dates configuration that drives recurring billing, invoicing, reconciliation, and audit scheduling for leases with variable rent terms. Because it is a form view rather than a table, it presents a stable, denormalized projection of calendar-derived scheduling attributes that forms and concurrent programs can query without directly joining the underlying transaction table. The single referenced base object, PN_VAR_RENT_DATES, confirms the view is a thin, single-table projection rather than a multi-table join.

Underlying Base Objects

The only documented base object referenced by this view is the table PN_VAR_RENT_DATES, accessed through a synonym in the APPS schema. The view text selects from PN_VAR_RENT_DATES using the alias CAL. No other tables, lookup views, or flexfield views are joined. All columns returned are direct projections of base-table columns, with the exception of a single transformation.

That transformation is the NVL expression on USE_GL_CALENDAR: NVL(CAL.USE_GL_CALENDAR, 'Y') USE_GL_CALENDAR. This ensures a default value of 'Y' is returned when the underlying flag is null, meaning the General Ledger calendar is treated as the effective calendar by default. The view is therefore effectively a filtered-by-default convenience layer, not a re-aggregation or derived-join object.

Key Columns

The view exposes the full audit trail of the base record: ROW_ID (from CAL.ROWID), VAR_RENT_DATE_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. It also exposes VAR_RENT_ID, the foreign key linking each scheduled date set to its parent variable rent definition, and ORG_ID for multi-org security.

Calendar and frequency attributes include USE_GL_CALENDAR, GL_PERIOD_SET_NAME, PERIOD_TYPE, YEAR_START_DATE, and PERIOD_FREQ_CODE. Billing and reporting schedules are represented by REPTG_FREQ_CODE, REPTG_DAY_OF_MONTH, REPTG_DAYS_AFTER, INVG_FREQ_CODE, INVG_DAY_OF_MONTH, INVG_DAYS_AFTER, INVG_SPREAD_CODE, and INVG_TERM. Reconciliation and audit scheduling are governed by RECON_FREQ_CODE, RECON_DAY_OF_MONTH, RECON_DAYS_AFTER, AUDIT_FREQ_CODE, AUDIT_DAY_OF_MONTH, and AUDIT_DAYS_AFTER. The AUDIT_FREQ_CODE column, which corresponds directly to the user's search term, defines the frequency at which audit dates are generated for the variable rent schedule.

Fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) and a free-text COMMENTS column are also exposed.

Common Use Cases and Queries

Typical use cases include diagnosing variable rent schedules, reproducing audit and reconciliation frequency configuration in custom reports, and extracting schedule data for downstream integration or reconciliation with billing output.

  • Retrieve all schedule rows for a given variable rent definition, including audit frequency:
    SELECT var_rent_date_id, var_rent_id, audit_freq_code, audit_day_of_month, audit_days_after, recon_freq_code FROM apps.pn_var_rent_dates_v WHERE var_rent_id = :p_var_rent_id;
  • Find schedules configured with a specific audit frequency:
    SELECT var_rent_id, audit_freq_code, use_gl_calendar, gl_period_set_name FROM apps.pn_var_rent_dates_v WHERE audit_freq_code = :p_audit_freq_code;
  • List all rows for an operating unit with defaulted calendar flag:
    SELECT var_rent_id, period_freq_code, invg_freq_code, audit_freq_code FROM apps.pn_var_rent_dates_v WHERE org_id = :p_org_id AND use_gl_calendar = 'Y';

Because the view is a direct projection of PN_VAR_RENT_DATES, any query can be rewritten against the base table; the view primarily provides the defaulted USE_GL_CALENDAR value and a stable interface for form and report consumers.