Search Results pn_landlord_service_history




Overview
Explore in AI Chat

Overview

The PN_LANDLORD_SERVICE_HISTORY table is a core transactional entity within the Oracle E-Business Suite Property Manager (PN) module. Its primary function is to serve as an audit and historical tracking mechanism for changes to landlord-provided services associated with a lease. When a service obligation, such as maintenance, utilities, or other amenities detailed in a lease agreement, is created, modified, or terminated, this table records a historical entry. This ensures a complete, time-stamped audit trail of the service's lifecycle, which is critical for lease administration, compliance reporting, and resolving tenant-landlord disputes regarding service obligations over the term of a lease.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key relationships and the table's purpose define its critical data elements. Each record is uniquely identified by the LANDLORD_SERVICE_HISTORY_ID (the primary key). The table stores the foreign key LANDLORD_SERVICE_ID, which links each history entry to its master service definition in the PN_LANDLORD_SERVICES_ALL table. The LEASE_ID column anchors the history to the specific lease in PN_LEASES_ALL. Crucially, the LEASE_CHANGE_ID column links the service change to a formal lease amendment or modification event recorded in PN_LEASE_CHANGES_ALL, providing context for why the service was altered. Typical data would also include effective start and end dates for the service change, the type of change (e.g., NEW, UPDATE, TERMINATE), and the user or process that initiated the change.

Common Use Cases and Queries

This table is essential for generating historical reports on service obligations. A common use case is auditing all changes to landlord services for a specific lease, often for lease abstraction reconciliation or during a tenant audit. Another scenario involves analyzing the cost impact of service changes over time. A typical query would join to the lease and service tables to provide context.

  • Service Change Audit Report: SELECT lsh.*, ls.service_name, l.lease_num FROM pn_landlord_service_history lsh, pn_landlord_services_all ls, pn_leases_all l WHERE lsh.landlord_service_id = ls.landlord_service_id AND lsh.lease_id = l.lease_id AND l.lease_id = :p_lease_id ORDER BY lsh.effective_start_date;
  • Identifying Services Active During a Period: Queries often filter on effective date columns to determine which service terms were applicable at a given point in time, which is vital for accurate financial accruals and chargebacks.

Related Objects

The PN_LANDLORD_SERVICE_HISTORY table is centrally connected to other major Property Manager entities through its documented foreign keys.

  • PN_LANDLORD_SERVICES_ALL: Joined via LANDLORD_SERVICE_ID. This is the master definition table for the service itself, containing details like service type, description, and cost basis.
  • PN_LEASES_ALL: Joined via LEASE_ID. This is the core lease table, providing the contractual context for the service obligation.
  • PN_LEASE_CHANGES_ALL: Joined via LEASE_CHANGE_ID. This relationship formally ties a service modification to a specific lease amendment or change document, providing an audit trail to the business process that authorized the update.