Search Results interface_line_attribute6

Overview

The PN_PAYMENT_TERMS_HISTORY_V view is a Property Manager (PN) reporting and forms-support object owned by the APPS schema. It is documented as the "Term History Form View," indicating that it is the query layer used by the Payment Terms History form to present historical payment term records associated with leases and lease changes. The view projects column-for-column from the PN_PAYMENT_TERMS_HISTORY table, exposing term history identity, distribution change linkage, payment term details, schedule attributes, amounts, currency information, and the full 15-column ATTRIBUTE descriptive flexfield (DFF) block.

Its role in Oracle EBS 12.1.1 and 12.2.2 is primarily that of a reporting and integration surface. Because it consolidates the term history base with joined lookup, party, vendor, lease, template, and payment group rule objects, it eliminates the need for ad hoc joins in custom reports, business intelligence extracts, and downstream integrations that consume lease payment term history. When users search for interface_line_attribute14 in connection with this object, the typical interpretation is the DFF segment mapped on the payment terms history record, since the view exposes ATTRIBUTE14 natively; the interface_line_attribute naming convention instead belongs to the lease/payment interface tables that feed this history.

Underlying Base Objects

The documented referenced base objects are:

• PN_PAYMENT_TERMS_HISTORY (synonym) — the primary transactional base for the view; the view text is a direct projection of this table.
• PN_LEASES_ALL (synonym) — lease header information, used to resolve lease context for the history rows.
• PN_PAY_GROUP_RULES (synonym) — payment group rule definitions tied to payment purposes.
• PN_TERM_TEMPLATES_ALL (synonym) — term template defaults for payment terms.
• HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES (synonyms) — Trading Community Architecture customer and party data for customer-side terms.
• PO_VENDORS, PO_VENDOR_SITES_ALL (views) — supplier and supplier site information for vendor-side terms.
• FND_LOOKUPS (view) — validation of lookup codes such as payment purpose and frequency.
• FND_GLOBAL, PNP_UTIL_FUNC (packages) — session context and Property Manager utility functions.

The combination shows the view is designed to resolve codes to meaningful values and to bring customer, vendor, lease, template, and rule context together for the history form.

Key Columns

• TERM_HISTORY_ID / PREV_TERM_HISTORY_ID — primary key and self-referencing pointer for the version chain.
• DISTRIBUTION_CHANGE_ID — links the term history record to the distribution change that generated it.
• PAYMENT_TERM_ID, PAYMENT_PURPOSE_CODE, PAYMENT_TERM_TYPE_CODE, FREQUENCY_CODE — the term definition and its classification.
• LEASE_ID, LEASE_CHANGE_ID — the lease and lease change context.
• START_DATE, END_DATE, TARGET_DATE, SCHEDULE_DAY — the timing and scheduling attributes of the term.
• ACTUAL_AMOUNT, ESTIMATED_AMOUNT, CURRENCY_CODE, RATE, SET_OF_BOOKS_ID — financial values and the set of books against which they are tracked.
• VENDOR_ID, VENDOR_SITE_ID, CUSTOMER_ID, CUSTOMER_SITE_USE_ID, CUST_SHIP_SITE_ID — the payee/payer and site identifiers.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..ATTRIBUTE15 — the DFF block, where ATTRIBUTE14 is the fourteenth free descriptive segment.
• AP_AR_TERM_ID, CUST_TRX_TYPE_ID, PROJECT_ID, TASK_ID, ORGANIZATION_ID, EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE, TAX_GROUP_ID, TAX_CODE_ID, TAX_INCLUDED — integration and accounting attributes for downstream Payables, Receivables, and Projects processing.

Common Use Cases and Queries

Typical uses include auditing the payment term change history for a lease, reconciling estimated versus actual amounts per term, extracting DFF values (including ATTRIBUTE14) for downstream systems, and feeding integration processes that require a flattened term history row.

A representative query retrieving term history with the fourteenth attribute segment is:

• SELECT term_history_id, lease_id, payment_term_id, payment_purpose_code, frequency_code, start_date, end_date, actual_amount, estimated_amount, currency_code, attribute_category, attribute14 FROM apps.pn_payment_terms_history_v WHERE lease_id = :p_lease_id ORDER BY start_date;

To trace a specific DFF value across leases, filter on the attribute directly:

• SELECT term_history_id, lease_id, payment_term_id, attribute14 FROM apps.pn_payment_terms_history_v WHERE attribute14 = :p_value;

The view should be treated as read-only; all maintenance of term history is performed through the Property Manager forms against the base PN_PAYMENT_TERMS_HISTORY table.