Search Results payment_term_type




Overview
Explore in AI Chat

Overview

The APPS.PN_VAR_TERMS_V view is a form-driven database object within the Oracle E-Business Suite PN – Property Manager module. Its documented purpose is to expose abatement details associated with variable rent invoices, allowing the Property Manager forms to display and validate payment-term level information alongside vendor, customer, and lease context. The view is VALID and owned by the APPS schema, and is queryable in both EBS 12.1.1 and 12.2.2.

Functionally, the view joins payment terms to variable rent invoices and enriches each row with decoded lookup meanings, supplier details, customer/party information, and a computed flag indicating whether a term exists for the given invoice. This makes it well suited for reporting, form blocks, and lightweight integration extracts where term-level abatement visibility is required without navigating multiple base tables.

Underlying Base Objects

The documented referenced base objects include both tables and supporting lookups:

Key Columns

Common Use Cases and Queries

Typical scenarios include reconciling abatement terms against variable rent invoices, driving Property Manager form blocks, and producing term-level extracts filtered by lease, period, or organization.

Example — active terms for a lease:

SELECT payment_term_id, lease_id, start_date, end_date, payment_term_type, actual_amount
FROM apps.pn_var_terms_v
WHERE lease_id = :p_lease_id
AND sysdate BETWEEN start_date AND end_date;

Example — terms grouped by start date ("grp_start_date"):

SELECT TRUNC(start_date) grp_start_date, COUNT(*) term_count, SUM(actual_amount) total_actual
FROM apps.pn_var_terms_v
WHERE org_id = :p_org_id
AND include_term = 'Y'
GROUP BY TRUNC(start_date)
ORDER BY grp_start_date;

Example — invoice abatement detail:

SELECT invoice_date, var_rent_inv_id, payment_purpose, vendor_name, customer_name, estimated_amount
FROM apps.pn_var_terms_v
WHERE var_rent_inv_id = :p_invoice_id;

Because several joins are outer joins, results may contain NULL vendor or customer fields; consumers should account for this in reporting and integration logic. Access is granted through the APPS schema, and runtime context is supported via FND_GLOBAL.