Search Results assignable_flag




Overview
Explore in AI Chat

Overview

PN_TENANCIES_HISTORY is a table in the Oracle E-Business Suite Property Manager (PN) module, owned by the PN schema. Its documented purpose is to track changes in leased or subleased locations, providing a historical audit trail of tenancy records as they evolve over the lease lifecycle. In EBS 12.1.1 and 12.2.2, this table works alongside PN_TENANCIES_ALL, which holds the current active tenancy records, while PN_TENANCIES_HISTORY preserves prior states generated whenever a lease change is applied.

Based on the Data Vault classification heuristic derived from its foreign key structure, this table is best modeled as a link, connecting leases, lease changes, locations, tenancies, and customer accounts. This classification reflects its role as a transactional association table that records relationships between business entities at a point in time. The table contains 50 documented columns in the ETRM 12.2.2 physical schema.

Key Information Stored

The primary key is TENANCY_HISTORY_ID, enforced by the PN_TENANCIES_HISTORY_PK constraint, with a unique index PN_TENANCIES_HISTORY_U1 on the same column. This surrogate key uniquely identifies each historical version of a tenancy record and is distinct from the business identity represented by TENANCY_ID, which links back to the current tenancy in PN_TENANCIES_ALL.

The most significant columns include:

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are present, along with 15 ATTRIBUTE flex columns and RECOVERY_TYPE_CODE, RECOVERY_SPACE_STD_CODE, FIN_OBLIG_END_DATE, ASSIGNABLE_FLAG, SUBLEASEABLE_FLAG, and TENANTS_PROPORTIONATE_SHARE.

Common Use Cases and Queries

Typical uses include historical space analysis, lease change auditing, and reporting on occupancy trends over time. A common query pattern joins the history table to its parent tables to reconstruct the tenancy timeline:

  • SELECT h.TENANCY_HISTORY_ID, h.TENANCY_ID, h.LEASE_ID, h.LEASE_CHANGE_ID, h.OCCUPANCY_DATE, h.EXPIRATION_DATE, h.STATUS FROM PN_TENANCIES_HISTORY h WHERE h.ORG_ID = :org_id AND h.LOCATION_ID = :location_id ORDER BY h.OCCUPANCY_DATE.
  • Joining to PN_LEASES_ALL on LEASE_ID and PN_LOCATIONS_ALL on LOCATION_ID to report leased versus subleased space history.
  • Joining to HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL on CUSTOMER_ID and CUSTOMER_SITE_USE_ID to attribute historical occupancy to specific tenants and sites.
  • Comparing current PN_TENANCIES_ALL rows against the latest PN_TENANCIES_HISTORY row per TENANCY_ID to detect stale or unapplied changes.

Related Objects

The following objects are directly referenced by PN_TENANCIES_HISTORY and are the most significant for joins and dependency analysis:

  • PN_TENANCIES_ALL — via TENANCY_ID; the current tenancy master record.
  • PN_LEASES_ALL — via LEASE_ID; the governing lease.
  • PN_LEASE_CHANGES_ALL — via LEASE_CHANGE_ID and NEW_LEASE_CHANGE_ID; the lease change event.
  • PN_LOCATIONS_ALL — via LOCATION_ID; the physical location.
  • HZ_CUST_ACCOUNTS — via CUSTOMER_ID; the tenant account.
  • HZ_CUST_SITE_USES_ALL — via CUSTOMER_SITE_USE_ID; the tenant site use.