Search Results pn_lease_milestones_all




Overview
Explore in AI Chat

Overview

The PN_LEASE_MILESTONES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Property Manager (PN) module. It serves as the central repository for tracking significant, time-bound events associated with a lease agreement. These events, or milestones, are critical for lease administration, financial forecasting, and compliance monitoring. The table's role is to systematically capture the details of these contractual events—such as option exercise dates, rent review dates, or insurance renewal deadlines—and link them to their originating lease document. Its "ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by the operating unit, which is a fundamental design pattern in Oracle EBS to support complex enterprise structures.

Key Information Stored

The table's primary purpose is to define the what, when, and context of a lease milestone. While the full column list is not detailed in the provided metadata, its structure is defined by its primary and foreign keys. The primary identifier is the LEASE_MILESTONE_ID. The most critical foreign key is LEASE_ID, which anchors every milestone to a specific lease record in the PN_LEASES_ALL table. Other key foreign key columns establish the type and origin of the milestone. These include OPTION_ID (linking to PN_OPTIONS_ALL for lease option dates), PAYMENT_TERM_ID (linking to PN_PAYMENT_TERMS_ALL for payment-related events), LEASE_CHANGE_ID (linking to PN_LEASE_CHANGES_ALL), and INSURANCE_REQUIREMENT_ID (linking to PN_INSURANCE_REQUIREMENTS_ALL). Typical data stored would encompass the milestone date, a description, its status (e.g., Pending, Completed), and associated amounts or terms relevant to the event.

Common Use Cases and Queries

This table is essential for proactive lease management and reporting. A primary use case is generating milestone calendars or dashboards to alert property managers of upcoming critical dates. For example, a query to find all option exercise milestones due in the next 90 days for a specific operating unit would join PN_LEASE_MILESTONES_ALL to PN_LEASES_ALL and PN_OPTIONS_ALL. Another common scenario is financial accrual and budgeting, where payment-related milestones (like fixed rent increases) are extracted to project future cash flows. The table is also queried during the lease abstraction process to validate that all contractual events have been captured in the system. A basic reporting pattern involves filtering by milestone date and type:

  • SELECT lm.milestone_date, l.lease_number, l.description FROM pn_lease_milestones_all lm, pn_leases_all l WHERE lm.lease_id = l.lease_id AND lm.milestone_date BETWEEN SYSDATE AND SYSDATE+30 ORDER BY lm.milestone_date;

Related Objects

The PN_LEASE_MILESTONES_ALL table is a central hub connected to several key Property Manager entities via documented foreign key relationships. These relationships define the permissible origins of a milestone record and are crucial for accurate joins in reports and integrations.

  • PN_LEASES_ALL: The foundational parent table. Joined via LEASE_ID to retrieve lease header information (lease number, tenant, property).
  • PN_OPTIONS_ALL: Joined via OPTION_ID for milestones related to lease options like renewal, expansion, or termination.
  • PN_PAYMENT_TERMS_ALL: Joined via PAYMENT_TERM_ID for milestones tied to payment schedule changes or rent escalations.
  • PN_LEASE_CHANGES_ALL: Joined via LEASE_CHANGE_ID for milestones generated by lease amendments or modifications.
  • PN_INSURANCE_REQUIREMENTS_ALL: Joined via INSURANCE_REQUIREMENT_ID for milestones tracking insurance certificate expiration or renewal dates.