Results for “recon_freq_code”

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

Overview

PN_VAR_PERIODS_DATES_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the PN (Property Manager) product. Its documented purpose is to serve as a form view for viewing variable rent period details. In the Property Manager module, variable rent arrangements allow lease charges to be calculated on the basis of actual usage, sales turnover, or other periodic measurements rather than a fixed contractual amount. Because these arrangements are billed and reconciled over defined reporting periods, users require a consolidated presentation of each period and its associated rent header and frequency information. The view provides exactly that: a flattened, query-ready projection that joins period-level rows to their parent variable rent definition and to the frequency attributes held at the variable rent dates level.

In EBS 12.1.1 and 12.2.2, such views are typically the data source behind an Oracle Forms block or an OAF page region. They are not intended for direct transactional maintenance; instead they present derived, read-oriented data. This makes the view equally suitable for reporting and integration scenarios where a stable, denormalized snapshot of variable rent periods is required without reimplementing the underlying join logic. The view carries a status of VALID and resides in the APPS schema, consistent with standard EBS object ownership conventions.

Underlying Base Objects

The view definition references three principal base objects through APPS synonyms: PN_VAR_PERIODS_ALL, PN_VAR_RENTS, and PN_VAR_RENT_DATES_ALL. The ETRM metadata also lists PN_VAR_RENT_INV_ALL among the referenced base objects for the 12.2.2 release. The join relationships are explicit in the view text: PN_VAR_PERIODS_ALL joins to PN_VAR_RENTS on VAR_RENT_ID, and PN_VAR_RENTS joins to PN_VAR_RENT_DATES_ALL on the same key. This produces one row per variable rent period, enriched with header attributes from PN_VAR_RENTS and frequency attributes from PN_VAR_RENT_DATES_ALL.

• PN_VAR_PERIODS_ALL — supplies the period-level rows, including period identity, sequence, and date range.
• PN_VAR_RENTS — supplies the variable rent header, including the unit of measure, rent number, lease identifier, and operating unit (ORG_ID).
• PN_VAR_RENT_DATES_ALL — supplies the invoice, reconciliation, reporting, and audit frequency codes.
• PN_VAR_RENT_INV_ALL — documented as a referenced base object; it relates to variable rent invoice processing and supports the invoice frequency context of the arrangement.

Key Columns

• ROW_ID — the ROWID of the underlying PN_VAR_PERIODS_ALL row, useful for addressing a specific period record.
• PERIOD_ID / PERIOD_NUM — unique identifier and sequence number of the variable rent period.
• VAR_RENT_ID — foreign key linking each period to its parent variable rent definition.
• START_DATE / END_DATE — the effective date range of the period.
• RENT_NUM / LEASE_ID — the variable rent number and the associated lease identifier, providing business context.
• UOM_CODE — unit of measure against which the variable rent quantity is expressed.
• INVG_FREQ_CODE, RECON_FREQ_CODE, REPTG_FREQ_CODE, AUDIT_FREQ_CODE — invoice, reconciliation, reporting, and audit frequency codes governing how the arrangement is processed.
• ORG_ID — operating unit identifier, enabling multi-org filtered reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns for change tracking.

Common Use Cases and Queries

Typical uses include auditing variable rent periods for a lease, verifying that period date ranges align with configured frequencies, and feeding downstream reporting or reconciliation processes. A representative query retrieves all periods for a given variable rent:

• SELECT period_num, start_date, end_date, uom_code, rent_num FROM pn_var_periods_dates_v WHERE var_rent_id = :p_var_rent_id ORDER BY period_num;
• SELECT lease_id, rent_num, period_num, start_date, end_date FROM pn_var_periods_dates_v WHERE org_id = :p_org_id AND start_date BETWEEN :p_from AND :p_to;

Analysts commonly filter by ORG_ID to respect operating unit security, and join the view back to lease or invoice tables on LEASE_ID or VAR_RENT_ID when reconciling billed amounts to period records. Because the view already resolves the three-table join, it reduces the risk of inconsistent joins in downstream extracts in both 12.1.1 and 12.2.2 environments.