Search Results pn_lease_transactions_all




Overview
Explore in AI Chat

Overview

The PN_LEASE_TRANSACTIONS_ALL table is a core transactional data store within the Oracle E-Business Suite Property Manager module (PN). It serves as the system of record for all financial and administrative transactions performed on a lease, forming the detailed audit trail for lease lifecycle management. In the context of EBS 12.1.1 and 12.2.2, this table is fundamental to tracking changes, payments, adjustments, and other activities that impact the financial and contractual terms of a lease agreement. As an "_ALL" table, it is designed to support multi-organization access (MOAC) by storing data across operating units, with security typically enforced by a Virtual Private Database (VPD) policy. Its role is to provide the granular transaction history that feeds into lease accounting, reporting, and inquiry functionalities.

Key Information Stored

The table's primary structure centers on the unique transaction identifier and its relationships to key lease entities. The primary key, LEASE_TRANSACTION_ID, uniquely identifies each row. Two critical foreign keys define its core relationships: LEASE_ID links the transaction to its master agreement in PN_LEASES_ALL, and LOCATION_ID associates it with a specific property location in PN_LOCATIONS_ALL. While the provided ETRM excerpt does not list all columns, typical transactional data stored includes transaction dates, types (e.g., payment, amendment, termination), amounts, periods affected, and accounting references. This structure allows the system to maintain a complete chronological record of every action that modifies the lease's financial or legal state.

Common Use Cases and Queries

This table is central to transaction reporting, lease audit trails, and supporting period-end processes. Common use cases include generating detailed lease transaction histories for compliance, reconciling scheduled versus actual payments, and analyzing lease modification impacts. A fundamental query pattern involves joining to the lease and location master tables to provide context. For example, to retrieve all transactions for a specific lease within a date range, a query would filter on LEASE_ID and transaction date columns. Reporting often aggregates transaction amounts by type or period, supporting financial statement preparation. The table is also critical for troubleshooting, as it allows consultants and administrators to trace the origin of calculated lease liabilities or expense figures back to individual transactional events.

Related Objects

  • PN_LEASES_ALL: The parent lease master table, linked via the foreign key on LEASE_ID.
  • PN_LOCATIONS_ALL: The property locations table, linked via the foreign key on LOCATION_ID.
  • PN_LEASE_CHANGES_ALL: This table holds a foreign key (LEASE_TRANSACTION_ID) referencing PN_LEASE_TRANSACTIONS_ALL, indicating it stores detailed change records associated with each high-level transaction.
  • PN_LEASE_TRANSACTIONS_PK: The primary key constraint on LEASE_TRANSACTION_ID.

Integration with Oracle Subledger Accounting (SLA) and General Ledger is also typical, where transaction data from this table is used to create accounting entries, though those relationships are managed through interface and distribution tables.