Search Results max_end_date




Overview
Explore in AI Chat

Overview

PN_ADJUSTMENT_DETAILS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Property Manager (PN) product family. It exists to support the Adjustment Details form and its associated inquiry and reporting surfaces. Functionally, the view presents a summarized, grouped projection of adjustment records rather than a row-for-row copy of the underlying detail table. Each row represents one combination of a term history identifier and an adjustment group number, with the individual adjustment lines collapsed into aggregate start date, end date, and monetary totals.

Because the view is a grouping query, it is intended for display and reporting contexts where a consolidated view of adjustment activity is preferable to the raw transactional detail. The term_history_id column is the primary correlation key exposed by the view and links each summarized adjustment group back to the term history record that governs the lease or property term involved. In 12.1.1 and 12.2.2, the object is documented as VALID and carries the standard Oracle proprietary and confidential marking applied to ETRM reference material.

Underlying Base Objects

The view is defined over a single documented base object, PN_ADJUSTMENT_DETAILS, referenced through a synonym. The view text applies a GROUP BY clause on PAD.GROUP_NUM and PAD.TERM_HISTORY_ID, aliasing the base table as PAD. No joins to other tables are present in the documented definition; the view is therefore a pure aggregation layer over PN_ADJUSTMENT_DETAILS.

This has two practical consequences. First, the view cannot be used to retrieve individual adjustment line identifiers, since those columns are removed by the grouping. Second, any filter applied to the view operates on aggregated results, so predicates on date or amount columns test the summarized values rather than the source rows. Consumers requiring line-level detail must query PN_ADJUSTMENT_DETAILS directly.

Key Columns

  • TERM_HISTORY_ID — The term history identifier drawn from the base table. It identifies the term record to which the adjustment group belongs and is the principal join key to term history and lease-related data.
  • GROUP_NUM — The adjustment group number. Together with TERM_HISTORY_ID it forms the grouping key that determines one output row.
  • MIN_START_DATE — The earliest adjustment start date within the group, produced by MIN(PAD.ADJ_START_DATE).
  • MAX_END_DATE — The latest adjustment end date within the group, produced by MAX(PAD.ADJ_END_DATE). The pairing of MIN_START_DATE and MAX_END_DATE yields the effective span covered by the group.
  • ADJUSTMENT_AMOUNT — The sum of adjustment amounts within the group, produced by SUM(PAD.ADJUSTMENT_AMOUNT).

Common Use Cases and Queries

The view is typically used to display consolidated adjustment information on an Adjustment Details form, to populate reports summarizing adjustments by term history, and to feed integrations that require grouped rather than line-level adjustment data. The following query retrieves all summarized groups for a given term history:

  • SELECT term_history_id, group_num, min_start_date, max_end_date, adjustment_amount
  • FROM apps.pn_adjustment_details_v
  • WHERE term_history_id = :p_term_history_id
  • ORDER BY group_num;

Where only the total adjustment value per term history is required, an additional aggregation over the view is appropriate:

  • SELECT term_history_id, SUM(adjustment_amount) total_adjustment
  • FROM apps.pn_adjustment_details_v
  • GROUP BY term_history_id;

Because the view performs aggregation at runtime, queries against it should always constrain TERM_HISTORY_ID or GROUP_NUM where possible to limit the volume of base rows scanned and grouped. For reconciliation or drill-down to individual adjustments, query PN_ADJUSTMENT_DETAILS directly using the same TERM_HISTORY_ID and GROUP_NUM values returned by the view.