Search Results min_start_date




Overview
Explore in AI Chat

Overview

The Oracle EBS view APPS.PN_ADJUSTMENT_DETAILS_V is an aggregation view that summarizes payment adjustment detail records held in the Oracle Property Manager (PN) module. Rather than exposing the individual adjustment rows stored at the transaction level, this view consolidates them into a single row per combination of GROUP_NUM and TERM_HISTORY_ID. It is a read-only reporting object, typically used to present the effective span and net amount of a group of adjustments in a single summarized line.

The view plays a supporting role in reporting and integration. Because it collapses many adjustment rows into a single consolidated record, it is well suited to inquiries and extracts that need to display the overall start date, end date, and total adjustment amount for a group without processing each constituent detail row. It is commonly referenced in the context of lease/term adjustment analysis within Oracle Property Manager.

Underlying Base Objects

The view is owned by the APPS schema and is defined over a single referenced base object: the synonym PN_ADJUSTMENT_DETAILS. In practice this synonym resolves to the underlying PN_ADJUSTMENT_DETAILS table that stores the granular adjustment records.

The view definition is an aggregate query that applies the following operations against the base table:

  • MIN(pad.adj_start_date) aggregated into MIN_START_DATE — the earliest adjustment start date within the group.
  • MAX(pad.adj_end_date) aggregated into MAX_END_DATE — the latest adjustment end date within the group.
  • SUM(pad.adjustment_amount) aggregated into ADJUSTMENT_AMOUNT — the total adjustment amount for the group.

The rows are grouped by pad.group_num and pad.term_history_id, with term_history_id and group_num carried through as non-aggregated grouping columns. This structure means the view is fully derived from PN_ADJUSTMENT_DETAILS and introduces no additional tables or joins.

Key Columns

The view exposes five columns, all sourced from PN_ADJUSTMENT_DETAILS:

  • TERM_HISTORY_ID — Identifier linking the adjustment group to the associated term history record; a grouping key in the view.
  • GROUP_NUM — The group number that partitions the underlying adjustment details; the second grouping key.
  • MIN_START_DATE — The minimum (earliest) ADJ_START_DATE across all rows in the group. This is the column most relevant to searches involving min_start_date.
  • MAX_END_DATE — The maximum (latest) ADJ_END_DATE across all rows in the group.
  • ADJUSTMENT_AMOUNT — The sum of ADJUSTMENT_AMOUNT for all detail rows in the group.

Because MIN_START_DATE is an aggregate, it represents the effective earliest start of an adjustment group rather than the start date of any single detail record.

Common Use Cases and Queries

Typical use cases include summarizing adjustment activity by term history and group, identifying the effective period covered by a set of adjustments, and totalling adjustment amounts for reporting. A representative query filtering on the aggregated start date is:

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

Because MIN_START_DATE is an aggregate expression, filtering on it in the WHERE clause is valid here since the column is exposed directly by the view. Users performing date-based searches, such as for min_start_date, should note that only the earliest start date within each group is returned. To retrieve the full detail behind any group, query the base PN_ADJUSTMENT_DETAILS table using the corresponding GROUP_NUM and TERM_HISTORY_ID.