Search Results pn_var_constraints




Overview
Explore in AI Chat

Overview

APPS.PN_VAR_CONSTRAINTS_V is a reporting and integration view within the Oracle E-Business Suite Property Manager (PN) module. Its name reflects its role in exposing variance constraint records — the contractual clauses and financial thresholds that govern lease and property agreements in Oracle Property Manager. The view presents the data held in PN_VAR_CONSTRAINTS in a denormalized form, resolving the foreign key to the agreement template so that the template name (AGREEMENT_TEMPLATE) is available alongside each constraint without requiring an additional join in the calling query.

Because a view rather than a base table is the object of interest, this object is read-only in practice; DML against variance constraints is performed against the underlying PN_VAR_CONSTRAINTS table through the standard Property Manager forms and concurrent programs. The view is owned by APPS and is typically granted to reporting and integration responsibilities, allowing external systems, custom reports, and Oracle Discoverer or BI Publisher datasets to consume variance constraint data without direct access to the base tables.

Underlying Base Objects

According to the documented metadata, the view is defined over two base objects, both referenced through synonyms in the APPS schema:

  • PN_VAR_CONSTRAINTS — the primary table holding variance constraint rows, aliased as CON in the view definition.
  • PN_VAR_TEMPLATES_ALL — the multi-org variance template table, aliased as TMP, which supplies the AGREEMENT_TEMPLATE descriptive column.

The join between the two tables is an outer join: tmp.AGREEMENT_TEMPLATE_ID(+) = con.AGREEMENT_TEMPLATE_ID. This is significant because it guarantees that every row in PN_VAR_CONSTRAINTS is returned even when no matching template exists. Consequently, consumers of this view must tolerate a NULL AGREEMENT_TEMPLATE value. Note also that PN_VAR_TEMPLATES_ALL is a _ALL table, implying a multi-org (ORG_ID) partitioning pattern; even so, the view does not filter by ORG_ID, so it exposes rows across operating units unless the caller supplies an ORG_ID predicate.

Key Columns

Common Use Cases and Queries

Typical uses include auditing the variance thresholds tied to a given agreement template, reporting constraints by category or operating unit, and feeding constraint data into downstream billing or lease administration processes. A representative query listing active constraints for a specific organization might read:

  • SELECT constraint_num, constr_cat_code, type_code, amount, agreement_template, constr_start_date, constr_end_date FROM apps.pn_var_constraints_v WHERE org_id = :p_org_id AND SYSDATE BETWEEN constr_start_date AND constr_end_date ORDER BY constraint_num;
  • SELECT constraint_id, constraint_num, agreement_template FROM apps.pn_var_constraints_v WHERE constr_cat_code = :p_category;

Because the view performs the outer join to PN_VAR_TEMPLATES_ALL, developers should avoid re-joining to the template table in custom SQL, and should filter explicitly on ORG_ID to respect multi-org security. This behaviour is consistent across Oracle EBS 12.1.1 and 12.2.2, where the object definition and base tables are unchanged.