Search Results adjustment_detail_id

Overview

The PN_ADJUSTMENT_DETAILS table is a core data object within the Property Manager (PN) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the transactional repository for the detailed line items of a lease adjustment. An adjustment in Property Manager is a financial transaction that modifies the accounting and payment schedule for a lease, typically to correct errors, account for lease modifications, or handle one-time charges or credits. This table stores the granular, period-by-period impact of an approved adjustment, linking the high-level adjustment summary to the specific payment terms and payment items it affects. Its existence is critical for maintaining an accurate and auditable history of all changes to a lease's financial obligations.

Key Information Stored

While the full column list is not provided in the metadata, the documented foreign key relationships and primary key define its essential structure. The primary key, ADJUSTMENT_DETAIL_ID, uniquely identifies each adjustment line. The table's core function is to associate an adjustment with the specific lease payment components it modifies. This is achieved through three critical foreign key columns: ADJUSTMENT_SUMMARY_ID links the detail line to its parent header record in the PN_ADJUSTMENT_SUMMARIES table. TERM_HISTORY_ID connects the detail to a specific payment term history record in PN_PAYMENT_TERMS_HISTORY, which holds the schedule of payments. PAYMENT_ITEM_ID references the individual payment item in PN_PAYMENT_ITEMS_ALL that is being adjusted. Typical data stored would also include the adjusted monetary amount, the accounting period affected, and the type of adjustment being applied.

Common Use Cases and Queries

This table is central to inquiries and reports concerning lease financial adjustments. A common use case is tracing the complete downstream impact of an adjustment. For instance, to audit all adjustments made to a specific lease payment schedule, one would join from PN_PAYMENT_TERMS_HISTORY to PN_ADJUSTMENT_DETAILS. Another critical scenario is generating reports for period-end reconciliation, showing all adjustment details posted within a specific accounting period. A sample query pattern to list adjustment details for a given adjustment summary would be:

• SELECT d.adjustment_detail_id, d.term_history_id, d.payment_item_id, p.amount FROM pn_adjustment_details d, pn_payment_items_all p WHERE d.adjustment_summary_id = :p_summary_id AND d.payment_item_id = p.payment_item_id;

This table is also fundamental for any custom interfaces or extensions that need to read or validate the detailed results of the adjustment posting process.

Related Objects

As defined by its foreign keys, PN_ADJUSTMENT_DETAILS has direct and integral relationships with several key Property Manager tables. Its parent object is the PN_ADJUSTMENT_SUMMARIES table, which holds the header-level information such as adjustment number, date, and status. It is a child to PN_PAYMENT_TERMS_HISTORY, which stores the historical versions of payment terms for a lease. Most importantly, it directly modifies individual PN_PAYMENT_ITEMS_ALL records, which are the atomic payment schedule entries used for billing and accounting. In practice, workflows and APIs that create or process adjustments, such as the lease adjustment form, will heavily interact with this table to create and update these detail records.