Search Results pn_insurance_requirements_all




Overview
Explore in AI Chat

Overview

The PN_INSURANCE_REQUIREMENTS_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 storing and managing all insurance policy requirements stipulated within lease agreements. This table is essential for tracking the contractual obligations of both lessors and lessees regarding insurance coverage, such as liability, property, and casualty insurance. Its role is critical for ensuring lease compliance, managing risk exposure, and facilitating the audit and renewal of insurance policies throughout the lease lifecycle. As a multi-organization enabled table (indicated by the "_ALL" suffix), it stores data across all operating units, making it integral to global lease portfolio management in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is INSURANCE_REQUIREMENT_ID, which uniquely identifies each insurance requirement record. The most significant foreign key is LEASE_ID, which links the requirement to a specific lease in the PN_LEASES_ALL table. Another key column is LEASE_CHANGE_ID, linking the requirement to a specific lease amendment or change document in PN_LEASE_CHANGES_ALL. While the full column list is not detailed in the provided metadata, typical columns in such a table would include data points for the insurance type (e.g., General Liability, Property), the required coverage amount, the policy expiration date, the responsible party (Lessor/Lessee), certificate holder information, and status flags. The table also likely contains standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is primarily used for compliance reporting and lease administration. Common business scenarios include generating reports of all leases with insurance policies expiring within a certain period to proactively manage renewals, identifying leases where a tenant's provided certificate of insurance is deficient, and assessing aggregate risk exposure across a property portfolio. A typical query would join PN_INSURANCE_REQUIREMENTS_ALL to PN_LEASES_ALL to list requirements for a specific lease or property.

  • Sample Query for Upcoming Expirations:
    SELECT l.lease_number, ir.insurance_type, ir.coverage_amount, ir.expiration_date
    FROM pn_insurance_requirements_all ir, pn_leases_all l
    WHERE ir.lease_id = l.lease_id
    AND ir.expiration_date BETWEEN SYSDATE AND SYSDATE + 90
    AND l.org_id = :p_org_id;
  • Reporting Use Case: Creating a "Proof of Insurance" tracking report to ensure all active leases have current, compliant certificates on file, often by joining to history or document tables.

Related Objects

As indicated by the foreign key relationships, PN_INSURANCE_REQUIREMENTS_ALL is centrally connected to several key Property Manager tables.

  • PN_LEASES_ALL: The primary parent table. Every insurance requirement must be associated with a lease.
  • PN_LEASE_CHANGES_ALL: Tracks which lease amendment introduced or modified a specific insurance requirement.
  • PN_INSUR_REQUIRE_HISTORY: Likely stores a historical audit trail of changes made to each requirement record, with a foreign key back to INSURANCE_REQUIREMENT_ID.
  • PN_LEASE_MILESTONES_ALL: Used to schedule and track critical dates related to insurance requirements, such as renewal deadlines or certificate submission dates, linking them to the base requirement.