Search Results adjustment_summary_id

Overview

The PN_ADJUSTMENT_SUMMARIES table is a core data object within the Oracle E-Business Suite (EBS) Property Manager (PN) module. It serves as the central repository for summary-level information related to lease adjustments. In the context of lease management, adjustments are modifications to standard payment schedules, often for items like operating expenses (OpEx), common area maintenance (CAM), or other recurring charges that require periodic reconciliation and billing. This table acts as a header or control record, aggregating the total calculated adjustment amount for a specific payment term and lease, thereby providing a high-level view of adjustment obligations.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships define its critical structure. The central identifier is the ADJUSTMENT_SUMMARY_ID, a unique primary key. The most significant foreign key is PAYMENT_TERM_ID, which links the adjustment summary to a specific payment schedule line (PN_PAYMENT_TERMS_ALL) for a lease. This connection is fundamental, as it ties the calculated adjustment amount to the specific lease payment term it affects. Other columns typically found in such a summary table would include the total adjustment amount, the currency, the adjustment period or date range, and status flags indicating whether the summary is draft, approved, or invoiced.

Common Use Cases and Queries

The primary use case is reporting and inquiry on lease-related adjustments. Property managers and accountants query this table to review total adjustment liabilities before generating invoices or performing reconciliations. A common SQL pattern retrieves all adjustment summaries for a lease or property within a specific period. For example:

• Identifying all adjustment summaries linked to a particular lease's payment terms for financial accruals.
• Generating a report of pending adjustments that require approval before being passed to Accounts Receivable.
• Troubleshooting by joining to PN_ADJUSTMENT_DETAILS to compare the summary total against the sum of its constituent detail lines.

A typical diagnostic query would join PN_ADJUSTMENT_SUMMARIES to PN_PAYMENT_TERMS_ALL and the PN_LEASES table to provide lease context for all adjustments.

Related Objects

This table is a nexus in the Property Manager adjustment subsystem, with documented relationships to key transactional tables.

• PN_PAYMENT_TERMS_ALL: This is a parent table. Each row in PN_ADJUSTMENT_SUMMARIES references a specific lease payment schedule line via the PAYMENT_TERM_ID foreign key. This defines which payment term the adjustment applies to.
• PN_ADJUSTMENT_DETAILS: This is a child table. The ADJUSTMENT_SUMMARY_ID primary key is referenced as a foreign key in PN_ADJUSTMENT_DETAILS. This one-to-many relationship means a single adjustment summary record aggregates multiple detailed adjustment lines, which contain the granular calculations (e.g., by expense type or square footage).

These relationships form a critical hierarchy: Payment Term -> Adjustment Summary -> Adjustment Details, ensuring traceability from a high-level lease obligation down to the individual calculation components.