Search Results pn_var_rent_dates_all




Overview

The PN_VAR_RENT_DATES_ALL table is a core data object within the Oracle E-Business Suite Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. Its primary role is to manage the date-related parameters and frequencies for variable rent agreements. Variable rent, a common feature in commercial real estate leases, is calculated based on factors like sales volume or usage, rather than a fixed monthly amount. This table stores the critical calendar and frequency definitions that determine when these variable rent calculations are performed, billed, and recognized in the General Ledger (GL). It acts as the master scheduler, defining the periodic cycles—such as monthly, quarterly, or annually—for which variable rent amounts are computed and the specific GL calendar that governs the accounting periods for these transactions.

Key Information Stored

The table's structure is designed to capture the scheduling logic for variable rent agreements. While a full column list is not provided in the metadata, the documented primary and foreign keys indicate its core data elements. The primary key, VAR_RENT_DATE_ID, uniquely identifies each date frequency record. The foreign key column, VAR_RENT_ID, links each record to its parent variable rent agreement in the PN_VAR_RENTS_ALL table. Based on its described purpose, the table typically stores columns such as the frequency type (e.g., 'MONTHLY', 'QUARTERLY'), the day of the period for calculations, the start and end dates for the frequency schedule, and a reference to the specific GL calendar (like a calendar ID or name) to be used for mapping dates to accounting periods. This ensures all variable rent calculations adhere to the correct fiscal calendar for financial reporting.

Common Use Cases and Queries

This table is central to the automated rent calculation engine. A primary use case is the batch process that generates variable rent invoices or journal entries. The process queries this table to determine which agreements have a calculation date falling within the current processing period. For reporting and analysis, common queries involve joining this table to the main rent agreement table to list all active variable agreements and their billing frequencies. A sample SQL pattern to retrieve this information would be:

SELECT vr.agreement_num, vrd.frequency, vrd.calendar_id, vrd.start_date
FROM pn_var_rents_all vr, pn_var_rent_dates_all vrd
WHERE vr.var_rent_id = vrd.var_rent_id
AND vr.status = 'ACTIVE'
AND SYSDATE BETWEEN vrd.start_date AND NVL(vrd.end_date, SYSDATE);

Administrators may also query this table to troubleshoot missing calculations by verifying that the date frequencies are correctly set up and aligned with the GL calendar.

Related Objects

The PN_VAR_RENT_DATES_ALL table has a direct and critical relationship with the main variable rent header table, as documented by the provided foreign key constraint.

  • PN_VAR_RENTS_ALL: This is the parent table for all variable rent agreements. The relationship is defined by the foreign key from PN_VAR_RENT_DATES_ALL.VAR_RENT_ID to PN_VAR_RENTS_ALL.VAR_RENT_ID. A single variable rent agreement (row in PN_VAR_RENTS_ALL) can have one or more associated date frequency records in PN_VAR_RENT_DATES_ALL, though typically one active schedule exists at a time.

While not explicitly listed in the provided metadata, this table is also fundamentally related to the GL calendar tables (such as GL_PERIODS or product-specific calendar structures) via the stored calendar reference. Furthermore, it feeds data into the PN_VAR_RENT_INVOICES_ALL or PN_VAR_RENT_CALC_DETAILS_ALL tables, which store the actual calculated amounts generated based on the schedules defined here.