Search Results pn_tenancies_all




Overview
Explore in AI Chat

Overview

The PN_TENANCIES_ALL table is a core data object within the Oracle E-Business Suite Property Manager (PN) module. It serves as the central repository for information pertaining to tenancies, which represent the specific leased or subleased locations under a property lease agreement. Each record in this table defines a distinct occupancy arrangement, linking a customer (tenant) to a physical location for a defined term under the financial and legal terms of a master lease. Its role is critical for managing the complete lifecycle of a tenancy, from commencement through termination, and for supporting key processes such as rent billing, expense recovery, and space utilization reporting. The '_ALL' suffix indicates it is a multi-organization table, storing data partitioned by the operating unit (ORG_ID).

Key Information Stored

The table's primary key is TENANCY_ID, a unique system-generated identifier. Its structure is defined by key foreign key relationships that anchor the tenancy within the broader Property Manager data model. The most significant columns include LEASE_ID, which links the tenancy to its governing contract in PN_LEASES_ALL, and LOCATION_ID, which ties it to a physical property location defined in PN_LOCATIONS_ALL. For tenant information, it stores CUSTOMER_ID (linking to HZ_CUST_ACCOUNTS) and CUSTOMER_SITE_USE_ID (linking to HZ_CUST_SITE_USES_ALL) to identify the tenant party and their specific billing site. The LEASE_CHANGE_ID column associates the tenancy with a specific amendment or change document in PN_LEASE_CHANGES_ALL. Additional columns typically track tenancy dates (start, end, termination), status, area, and rental terms.

Common Use Cases and Queries

A primary use case is generating tenant rosters and lease abstracts, which require joining tenancy data to lease, location, and customer details. For billing and accounts receivable integration, queries often join PN_TENANCIES_ALL to customer and site tables to feed invoice generation. Space management reports aggregate tenancy area by location or building. A common analytical query pattern is to list all active tenancies for a given lease:

  • SELECT t.tenancy_id, t.location_id, hca.account_name, t.start_date, t.end_date FROM pn_tenancies_all t, pn_leases_all l, hz_cust_accounts hca WHERE t.lease_id = l.lease_id AND t.customer_id = hca.cust_account_id AND l.lease_num = '&LEASE_NUMBER' AND sysdate BETWEEN t.start_date AND nvl(t.end_date, sysdate+1);

Another frequent scenario involves tracking tenancy history or changes by joining to the PN_TENANCIES_HISTORY table.

Related Objects

PN_TENANCIES_ALL maintains integral relationships with several key tables, as documented by its foreign keys. It is a child of the lease master (PN_LEASES_ALL via LEASE_ID) and lease amendment (PN_LEASE_CHANGES_ALL via LEASE_CHANGE_ID) tables. It references the location master (PN_LOCATIONS_ALL via LOCATION_ID) and Oracle Trading Community Architecture tables for customer data (HZ_CUST_ACCOUNTS via CUSTOMER_ID and HZ_CUST_SITE_USES_ALL via CUSTOMER_SITE_USE_ID). Conversely, it acts as a parent table for tenancy-specific assignment details (PN_SPACE_ASSIGN_CUST_ALL via TENANCY_ID) and for maintaining an audit trail of changes (PN_TENANCIES_HISTORY via TENANCY_ID).