Search Results pn_lease_changes_all




Overview
Explore in AI Chat

Overview

The PN_LEASE_CHANGES_ALL table is a core data object within Oracle E-Business Suite Property Manager (PN) module, serving as the central audit and version control mechanism for lease modifications. It records every instance of a lease being abstracted, amended, or edited, creating a historical audit trail. Each row represents a specific change event, linking back to the master lease record in PN_LEASES_ALL and to the originating transaction in PN_LEASE_TRANSACTIONS_ALL. Its primary role is to maintain data integrity and a complete history of all lease terms, financials, and associated entities over the lifecycle of a lease agreement, which is critical for compliance, reporting, and lease administration.

Key Information Stored

The table's primary key is LEASE_CHANGE_ID, a unique identifier for each change set. Two critical foreign key columns establish its core relationships: LEASE_ID links to the parent lease in PN_LEASES_ALL, and LEASE_TRANSACTION_ID links to the transaction that initiated the change in PN_LEASE_TRANSACTIONS_ALL. The table also tracks user accountability through columns like ABSTRACTED_BY_USER and RESPONSIBLE_USER, which are foreign keys to FND_USER. While the provided metadata focuses on relationships, typical columns would also include timestamps (e.g., creation date), change type indicators, and status fields to manage the lifecycle of the proposed or approved amendments.

Common Use Cases and Queries

A primary use case is generating a complete history of changes for a specific lease, often for audit purposes or to understand the evolution of terms. Developers and report writers frequently query this table to join historical versions of lease details, payment terms, or options. A common SQL pattern involves filtering by LEASE_ID and ordering by a creation date to see the sequence of amendments.

  • Sample Query (Change History): SELECT plc.lease_change_id, plc.creation_date, fu.user_name AS abstracted_by FROM pn_lease_changes_all plc JOIN fnd_user fu ON plc.abstracted_by_user = fu.user_id WHERE plc.lease_id = <lease_id> ORDER BY plc.creation_date DESC;
  • Reporting Use Case: Identifying all leases with amendments created by a specific user within a date range, or reporting on the volume of lease changes per period for operational metrics.
  • Integration Use Case: When extracting lease data for a downstream system, queries often join PN_LEASE_CHANGES_ALL with PN_LEASE_DETAILS_ALL using LEASE_CHANGE_ID to ensure the most recent approved version of details is selected.

Related Objects

PN_LEASE_CHANGES_ALL is a pivotal hub with extensive foreign key relationships, as documented. It is the parent table for historical and current records across numerous lease components. Key documented relationships include:

This structure confirms that PN_LEASE_CHANGES_ALL is the anchor point for tracking all modifications to the lease's constituent parts throughout the amendment process.