Results for “var_rent_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_VAR_CONSTR_DEFAULTS_ALL is a Property Manager (PN) transactional setup table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores constraint setup information by organization, defining the default constraint terms that apply to variable rent agreements and agreement templates within a given operating unit (ORG_ID). Constraints in Property Manager represent negotiated limits — such as minimum or maximum rent thresholds, escalation caps, or percentage limitations on revenue participation — that govern how variable rent is calculated across a lease or agreement portfolio.

The table is owned by the PN schema and is documented as VALID in ETRM 12.2.2, with 32 physical columns. Heuristically, the mined foreign-key structure classifies this object as standalone at the Data Vault modeling level: it does not participate in a dense hub-and-link network and functions largely as an independent setup entity. From a dimensional perspective, it is best treated as a reference or configuration satellite keyed by its own surrogate identifier, rather than as a hub carrying shared business keys across the enterprise.

Key Information Stored

The table’s surrogate primary key is CONSTR_DEFAULT_ID, enforced by the primary key constraint PN_VAR_CONSTR_DEFAULTS_PK. A unique index, PN_VAR_CONSTR_DEFAULTS_U1, is defined on the same column, confirming it as the sole documented business-key candidate for row-level identification.

Common Use Cases and Queries

Typical scenarios include validating constraint setup prior to running variable rent calculations, auditing effective-dated constraint defaults by operating unit, and reporting on the templates and rent definitions to which defaults are attached.

A sample query listing active constraint defaults for an organization:

SELECT c.CONSTR_DEFAULT_ID,
       c.CONSTR_DEFAULT_NUM,
       c.CONSTR_CAT_CODE,
       c.TYPE_CODE,
       c.AMOUNT,
       c.CONSTR_START_DATE,
       c.CONSTR_END_DATE
FROM   PN.PN_VAR_CONSTR_DEFAULTS_ALL c
WHERE  c.ORG_ID = :org_id
AND    TRUNC(SYSDATE) BETWEEN c.CONSTR_START_DATE
                          AND NVL(c.CONSTR_END_DATE, SYSDATE + 1);

A join pattern resolving the owning templates and rent definition:

SELECT c.CONSTR_DEFAULT_NUM,
       t.TEMPLATE_NAME,
       r.RENT_NAME
FROM   PN.PN_VAR_CONSTR_DEFAULTS_ALL c,
       PN.PN_VAR_TEMPLATES_ALL t,
       PN.PN_VAR_RENTS_ALL r
WHERE  c.AGREEMENT_TEMPLATE_ID = t.AGREEMENT_TEMPLATE_ID
AND    c.VAR_RENT_ID = r.VAR_RENT_ID;

Reports frequently extract the descriptive flexfield attributes for client-specific constraint rules; the ATTRIBUTE_CATEGORY value should always be restricted to the relevant context to avoid cross-context contamination.

Related Objects

  • PN_VAR_RENTS_ALL — referenced via VAR_RENT_ID; defines the variable rent to which the constraint default applies.
  • PN_VAR_TEMPLATES_ALL — referenced via AGREEMENT_TEMPLATE_ID; supplies the agreement template context.
  • PN_VAR_CONSTR_TEMPLATES_ALL — referenced via CONSTR_TEMPLATE_ID; holds the reusable constraint template definition.
  • PN_VAR_CONSTR_DEFAULTS_VL / _TL — translated views, where deployed, expose the constraint default with language-specific text.
  • PN_VAR_CONSTR_DEFAULTS_PK — the primary key constraint enforcing CONSTR_DEFAULT_ID uniqueness.
  • PN_VAR_CONSTR_DEFAULTS_U1 — the unique index that corroborates CONSTR_DEFAULT_ID as the business-key candidate.