Search Results pn_var_trx_details_all




Overview
Explore in AI Chat

Overview

The PN_VAR_TRX_DETAILS_ALL table is a core data repository within the Oracle E-Business Suite (EBS) Property Manager (PN) module. Its primary function is to store detailed transactional records for variable rent calculations. Variable rent, a key feature in commercial property management, refers to lease payments that fluctuate based on agreed-upon metrics, such as a percentage of a tenant's sales revenue. This table acts as the system of record for each individual variable rent transaction, capturing the calculated amounts and associated lease terms. Its role is critical for generating accurate billing, supporting financial reporting, and providing an audit trail for all variable rent-related activities within the application.

Key Information Stored

While the provided ETRM excerpt is concise, the table's structure is designed to support variable rent processing. The primary key, TRX_DETAIL_ID, is a unique system-generated identifier for each variable rent record. Based on standard EBS design patterns for transactional tables in the PN module, other significant columns typically include identifiers to link to the parent lease (such as LEASE_ID or LEASE_CHANGE_ID), the specific variable rent term (VAR_RENT_ID), and the period being calculated. It also stores critical financial data like the calculated rent amount, currency, and status flags indicating whether the transaction is draft, finalized, or posted. The "_ALL" suffix denotes that the table is multi-org enabled, containing data for all operating units.

Common Use Cases and Queries

This table is central to several operational and reporting processes. A common use case is the generation of variable rent invoices, where the system queries finalized transactions for a given lease and period. Financial analysts run queries against this table to analyze variable rent performance across a property portfolio. Auditors use it to trace the calculation and approval history of variable payments. A fundamental query pattern involves joining to the lease and variable rent term headers using the foreign key relationships.

  • Sample SQL to retrieve variable rent details for a specific lease:
    SELECT trx_detail_id, amount, period_start_date, period_end_date
    FROM pn_var_trx_details_all
    WHERE lease_id = <lease_id>
    AND status = 'FINALIZED'
    ORDER BY period_start_date;
  • Reporting on total variable rent by property or operating unit.
  • Reconciling calculated variable rent against tenant-reported sales figures.

Related Objects

The PN_VAR_TRX_DETAILS_ALL table exists within a network of related objects in the Property Manager schema. As documented, its primary key constraint is PN_VAR_TRX_DETAILS_PK on the TRX_DETAIL_ID column. It is the child table in relationships with core lease and variable rent definition tables. While specific foreign key names are not listed in the excerpt, standard implementation involves joins to:

  • PN_LEASES_ALL via a column such as LEASE_ID, linking the transaction to the master lease agreement.
  • PN_VAR_RENTS_ALL via a column such as VAR_RENT_ID, linking to the specific variable rent clause or term defined in the lease.
  • It is also commonly referenced by interfaces, reports, and the PN Variable Rent Calculation engine, which populates the table.