Search Results pn_leases_v




Overview
Explore in AI Chat

Overview

PN_LEASES_V is a reporting and integration view in the APPS schema belonging to the PN – Property Manager product within Oracle E-Business Suite. It is a denormalized projection that consolidates lease header information, lease detail records, customer (party) attributes, and descriptive lookup values into a single queryable structure. The view carries a VALID status in both EBS 12.1.1 and 12.2.2 and is defined entirely in PL/SQL independent of the underlying table structures, meaning it does not store data of its own.

Its primary role is to expose lease data in a form suitable for operational reporting, custom concurrent programs, Oracle Reports/BI Publisher layouts, and inbound/outbound integrations that require lease, tenant, and financial account attributes in one fetch. Because the view joins across the lease, lease detail, lease change, and trading community (HZ) tables, it abstracts the relational complexity of the Property Manager data model from report developers and integration consumers.

Underlying Base Objects

The documented metadata lists the following referenced base objects: FND_GLOBAL (package), FND_LOOKUPS (view), FND_USER (synonym), HZ_CUST_ACCOUNTS (synonym), HZ_PARTIES (synonym), PNP_UTIL_FUNC (package), PN_LEASES (synonym), PN_LEASES_ALL (synonym), PN_LEASE_CHANGES_ALL (synonym), PN_LEASE_DETAILS_ALL (synonym), and PN_PAY_GROUP_RULES (synonym).

Key Columns

  • LEASE_ID, LEASE_DETAIL_ID, LEASE_CHANGE_ID — primary and foreign key identifiers linking lease, detail, and change records.
  • LEASE_NAME, LEASE_NUMBER — the lease NAME and LEASE_NUM display values.
  • LEASE_TYPE_CODE, LEASE_CLASS_CODE, LEASE_TYPE — classification codes plus the decoded LEASE_TYPE meaning from FND_LOOKUPS.
  • STATUS, LEASE_STATUS — lease workflow and lifecycle status indicators.
  • CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — tenant identifiers resolved from HZ_PARTIES and HZ_CUST_ACCOUNTS.
  • LEASE_COMMENCEMENT_DATE, LEASE_TERMINATION_DATE — the core lease period boundaries.
  • LEASE_TERM — computed as TRUNC(LEASE_TERMINATION_DATE) - TRUNC(LEASE_COMMENCEMENT_DATE) + 1, giving an inclusive day count for the lease.
  • LEASE_EXECUTION_DATE, LEASE_EXTENSION_END_DATE — execution and extension milestones.
  • EXPENSE_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, RECEIVABLE_ACCOUNT_ID, TERM_TEMPLATE_ID — accounting and term configuration references.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield columns carried through from the lease detail.
  • USER_ABSTRACTED, USER_RESPONSIBLE — user names for abstraction and responsibility ownership.

Common Use Cases and Queries

Typical scenarios include lease portfolio reporting, tenant billing reconciliation, lease-term aging analysis, and integration extracts that feed downstream accounting or facilities systems. A common selection pattern joins lease summaries with the decoded customer name and computed term:

  • Active lease register: SELECT LEASE_NUMBER, LEASE_NAME, CUSTOMER_NAME, LEASE_TYPE, LEASE_COMMENCEMENT_DATE, LEASE_TERMINATION_DATE, LEASE_TERM FROM APPS.PN_LEASES_V WHERE LEASE_STATUS = 'ACTIVE' ORDER BY LEASE_TERMINATION_DATE;
  • Tenant-based extraction: SELECT LEASE_ID, LEASE_DETAIL_ID, LEASE_NUMBER, CUSTOMER_NUMBER, CUSTOMER_NAME, RESPONSIBLE_USER, USER_RESPONSIBLE FROM APPS.PN_LEASES_V WHERE CUSTOMER_ID = :p_customer_id;
  • Expiring leases within 90 days: SELECT LEASE_NUMBER, CUSTOMER_NAME, LEASE_TERMINATION_DATE, LEASE_TERM FROM APPS.PN_LEASES_V WHERE LEASE_TERMINATION_DATE BETWEEN SYSDATE AND SYSDATE+90;

Because the view spans multiple base objects, queries should filter aggressively on indexed columns such as LEASE_ID, CUSTOMER_ID, or LEASE_STATUS to maintain performance on large lease portfolios. Consumers should treat the view as read-only and validate joins against PN_LEASES_ALL and PN_LEASE_DETAILS_ALL where row-level security or configuration semantics are decisive.