Search Results pn_lease_details_all

Overview

The PN_LEASE_DETAILS_ALL table is a core data repository within the Oracle E-Business Suite (EBS) Property Manager module (PN). It serves as the central table for storing critical lease-specific dates and accounting information for every lease agreement managed in the system. Its primary role is to maintain the detailed financial and temporal parameters that drive lease accounting calculations, payment schedules, and general ledger postings. As an "ALL" table, it is designed to support multi-organization access (Multi-Org) by including data for all operating units, making it essential for enterprise-wide lease portfolio management in versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which indicate the nature of its critical columns. The primary key, LEASE_DETAIL_ID, uniquely identifies each record. The mandatory foreign key to PN_LEASES_ALL (LEASE_ID) ties each detail record to a master lease agreement. Another key foreign key, LEASE_CHANGE_ID, links to PN_LEASE_CHANGES_ALL, enabling the system to track amendments or modifications to lease terms over time. Crucially, the table holds accounting references via the EXPENSE_ACCOUNT_ID, which points to GL_CODE_COMBINATIONS to determine the correct general ledger account for lease expenses. The RESPONSIBLE_USER column, linked to FND_USER, assigns accountability for lease management. While the exact column list is not fully detailed in the excerpt, the description implies the table stores dates such as commencement, expiration, and critical notice dates, alongside other accounting flags and parameters necessary for compliance and financial reporting.

Common Use Cases and Queries

This table is fundamental for lease lifecycle reporting and financial integration. Common operational and reporting scenarios include generating lease abstracts with key dates and accounts, feeding data into period-end close processes for accruals and amortization, and auditing lease term changes. A typical query might join this table to the lease master to pull a summary for a specific operating unit or responsible manager. For example:

• Identifying leases with upcoming expiration dates for portfolio planning.
• Extracting the expense account combinations for a batch of leases to interface with General Ledger.
• Comparing current lease details against historical records in PN_LEASE_DETAILS_HISTORY to analyze term changes.

A sample SQL pattern to retrieve active lease details would involve filtering on date columns and joining with PN_LEASES_ALL and GL_CODE_COMBINATIONS.

Related Objects

PN_LEASE_DETAILS_ALL sits at the center of a key relational cluster within Property Manager. Its most direct relationships, as documented, are:

• PN_LEASES_ALL: The parent table, providing the master lease header information.
• PN_LEASE_CHANGES_ALL: Tracks the history of amendments that result in new detail records.
• GL_CODE_COMBINATIONS: Provides the accounting flexfield structure for the expense account.
• FND_USER: Provides the username for the responsible party.
• PN_LEASE_DETAILS_HISTORY: A child table that archives previous versions of lease detail records, ensuring a full audit trail when details are updated.

This network of relationships underscores the table's integral role in maintaining a complete, auditable, and accountably sound lease management system.