Search Results pn_var_abatements_all




Overview
Explore in AI Chat

Overview

The PN_VAR_ABATEMENTS_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. It serves as the primary repository for storing detailed information about recurring abatements applied to variable rent invoices. An abatement, in this context, is a recurring reduction or discount in the variable rent amount due, often negotiated as part of a lease agreement. This table is critical for the accurate calculation and invoicing of net variable rent charges, ensuring that contractual abatement terms are systematically applied and tracked over the lease term. Its "ALL" suffix indicates it is a multi-organization table, storing data partitioned by the operating unit (org_id).

Key Information Stored

The table's structure is designed to link abatements to specific variable rent invoices and their underlying agreements. The primary key, VAR_ABATEMENT_ID, uniquely identifies each abatement record. The most significant foreign key columns define its core relationships: VAR_RENT_INV_ID links the abatement to a specific invoice line in the PN_VAR_RENT_INV_ALL table, while VAR_RENT_ID connects it to the master variable rent definition in PN_VAR_RENTS_ALL. The PAYMENT_TERM_ID column, referencing PN_PAYMENT_TERMS_ALL, associates the abatement with specific payment terms that govern its calculation and application. While the exact column list is not fully detailed in the provided metadata, typical data stored would include the abatement amount or percentage, effective dates, frequency, and status, all tied to the invoice and lease.

Common Use Cases and Queries

This table is central to processes involving variable rent billing and lease financial analysis. A primary use case is the generation of accurate tenant invoices, where the system queries this table to apply all valid abatements to the calculated variable rent for a specific period. For reporting, it enables analysis of abatement costs and lease profitability. Common queries involve joining to invoice and rent tables to summarize abatements by lease or property. A sample reporting query pattern might be:

  • SELECT pvra.VAR_RENT_ID, pvria.INVOICE_ID, SUM(pvra.ABATEMENT_AMOUNT)
  • FROM PN_VAR_ABATEMENTS_ALL pvra, PN_VAR_RENT_INV_ALL pvria
  • WHERE pvra.VAR_RENT_INV_ID = pvria.VAR_RENT_INV_ID
  • AND pvria.ORG_ID = :org_id
  • GROUP BY pvra.VAR_RENT_ID, pvria.INVOICE_ID;

This would provide a summary of total abatement amounts applied per variable rent agreement per invoice.

Related Objects

The PN_VAR_ABATEMENTS_ALL table has defined foreign key relationships with several key Property Manager tables, as documented in the ETRM metadata. These relationships are fundamental to its integrity and function:

  • PN_VAR_RENT_INV_ALL: Joined via the VAR_RENT_INV_ID column. This is the most direct link, connecting each abatement record to the specific variable rent invoice line item it reduces.
  • PN_VAR_RENTS_ALL: Joined via the VAR_RENT_ID column. This links the abatement to the master variable rent agreement, providing context at the lease level.
  • PN_PAYMENT_TERMS_ALL: Joined via the PAYMENT_TERM_ID column (referenced twice in the metadata). This relationship ties the abatement calculation and timing to the defined payment schedule and terms.

These relationships ensure that abatement data is consistently maintained within the hierarchy of lease terms, variable rent formulas, and final invoice generation.