Search Results pn_payment_terms_v




Overview
Explore in AI Chat

Overview

PN_PAYMENT_TERMS_V is a form-driven database view owned by the APPS schema in Oracle E-Business Suite, and it is documented as VALID across the 12.1.1 and 12.2.2 releases. It belongs to the Property Manager (PN) product family and serves as the presentation-layer view that a Payment Terms form uses to enter and maintain payment term information for leases, operating expense (OPEX) agreements, and recovery agreements. The view is not a standalone reporting object by design; it is the interface that the PN payment terms form reads from and writes to, exposing the columns the form requires for currency, schedule, tax, and reference attributes.

For reporting and integration purposes, PN_PAYMENT_TERMS_V provides a denormalized read point over the underlying PN_PAYMENT_TERMS synonym, resolving selected payment-purpose, frequency, lease, vendor, customer, and accounting flexfield values so that a query against the view returns a form-ready record set.

Underlying Base Objects

The documented base objects include the base table synonym PN_PAYMENT_TERMS, which supplies the primary rows and most columns. Supporting PN objects include PN_LEASES_ALL, PN_OPEX_AGREEMENTS_ALL, PN_OPEX_RECON_ALL, PN_REC_AGREEMENTS_ALL, PN_REC_AGR_LINES_ALL, PN_TERM_TEMPLATES_ALL, and PN_PAY_GROUP_RULES, providing lease and agreement context and term templates. Supplier references resolve through PO_VENDORS and PO_VENDOR_SITES_ALL, while customer references resolve through HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES. Value translation uses FND_LOOKUPS and the package FND_GLOBAL, and logic is encapsulated in the packages PNT_PAYMENT_TERMS_PKG and PNP_UTIL_FUNC, both of which contribute decoded and derived values to the view text.

Key Columns

Common Use Cases and Queries

Typical usage includes extracting payment terms for a specific lease, reconciling estimated against actual amounts, and validating currency and rate values for downstream AP/AR processing. A representative query is:

SELECT payment_term_id, lease_id, payment_purpose_code,
       frequency_code, start_date, end_date,
       estimated_amount, actual_amount, currency_code
FROM   apps.pn_payment_terms_v
WHERE  lease_id = :lease_id
AND    end_date >= SYSDATE;

Investigate supplier or customer association by filtering on VENDOR_ID/CUSTOMER_ID, or join the view back to PN_LEASES_ALL on LEASE_ID to obtain lease attributes not exposed directly by the view. Because the view is form-oriented and built partly from package logic (PNT_PAYMENT_TERMS_PKG, PNP_UTIL_FUNC), integrations should query the base PN_PAYMENT_TERMS table directly when only persisted columns are required.