Search Results amend_name




Overview
Explore in AI Chat

Overview

PN_TERM_HISTORY_HEADER_V is a form-driven database view owned by the APPS schema in Oracle E-Business Suite, defined within the Property Manager (PN) product family. Its documented role is as the Term History Header Form View, meaning it is the queryable data source that backs the Term History header block on the Property Manager payment terms and lease change forms. Rather than storing data, the view consolidates lease change information from PN_LEASE_CHANGES_ALL with the historical payment term snapshots held in PN_PAYMENT_TERMS_HISTORY, enriching each row with descriptive attributes from PN_LEASES_ALL, PN_PAYMENT_TERMS_ALL, FND_LOOKUPS and FND_USER.

Because the view surfaces CHANGE_COMMENCEMENT_DATE, CHANGE_TERMINATION_DATE and CHANGE_EXECUTION_DATE directly from the lease change record, it is frequently targeted by reporting and integration queries that need to reconstruct how a lease's payment terms evolved over time, and specifically when a given change became effective. The view exists in both Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 metadata confirming a VALID status and the same column projection.

Underlying Base Objects

The view is defined over a join of six documented base objects, using Oracle's outer-join syntax for the lookup and user joins:

All PN base objects are accessed through APPS synonyms, and the view is secure with respect to operating unit through the ORG_ID exposed from PN_PAYMENT_TERMS_ALL.

Key Columns

  • TERM_HISTORY_ID — primary history row identifier; the join key back to PN_PAYMENT_TERMS_HISTORY.
  • PAYMENT_TERM_ID / LEASE_CHANGE_ID / PREV_TERM_HISTORY_ID — links to the payment term, the initiating lease change, and the prior history row respectively.
  • CHANGE_TYPE_LOOKUP_CODE and CHANGE_TYPE — coded and translated lease change type, sourced from FND_LOOKUPS.
  • CHANGE_DATE, CREATED_BY, USER_RESPONSIBLE — creation timestamp and the user who performed the change.
  • AMEND_NAME — the lease change name, suppressed to NULL when the change is an 'EDIT'.
  • CHANGE_COMMENCEMENT_DATE — the effective start date of the change, one of the three principal date columns.
  • CHANGE_TERMINATION_DATE / CHANGE_EXECUTION_DATE — effective end date and the date the change was executed.
  • TOTAL_ADJ_AMOUNT — total adjustment amount associated with the history row.
  • ORG_ID, LEASE_ID, LEASE_NAME, LEASE_NUMBER — operating unit and lease identification attributes.

Common Use Cases and Queries

The view is most often queried to audit term changes for a lease or to feed downstream reporting and integrations that need commencement, termination and execution dates. A typical query retrieving the change timeline for a lease is:

  • SELECT lease_number, lease_name, change_type, change_commencement_date, change_termination_date, total_adj_amount FROM pn_term_history_header_v WHERE lease_number = :p_lease_number ORDER BY change_commencement_date DESC;
  • SELECT term_history_id, change_commencement_date, change_execution_date, user_responsible FROM pn_term_history_header_v WHERE org_id = :p_org_id AND change_commencement_date BETWEEN :p_from AND :p_to;
  • SELECT lease_id, amend_name, change_type FROM pn_term_history_header_v WHERE lease_change_id = :p_lease_change_id;

Because the view exposes ORG_ID, reports should always filter by operating unit to respect multi-org security. Matching on CASE and the stored dates (which are DATE datatypes) ensures correct ordering and range filtering.