Search Results pn_leases_all




Overview

The PN_LEASES_ALL table is the central master data repository for lease contracts within Oracle E-Business Suite (EBS) Property Manager (PN) module. It serves as the foundational record for all lease-related activities, from financial accounting and payment scheduling to space management and compliance tracking. As an "ALL" table, it is multi-organization enabled, storing data partitioned by the ORG_ID column to support implementations with multiple operating units. Every lease entered into the system is uniquely identified by a LEASE_ID, which acts as the primary foreign key propagated to numerous child tables, creating a comprehensive lease hierarchy.

Key Information Stored

The table's primary key is LEASE_ID. While the provided metadata does not list all columns, the foreign key relationships indicate several critical data points stored. The CUSTOMER_ID column links to HZ_CUST_ACCOUNTS (Trading Community Architecture), identifying the lessee or customer party. The ABSTRACTED_BY_USER column links to FND_USER, tracking the individual who abstracted the lease terms into the system. Other essential columns typically include lease number, status, effective dates (start and end), lease type (e.g., operating, finance), and currency. The ORG_ID column is crucial for determining the operating unit context for the lease record.

Common Use Cases and Queries

This table is central to reporting, integration, and data validation. Common use cases include generating a lease listing report, validating lease details for period-end close processes, and extracting data for lease accounting systems. A fundamental query retrieves basic lease information for a specific operating unit, often joined to customer and user tables for comprehensiveness.

  • Lease Master List: SELECT pl.lease_id, pl.lease_num, hca.account_number, pl.start_date, pl.end_date FROM pn_leases_all pl, hz_cust_accounts hca WHERE pl.customer_id = hca.cust_account_id AND pl.org_id = :p_org_id;
  • Data Integrity Validation: Identifying leases missing critical customer assignments by checking for NULL CUSTOMER_ID values.
  • Integration Point: The LEASE_ID is the key exported to downstream financial systems or used in APIs for creating related transactions, such as payments or journal entries.

Related Objects

PN_LEASES_ALL has extensive foreign key relationships, underscoring its role as the core lease entity. The LEASE_ID column is referenced by a vast array of child tables that manage specific lease components. Key documented relationships include:

Each history table (e.g., PN_LEASE_DETAILS_HISTORY, PN_OPTIONS_HISTORY) also references PN_LEASES_ALL, maintaining an audit trail of changes to lease terms over time.