Search Results pn_rights_pk

Overview

The PN_RIGHTS_ALL table is a core data repository within the Oracle E-Business Suite Property Manager module (PN). It serves as the primary transactional table for storing all rights and obligations associated with leases. In the context of lease administration, a "right" represents a specific privilege, responsibility, or condition granted to or imposed upon a party within a lease agreement, such as a renewal option, a termination clause, or a maintenance obligation. This table is fundamental for managing the complete lifecycle of lease terms, enabling organizations to track, report on, and enforce contractual commitments. As a multi-organization enabled table, denoted by the "_ALL" suffix, it segregates data by operating unit, ensuring that lease rights information is maintained securely and appropriately within a multi-org architecture.

Key Information Stored

The table's structure is designed to capture the essential attributes of a lease right. The primary key, RIGHT_ID, uniquely identifies each right record. The critical foreign key LEASE_ID links the right to its master lease agreement in the PN_LEASES_ALL table, establishing the core relationship. The LEASE_CHANGE_ID column optionally links the right to a specific lease amendment or change document recorded in PN_LEASE_CHANGES_ALL, which is vital for tracking the historical evolution of lease terms. While the provided metadata does not list all columns, typical data stored includes the right's type (e.g., option, restriction), description, effective dates (start and end), status, associated financial terms, and the party to whom the right applies (lessor or lessee). This comprehensive data model supports detailed lease abstraction and compliance management.

Common Use Cases and Queries

This table is central to numerous Property Manager processes and reports. A primary use case is generating a lease abstract that summarizes all critical rights and options. Auditors and lease administrators frequently query this table to identify upcoming critical dates, such as lease expiration or option exercise deadlines, for portfolio management. Common SQL patterns involve joining to PN_LEASES_ALL to retrieve lease details and filtering by right type and date. For example, a query to find all renewal options expiring within the next 90 days would join PN_RIGHTS_ALL and PN_LEASES_ALL on LEASE_ID, filter where the right type indicates a renewal option and the notification date falls within the date range, and select relevant lease and right details. Reporting on the density of specific clauses across a property portfolio also relies heavily on this table.

Related Objects

• PN_LEASES_ALL: The master lease table. PN_RIGHTS_ALL is a child table, with a foreign key (LEASE_ID) linking each right to its parent lease.
• PN_LEASE_CHANGES_ALL: Stores amendments and modifications to leases. The foreign key (LEASE_CHANGE_ID) in PN_RIGHTS_ALL allows rights to be associated with the specific change document that created or modified them.
• PN_RIGHTS_HISTORY: A key dependent table that maintains a historical audit trail of changes made to records in PN_RIGHTS_ALL, as indicated by its foreign key (RIGHT_ID) referencing PN_RIGHTS_ALL.
• PN_RIGHTS_PK: The primary key constraint on the RIGHT_ID column, ensuring the uniqueness of each rights record.