Search Results recovery_space_std_code




Overview
Explore in AI Chat

Overview

PN_TENANCIES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Property Manager (PN) module. It exposes tenant occupancy records — the link between a lease, a physical location, and a customer (tenant) — at a granularity that is convenient for inquiry, reporting, and downstream integration. In EBS 12.1.1 and 12.2.2 the object has a status of VALID and is defined as a view rather than a table, so no storage or DDL maintenance is required on the customer side; it is a read-only projection of the underlying tenancies data.

The view's principal value is denormalization. Where the base tenancy table stores lookup codes and foreign keys, PN_TENANCIES_V resolves those codes into descriptive meanings and joins to Oracle Receivables and Trading Community (HZ) entities to present the customer name and account number directly. This makes the view suitable for operational reports, dashboards, and interface extracts without requiring the consumer to re-implement the lookup and party joins.

Underlying Base Objects

The documented base objects referenced by the view are:

  • PN_TENANCIES (synonym) — the primary source of tenancy rows, supplying lease, location, status, area, and attribute columns.
  • PN_LOCATIONS_ALL (synonym) — the Property Manager location/space table, providing the physical space context.
  • HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL (synonyms) — Trading Community and Receivables entities used to resolve the tenant's party name, account number, and site use.
  • FND_LOOKUPS (view) — the lookup source joined to translate tenancy usage, recovery type, and recovery space standard codes into their meanings.
  • FND_GLOBAL (package) and PN_TENANCIES_PKG (package) — supporting program units referenced by the view definition.

Because the view is built from these objects, its output reflects the current state of the underlying tenancy and location records at query time, consistent with standard EBS view behavior.

Key Columns

Common Use Cases and Queries

Typical uses include tenancy occupancy reports, tenant-by-location listings, lease expiration analysis, and expense recovery inputs. The following extracts illustrate practical access patterns.

  • Active tenancies for a lease: SELECT tenancy_id, location_id, customer_name, occupancy_date, expiration_date FROM pn_tenancies_v WHERE lease_id = :lease_id AND status = 'ACTIVE';
  • Tenant listing by customer: SELECT tenancy_id, customer_number, customer_name, tenancy_usage_type, tenants_proportionate_share FROM pn_tenancies_v WHERE customer_id = :customer_id;
  • Expiring tenancies within a period: SELECT tenancy_id, customer_name, expiration_date FROM pn_tenancies_v WHERE expiration_date BETWEEN :from_date AND :to_date ORDER BY expiration_date;
  • Recovery analysis: SELECT tenancy_id, recovery_type, recovery_space_std, tenants_proportionate_share FROM pn_tenancies_v WHERE recovery_type_code IS NOT NULL;

Consumers should treat the view as read-only and rely on the decoded meaning columns for reporting, while using the underlying code columns for filtered interfaces.