Search Results pn_var_constraints_v




Overview
Explore in AI Chat

Overview

PN_VAR_CONSTRAINTS_V is a documented Oracle E-Business Suite view owned by the APPS schema within the Property Manager (PN) product family. Its status is VALID in both ETRM 12.1.1 and 12.2.2. The view is described as a "form view used to input constraints related information," which indicates that it functions as a presentation-layer object supporting an Oracle Forms-based user interface rather than as a standalone reporting entity. In the Property Manager module, constraints represent defined limitations or conditions tied to variance periods used in the valuation and revaluation of property assets. This view exposes the constraint records maintained through the application form, allowing the form block to query, insert, and update constraint data against the underlying tables.

Because the view is built directly over the base constraint and period tables, it also serves reporting and integration purposes. Customers and integrators frequently query such views to extract constraint configurations for reconciliation, audit, or interface scripts, since they provide a convenient denormalized access point that joins period context to each constraint record.

Underlying Base Objects

The view text joins two sources. The first is PN_VAR_CONSTRAINTS, aliased as CON, which is the primary table holding the constraint records. The second is PN_VAR_PERIODS, aliased as PER, which supplies period-level context. The join predicate is PER.PERIOD_ID = CON.PERIOD_ID, an inner join that returns only constraints attached to a valid period. Documented metadata for ETRM 12.2.2 lists referenced base objects as PN_VAR_CONSTRAINTS and PN_VAR_TEMPLATES_ALL, both exposed as synonyms. The presence of PN_VAR_TEMPLATES_ALL suggests the view participates in the constraint template mechanism used to standardize constraint definitions across variance periods. All selected columns, with the exception of ROW_ID, originate from PN_VAR_CONSTRAINTS. ROW_ID is derived from CON.ROWID, providing the physical row identifier needed by Oracle Forms for optimistic locking and block-level updates.

Key Columns

  • ROW_ID — The rowid of the underlying constraint row; used by the form for update and delete operations.
  • CONSTRAINT_ID — Surrogate primary key uniquely identifying each constraint record.
  • CONSTRAINT_NUM — User-facing constraint number, typically the visible identifier on the form.
  • PERIOD_ID — Foreign key linking the constraint to its variance period in PN_VAR_PERIODS.
  • CONSTR_CAT_CODE — Constraint category code classifying the constraint type.
  • TYPE_CODE — Code indicating the constraint's specific type or behavior.
  • AMOUNT — Numeric value associated with the constraint, such as a threshold or limit.
  • COMMENTS — Free-text description or notes entered by the user.
  • ORG_ID — Operating unit identifier supporting multi-org (MOAC) security.
  • WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard audit tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Flexfield descriptor and attribute columns enabling descriptive flexfield capture.

Common Use Cases and Queries

Typical uses include auditing constraint setup by period, verifying multi-org isolation, and extracting constraint data for external valuation processes. A representative query listing all constraints for the current operating unit is:

  • SELECT constraint_num, constr_cat_code, type_code, amount, comments FROM pn_var_constraints_v WHERE org_id = :org_id ORDER BY constraint_num;
  • SELECT c.constraint_id, c.constraint_num, c.amount FROM pn_var_constraints_v c WHERE c.period_id = :period_id AND c.type_code = :type_code;
  • SELECT c.constr_cat_code, COUNT(*), SUM(c.amount) FROM pn_var_constraints_v c GROUP BY c.constr_cat_code;

Because the view is intended for form input, direct DML should be performed cautiously and preferably through the application UI. When used strictly for queries, it provides a reliable, ORG_ID-secured window into Property Manager variance constraint configuration.