Search Results pn_landlord_services_all




Overview
Explore in AI Chat

Overview

The PN_LANDLORD_SERVICES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary transactional repository for recording and managing services that a landlord (or property owner) is contractually obligated to provide to a tenant as part of a lease agreement. This table is central to tracking service obligations, which are critical components of lease administration, financial forecasting, and tenant relationship management. As an "_ALL" table, it is designed to support multi-organization architecture (Multi-Org), meaning it stores data partitioned by the operating unit, allowing a single installation to manage data for multiple legal entities or business units.

Key Information Stored

The table stores detailed records for each landlord-provided service. While the full column list is not provided in the excerpt, the documented primary and foreign keys reveal its essential structure. The primary key, LANDLORD_SERVICE_ID, uniquely identifies each service record. The LEASE_ID column is a critical foreign key that links the service to a specific lease in the PN_LEASES_ALL table, anchoring the obligation to a master agreement. The LEASE_CHANGE_ID foreign key links the service to an amendment or modification recorded in PN_LEASE_CHANGES_ALL, enabling the tracking of how service terms evolve over the lease lifecycle. Other typical columns in such a table would include service type, description, responsibility details, frequency, cost basis, and start/end dates, all scoped by the ORG_ID for Multi-Org integrity.

Common Use Cases and Queries

This table is primarily accessed for lease administration, audit, and reporting. Common operational use cases include generating a schedule of landlord obligations for a specific lease, calculating potential landlord liability for service costs, and validating lease abstracts. For reporting, it is often joined to lease and property tables to assess portfolio-wide service commitments. A typical query pattern involves selecting services for a lease, often joining to related history or detail tables:

  • SELECT * FROM pn_landlord_services_all WHERE lease_id = <lease_id> ORDER BY start_date;
  • SELECT l.lease_num, s.service_type, s.description FROM pn_landlord_services_all s, pn_leases_all l WHERE s.lease_id = l.lease_id AND l.property_id = <property_id>;

Data from this table feeds into calculations for operating expense reconciliations and common area maintenance (CAM) charges, where landlord-provided services impact pass-through costs to tenants.

Related Objects

The PN_LANDLORD_SERVICES_ALL table is integral to the Property Manager data model, with documented relationships to several key tables. The primary key (LANDLORD_SERVICE_ID) is referenced by the PN_LANDLORD_SERVICE_HISTORY table, which likely tracks changes to the service terms over time. The table has two primary foreign key dependencies:

  • PN_LEASES_ALL: Joined via PN_LANDLORD_SERVICES_ALL.LEASE_ID = PN_LEASES_ALL.LEASE_ID. This links every service to its governing lease agreement.
  • PN_LEASE_CHANGES_ALL: Joined via PN_LANDLORD_SERVICES_ALL.LEASE_CHANGE_ID = PN_LEASE_CHANGES_ALL.LEASE_CHANGE_ID. This associates the service record with a specific lease amendment or change document that introduced or modified it.

These relationships ensure data integrity and enable comprehensive reporting across the lease lifecycle, from the original agreement (PN_LEASES_ALL) through amendments (PN_LEASE_CHANGES_ALL) and detailed service history (PN_LANDLORD_SERVICE_HISTORY).