Search Results pn_rights_history_pk

Overview

The PN_RIGHTS_HISTORY table is a core data object within the Oracle E-Business Suite Property Manager (PN) module. Its primary function is to maintain a historical audit trail of changes made to lease rights, specifically in the context of lease amendments. When a lease is amended, the associated rights—such as payment terms, area usage, or escalation clauses—may be modified, terminated, or newly created. This table captures the state of a right both before and after an amendment, enabling a complete reconstruction of its lifecycle. It serves as a critical repository for compliance, financial reporting, and lease administration by providing a verifiable record of how contractual obligations have evolved over time.

Key Information Stored

The table's structure is designed to link rights data with specific lease amendment events. While the full column list is not provided in the metadata, the foreign key relationships define its essential components. The primary key, RIGHT_HISTORY_ID, uniquely identifies each historical record. The RIGHT_ID column links to the PN_RIGHTS_ALL table, identifying the specific lease right being tracked. Crucially, the table uses two separate foreign keys to PN_LEASE_CHANGES_ALL: LEASE_CHANGE_ID likely references the amendment that created the historical snapshot, while NEW_LEASE_CHANGE_ID may point to a subsequent amendment that further altered or superseded the right. This design allows the system to chain amendments together, creating a sequential history for each right.

Common Use Cases and Queries

The primary use case is auditing and reporting on the modification history of lease rights. Property administrators and accountants query this table to understand the effective dates and terms of a right for a given period, which is essential for accurate rent billing, expense recovery, and financial accruals. A common reporting pattern involves joining this history table with lease, right, and amendment details. For example, to trace all changes for a specific lease right, a query might join PN_RIGHTS_HISTORY to PN_RIGHTS_ALL on RIGHT_ID and to PN_LEASE_CHANGES_ALL on LEASE_CHANGE_ID to retrieve amendment numbers and dates. Another critical use is during the amendment process itself, where the system likely inserts records into this table to preserve the pre-amendment state of affected rights before applying new terms.

Related Objects

• PN_RIGHTS_ALL: The master table for lease rights. PN_RIGHTS_HISTORY records are created for entries in this table when they are amended.
• PN_LEASE_CHANGES_ALL: The table storing lease amendment headers. PN_RIGHTS_HISTORY is directly linked to this table via two foreign keys (LEASE_CHANGE_ID, NEW_LEASE_CHANGE_ID) to document which amendment action caused the historical record.
• PN_LEASES_ALL: The primary leases table. The metadata indicates a foreign key relationship, suggesting the history may also be linked at the lease header level for broader historical reporting.
• PN_RIGHTS_HISTORY_PK: The primary key constraint enforcing uniqueness on the RIGHT_HISTORY_ID column.