Results for “distribution_change_id”

30 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_PAYMENT_TERMS_HISTORY is a table in the PN (Property Manager) schema of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its official description is "Term History table." It records the historical and effective-dated states of payment term definitions associated with leases, lease changes, and distribution changes processed by Oracle Property Manager. Where PN_PAYMENT_TERMS_ALL stores the current definition of a lease payment term, PN_PAYMENT_TERMS_HISTORY preserves the versioned trail of those terms as leases are amended, adjusted, indexed, or re-billed.

The table is owned by the PN schema and is marked VALID. The physical schema documented for 12.2.2 comprises 103 columns. The primary key is PN_PAYMENT_TERMS_HISTORY_PK, defined on TERM_HISTORY_ID. A unique index, PN_PAYMENT_TERMS_HISTORY_U1, is also defined on TERM_HISTORY_ID. Based on the foreign key structure, the heuristic Data Vault classification for this object is satellite-leaning: it holds descriptive, time-variant attributes keyed by a surrogate identifier and dependent on parent lease and payment term hubs rather than acting as a hub or link itself. This classification is a modeling suggestion, not a mandated Oracle construct.

Key Information Stored

The most significant columns fall into several functional groups.

Standard who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and multi-org/legal entity identifiers (ORG_ID, LEGAL_ENTITY_ID) are present for audit and organization security.

Common Use Cases and Queries

The table is primarily queried for term amendment history, audit trails, and re-billing analysis. A typical pattern joins the history to its parent term and lease to reconstruct the term lifecycle.

SELECT h.TERM_HISTORY_ID, h.PAYMENT_TERM_ID, h.LEASE_ID, h.START_DATE, h.END_DATE, h.PAYMENT_TERM_TYPE_CODE, h.ACTUAL_AMOUNT, h.STATUS FROM PN.PN_PAYMENT_TERMS_HISTORY h WHERE h.LEASE_ID = :lease_id ORDER BY h.START_DATE;

To trace successive versions of a single term, the chain through PREV_TERM_HISTORY_ID is followed:

SELECT TERM_HISTORY_ID, PREV_TERM_HISTORY_ID, START_DATE, END_DATE, ESTIMATED_AMOUNT, ACTUAL_AMOUNT FROM PN.PN_PAYMENT_TERMS_HISTORY WHERE PAYMENT_TERM_ID = :payment_term_id ORDER BY START_DATE;

Reporting use cases include reconciliation of estimated versus actual amounts across amendments, validation of index-based rent adjustments via INDEX_PERIOD_ID, and analysis of variable rent billing through VAR_RENT_INV_ID. Adjustments applied to a term can be retrieved by joining PN_ADJUSTMENT_DETAILS on TERM_HISTORY_ID.

Related Objects