Search Results pn_lease_details_history




Overview
Explore in AI Chat

Overview

The PN_LEASE_DETAILS_HISTORY table is a core audit and historical tracking object within the Oracle E-Business Suite Property Manager (PN) module. Its primary function is to capture and persist a historical record of all modifications made to lease detail data elements. This table is essential for maintaining a complete audit trail, enabling compliance reporting, and facilitating the analysis of lease terms and financial obligations over time. It operates as a supporting table to the main transactional lease tables, ensuring that every change to a lease's detailed terms is permanently recorded with contextual metadata, such as who made the change and when. This historical integrity is critical for accurate financial reporting, lease administration, and dispute resolution in a property management context.

Key Information Stored

The table stores a snapshot of lease detail data at the point of each change. While the full column list is extensive, the provided metadata highlights critical relational and audit columns. The primary key, DETAIL_HISTORY_ID, uniquely identifies each historical record. The table links to major lease entities through foreign keys: LEASE_ID references the master lease in PN_LEASES_ALL, LEASE_DETAIL_ID points to the specific detail line in PN_LEASE_DETAILS_ALL that was modified, and LEASE_CHANGE_ID optionally links to a formal change document in PN_LEASE_CHANGES_ALL. For audit purposes, it tracks the RESPONSIBLE_USER (linked to FND_USER) who initiated the change. Financially, it stores the EXPENSE_ACCOUNT_ID (linked to GL_CODE_COMBINATIONS), capturing the accounting flexfield assignment at the time of the change. Each row typically includes standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) to complete the audit trail.

Common Use Cases and Queries

A primary use case is generating audit reports for lease modifications, either for internal controls or tenant inquiries. Analysts query this table to trace the evolution of specific lease terms, such as rental amounts or expense accounts. A common pattern is to join with lease and detail tables to present a coherent history. For example, to see all changes to expense accounts for a specific lease:

  • SELECT hist.*, detail.lease_detail_id, detail.attribute_category
  • FROM pn_lease_details_history hist,
  • pn_lease_details_all detail
  • WHERE hist.lease_detail_id = detail.lease_detail_id
  • AND hist.lease_id = <lease_id>
  • AND hist.expense_account_id IS NOT NULL
  • ORDER BY hist.creation_date DESC;

Another critical use case is supporting period-end reconciliation and financial audits, where accountants must verify the accuracy and authorization of changes to lease-related general ledger accounts recorded throughout a period.

Related Objects

As indicated by its foreign keys, PN_LEASE_DETAILS_HISTORY has direct dependencies on several key Property Manager and core EBS tables. It is a child table of PN_LEASES_ALL (the lease header) and PN_LEASE_DETAILS_ALL (the source transactional detail lines). Its optional relationship with PN_LEASE_CHANGES_ALL allows it to associate historical records with formal lease amendment documents. For user and accounting context, it references the core FND_USER table and the general ledger's GL_CODE_COMBINATIONS table. This table is typically accessed indirectly through Property Manager's standard forms and reports, but it is also a direct source for custom historical reports and data extracts for lease lifecycle management.